Re: Very Very Urgent, Please Help

Try logging onto the server under the domain account that the SQL Agent
services is running under and try launching the packages interactively
from Enterprise Manager.

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

In article <uWxyZDatFHA.3188@xxxxxxxxxxxxxxxxxxxx>,
willgart@xxxxxxxxxxxxxxxxx says...
> 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
.

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
    ... It sounds like you are running the SQL Agent service under the local ... system account which does not have access to the DTS packages. ... System can only access resources on the SQL Server itself) ... 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. ...
    (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)