Sounds to me like a permissions issue.

Check and make sure the user you are logged in as on the SQL server also has permissions to write to the folder you're...

Glad it helped!

It's very confusing sometimes figuring how to loop through and assign dynamic variables in SSIS!

Yes, thanks, for that.

The path noted does exist. I have verified that, but already knew that it did, because that path is being used to call it from cmdExec in...

One more problem.

Trying to call the SSIS Package from xp_CmdShell, as follows. We do use xp_CmdShell for other items in our SPs, so it is definitely switched on and...

Thanks Bhuvenesh...

A simple solution. Call the SSIS package from within the stored procedure.

It hadn't even occurred to me.

Good idea.

Um, no, in SQL2005 it doesn't care whether you use an alias or not, makes no difference and certainly doesn't make Order By clauses fail.

Keep in mind this is also...

Thanks a million Carl! That all sounds like great advice, and I've passed it on to the programmer having the problem to check things out.

Love the line SQL =...

Bhuvnesh, I'm not sure what your code is trying to achieve, but it doesn't seem to have anything to do with the info I am trying to get.

No, it is financially sensitive info, cannot show the trigger itself, but we have run the insert statements individually, confirmed all data being inserted exists and is valid, and have...

I could change the names, but it seems an awful lot of trouble to do just to post what basically amounts to the properties of the backup file. I can...

I'd rather not post specific details about our servers.

If there's something specifically you are looking for, I can check it out.

The logical filenames for the backup are as I'd expect,...

That's the problem, it does not have the same logical file names, but when trying to use MOVE it gets the message as above.

I have got around it for now...

Thanks for the questions Greg.

Running RESTORE HEADERONLY for the backup set returns what I would expect. Database name, etc. all look the same.

I've also run RESTORE FILELISTONLY which shows me...

I feel your pain. I had a similar situation, but had to dump the idea and head off in another direction, since I wasn't allowed to put our server...

I'm not sure.

I know that you won't be able to execute an SSIS package if you are in Windows Authentication Mode unless your users have pretty high access rights... like...