Check for firewall and login timeout properties. Are you able to login successfully to the target linked server machine using SSMS from the clinet machine.

Ok is the account running the agent service and the id that you are logged in are they same. Jsut try with that i have did it that way and...

The user should have necessary permissions in tempdb. Always grant users especially application owners dbo rights in tempdb as the might use temporary tables etc.

Leave it to the default of 255 unless you find the number of connections going beyond taht.

Just include xtype='P' alone so that you can limit the search in the system table.

It should be a permission issue as told by rubes give necessary permissions and check if you are able to

ok thanks

Crispin, He says that 32Gb of RAM is available and 30GB has been set to SQL server out of which 26 is being used and around 3GB is not.

If...

I am sure that the data will be read from and written to cache and particularly if the database runs in full recovery mode where the data is not written...

You need to check the client configuration properties of sql server. This can be done using typing cliconfg in run command. Then do the necessary property cahnge.

Always make this a point to run the script above after you restore a database from another server so that orphan ids gets fixed.

Have you restarted SQL Server services. Just restart both the services. Then try to map the profile to your agent service.

Have you set remote connections to on. Is named pipes protocol enabled in your server. By default named pipes is disabled in sql server 2005.

Your full database restore should ahve been with norecovery clause i hope you have missed that and the database has already become online. You need to redo the restoration of...

cross post!!!!!!!!!!!