Thanks for your reply...

when i am executing sp_delete_backuphistory '08/31/2013' its taking too long time to execute and MSDB log file is increasing very huge during this time.

why log file...

backupfile - 44095724

backupfilegroup - 22047863

restorefile - 974

restorefilegroup - 487

restorehistory - 487

backupmediafamily - 22047869

problem happenings only db restore activity rest of ssms activities working fine.

my question is why out of memory error is thrown when i am doing restoration using GUI

Yes, we restarted server also because RAM up-gradation happens on 2 back days back only from 16GB to 32GB

tsql restoration script is working well.

I tried both locally and server also.

When i am doing right click database >> Task >> restore >>database. I am getting below error

"Exception of type 'system.outofmemoryexception' was thrown"

Server configuration :

32 GB RAM

64 bit O/S

2 processors

Intel(R)...

Pls help me on this.

Thanks...

Thanks for your quick response.

I am very new about this topic.

I cant able to view SQL objects after connecting the linked server. Remote login credentials should be in remote server...

Thanks for your quick reply, shall i shrink both MSDB data and log file as well?

Its a permission issue check both server SQL Server Agent rights level and share folder access level as well as domain.

Yes, its really affect the log shipping configuration.

You can remove the log shipping and change the recovery model from Full to Simple and then shrink the log files and again...

Please find the error log

The job failed. The Job was invoked by Schedule 2864 (DefaultCopyJobSchedule). The last step to run was step 1 (Log shipping copy job step.)

Executed...