have you tried the same thing on another server just to test? exactly how is the path written? I don't need to see dir names or drives just X:\\XXXX\XXX for...

what type of db is the non sql db

what happens if you pass that path manually as a test? exec xp_create_subdir '..testpath..'

yeah sorry, replied then read your update properly!

do you have loads of linked servers? to do them all at the same time, click and highlight 'linked servers' under 'server objects', then click 'view'>'object explorer details', you will...

That sounds like a bad day at the office!

what is passed as the @chkdirectory parameter

Sounds strange! what if you specify what you want the column name to be returned as? ie

select FIRST_NAME "FIRST_NAME" from ...

it all depends on what resources the server has got, and what the workload is like. I have one server that profiler tracing is no problem for, and another where...

you can right click a linked server and choose 'script linked server as' > 'create to' > 'new query'

do this for each linked server. That what you're after?

do you see anything useful in the event logs? what happens if you then restart the SQL service?

are you the DBA? if not get someone who is sysadmin to run the trace and if they experience the same issues you can rule permissions out.

Is your instance up to date service pack wise? Not the same conditions but similar error described in the following url

https://support.microsoft.com/en-us/kb/2545989

I get this error after my ssms has been open for a long time, and i have a few connections open. Generally I get it when trying to view job...

Looks nasty! Seems to be addressed in this microsoft link

http://support.microsoft.com/kb/2001221

What is running at the time?