Re: Very Very Urgent, Please Help

does the profiler display something?
do you see any MSDB access when you try to open/execute a package?

have you try to force the server access by creating an alias?
you can force the TCP/IP usage or netbios usage; also try an IP address instead-of a netbios or DNS name


"DKRReddy" <dkrreddy@xxxxxxxxxxx> wrote in message news:%23wjNDdVtFHA.3896@xxxxxxxxxxxxxxxxxxxxxxx
No, production servers services will always run under domian admin account.
This is not the issue.


"Darren Gosbell" <dgosbell_at_yahoo_dot_com> wrote in message
news:MPG.1d8b89989fc5c0c7989688@xxxxxxxxxxxxxxxxxxxxx
It sounds like you are running the SQL Agent service under the local
system account which does not have access to the DTS packages.

The way I normally set up SQL Agent is to run it under a domain user
account. This has 2 advantages.

1) It can then access network resources such as file shares (Local
System can only access resources on the SQL Server itself)

2) You can also "debug" security issues such as the one you are now
having because you can log in under the same account as the SQL Agent
and run the packages from Enterprise manager it is often easier to see
exactly where your problems are occurring.

I would recommend setting up this user with the minimum require security
privileges. RESIST the temptation to set this user up as an
administrator as it could mean that any user that can schedule a job can
run a process under this account. If someone cracks an SA password, they
can schedule a job to give them full access to your machine at the OS
level and from there possibly out into your network.

--
Regards
Darren Gosbell
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell

In article <#bi0pnMtFHA.596@xxxxxxxxxxxxxxxxxxxx>,
willgart@xxxxxxxxxxxxxxxxx says...

does the SQL Agent service run under a known account?

"DKRReddy" <dkrreddy@xxxxxxxxxxx> wrote in message
news:%23SWDRmJtFHA.664@xxxxxxxxxxxxxxxxxxxxxxx
> When running the dts package as a job , it's failing while opening the
> package itself.
> Security log in keep filling, is this the cause?
>
>
>
> "Darren Gosbell" <dgosbell_at_yahoo_dot_com> wrote in message
> news:MPG.1d88f7c738031b6f989685@xxxxxxxxxxxxxxxxxxxxx
> This sounds like a permissions issue. If you can run the packages from
> Enterprise manager then the issue is not necessarily with the packages
> themselves.
>
> If the packages are executed via a SQL agent job that launches them
> using dtsrun, then I suggest you check which account the SQL Agent
> service is running under. It might also have something to do with the
> owner of the Agent jobs.
>
> Packages run via Enterprise Manager run in the security context of the
> currently logged on user. Packages launched via SQL Agent run in the
> context of the account that the SQL Agent Service logs in under.
>
> -- > Regards
> Darren Gosbell
> <dgosbell_at_yahoo_dot_com>
> Blog: http://www.geekswithblogs.net/darrengosbell
>
> In article <eP$UU6osFHA.3164@xxxxxxxxxxxxxxxxxxxx>, > dkrreddy@xxxxxxxxxxx
> says...
>> All packages are refering to the new server only.If I run the package
>> from
>> enterprise manager runs fine no timeout errors.
>>
>>
>>
>> "Jéjé" <willgart@xxxxxxxxxxxxxxxxx> wrote in message
>> news:OHhuUhnsFHA.3404@xxxxxxxxxxxxxxxxxxxxxxx
>> > does your packages are stored in the MSDB database?
>> > Have you changed your main package to use the right SQL Server
>> > instance?
>> >
>> > if your main dts package try to open a package on the <old server>
and 
> if
>> > this server is down, then you'll receive a timeout error.
>> >
>> >




.

Relevant Pages

  • Re: Very Very Urgent, Please Help
    ... production servers services will always run under domian admin account. ... It sounds like you are running the SQL Agent service under the local ... system account which does not have access to the DTS packages. ...
    (microsoft.public.sqlserver.datawarehouse)
  • Re: Very Very Urgent, Please Help
    ... It sounds like you are running the SQL Agent service under the local ... system account which does not have access to the DTS packages. ...
    (microsoft.public.sqlserver.datawarehouse)
  • Re: Very Very Urgent, Please Help
    ... Try logging onto the server under the domain account that the SQL Agent ... >> system account which does not have access to the DTS packages. ...
    (microsoft.public.sqlserver.datawarehouse)
  • Re: DTS transfer from Paradox to SQL Server 2000 using SQL Agent
    ... On your PC then you bring the package to your PC, it is not on the server. ... from executing tasks on the network, when started from SQL Agent? ... The DTS Packages collects data from a Paradox ... execute them from a SQL Agent job I receive an error. ...
    (microsoft.public.sqlserver.dts)
  • Re: Replication Monitor disappears
    ... account and see if it shows up. ... Looking for a SQL Server replication book? ... When I was setting up replication I had SQL ... Finally I was able to start the SQL Agent service by ...
    (microsoft.public.sqlserver.replication)