Check SQL Server Error log..If that wat u mentioning then check system logs..

Thanks a lot Gail Now I am Clear...

Thanks alot Jeff..

This will not work as I said before we are creating system varibales..The same system varible is called inside the package..

Thanks Siva..

What you have mentioned is right and still that wont help me...Can u please answer to my sample Q??

Take Gail's Advise ..its worth

Thanks alot Jeff..

But could u please giove me an example on adding the variable???

jeff.mason (7/26/2010)

---

I did read your code. You create two variables to indicate the path that the SSIS package is in as well as the path of the config file...

jeff.mason (7/26/2010)

---

A SQL Server Agent job running an SSIS package could be configured to point to a config file without a batch file. If all that the batch file...

That will be nice i feel..

Openings from around the globe...

Thanks Adiga..

So that wont resolev my problem...

The issue is that the DBA their in Client side dont want to run a .cmd file on server.

Can u please let me know the difference in executing as .cmd file and .bat batch file???

Thanks Vishal...

Thanks alot Prabha...

I tired fro command prompt but still getting the same error...

The user need to access froma remote machine..He needs full access to SSIS

It was on a developer machine and when he tried logshipping out of his curiosity he found those options missing..

SQL Server 2008 Entreprise RTM Version