From our discuss me tto feel the same..but I am junior guy here and dont have much to recommend...They still feels that what they do is right ..Now they came...

Thanks Gail,

How can we avoid that??

Its a procedure which takes data from a table inserts into table variable and displays that...I know its difficult to tell something from wat i...

Create a maintenance plan ..tats the simplest way..

You are right...

Still they opposing the suggestion..They staes if we schedule the dtsx file in some other scheduler in that case we cant give config file in job tats wat...

The variable in cmd file is storing the path of config file 🙁

Is that the same when u try to expand databasess in SSMS??

1.yes

2.Not able to login as u sadid as its rpompting the same login

3.How to do that??

Awesome Jeff....

will talk to SSIS guys and let u know ..

Thanks for ur help & support..

Let me explain u wat we doing ..

We have two temp variable

one for root path

second one for config path

the root path variable is assigned to ssis variable

ssis varibale +...

You can do this from SQL script task wizard..

select users-->in advanced select script login=true

Hope this will help

Check syslogins..

Have u checked giving anyother name as login and try will get same error...

The issues is with DNS i think...

Which Edition of SQL Server you using??

Is it a windows or SQL login??

Have anyone changed the password??

There are chances that password might have changed for the login and some where someone might have saved the old...

U checked the default folder??

by the way y u need last 4 months info??

You sure u cleaned the logs??