In that case it doesnt look like your xp_cmdshell proxy account is being used....

based on the error it looks like a permissions issue to the folder....

attached is a powershell script I have used to script out all objects. This scripts all objects to their own file you can adjust the $Scripter.Options.FileName option. The script either...

I have found the problem. The remote server is a VM and the VM was recently move to a different host and it's virtual switch was changed from being a...

My preferred way would be to make the port static on the server with the named instance.

You would do this by choosing a port not in use on the...

it looks like your port for the named instance is dynamic so without making any configuration changes you will have to get SQL Browser working.

First, is SQL Browser running? next...

Agreed, most likely, the SQL Browser port. you can test if it is open by...

You might not be able to use SERVERNAME\INSTANCE when creating the linked server. try SERVERNAME,PORT. This may be because the SQL browser service is unable to cross your domains. I...

if this is something to be scheduled you could avoid xp_cmdshell and run this powershell script with SQL Agent.

$Now = Get-Date

$Days = “30”

$TargetFolder = “\\t-fc-fim\logs”

$LastWrite = $Now.AddDays(-$days)

get-childitem $TargetFolder *.*...

you could check if there are any connections to your SQL Server by doing a netstat.

netstat -an | find "1433"

If there are any established connections the output will tell you...

Just for clarification, You can use UNC paths in a CMD windows. It is FORFILES that does not allow UNC paths.

Thanks. That is what I have done.

additionally I copied the mdf and corrupt ldf to a different server to poke around and when I try to attach the database the...

Forgot to mention that this database is in simple recovery, so no log backups. point-in-time recovery is not needed on the database so restoring from a couple of nights ago...

have a look at the datediff function

the job will run in the user context of the account used to start SQL Server agent. Possibly that account doesn't have the correct permissions.