Wednesday, March 7, 2012

DTS opening error on server enterprise manager

We have got a SQL server 2000 loaded on a Windows 2000 advance server. We had
created some DTS on this server which were scheduled to run on perticular
time. Few days back all the DTS started failing to execute through scheduler.
While checking from any client machine the DTS is running successfully but on
the server machine it is not. When I tried to open the DTS on the server
console Enterprise Manager it is giving me following error
Error Source : Microsoft OLE DB Provider for SQL Server
Error Description : [DBNETLIB][ConnectionOpen (connect()).]SQL Server
does not exists or access denied
I had tried with reinstalling the SQL Enterprise manager on the server,
reregistered the SQLDMO.dll but without any success.
Can anybody help me?
Hi
It is probably you creared the DTS on your workstation and not on the
server. If you schedule the DTS to run as a job it will be ran under SQL
Server Agent account. Check it out.
"satyaki" <satyaki@.discussions.microsoft.com> wrote in message
news:7A71BBFA-C68A-4894-9466-39CFAC659F7B@.microsoft.com...
> We have got a SQL server 2000 loaded on a Windows 2000 advance server. We
had
> created some DTS on this server which were scheduled to run on perticular
> time. Few days back all the DTS started failing to execute through
scheduler.
> While checking from any client machine the DTS is running successfully but
on
> the server machine it is not. When I tried to open the DTS on the server
> console Enterprise Manager it is giving me following error
> Error Source : Microsoft OLE DB Provider for SQL Server
> Error Description : [DBNETLIB][ConnectionOpen (connect()).]SQL Server
> does not exists or access denied
> I had tried with reinstalling the SQL Enterprise manager on the server,
> reregistered the SQLDMO.dll but without any success.
>
> Can anybody help me?
>
>
>
|||It is created from the workstation but on the server. That means it is saved
on the server and scheduled on the server under SQlserver Agent account. It
was running still last few days. Now it is giving the problem. it is not
giving me access to open the package also. it is giving me the error that I
had written.
"Uri Dimant" wrote:

> Hi
> It is probably you creared the DTS on your workstation and not on the
> server. If you schedule the DTS to run as a job it will be ran under SQL
> Server Agent account. Check it out.
>
>
> "satyaki" <satyaki@.discussions.microsoft.com> wrote in message
> news:7A71BBFA-C68A-4894-9466-39CFAC659F7B@.microsoft.com...
> had
> scheduler.
> on
>
>
|||Well,that means that something was changed (an account, a password)
Are you sure?
"satyaki" <satyaki@.discussions.microsoft.com> wrote in message
news:14BDAF90-AC4B-4C29-B459-0305DB6877DB@.microsoft.com...
> It is created from the workstation but on the server. That means it is
saved
> on the server and scheduled on the server under SQlserver Agent account.
It
> was running still last few days. Now it is giving the problem. it is not
> giving me access to open the package also. it is giving me the error that
I[vbcol=seagreen]
> had written.
>
>
> "Uri Dimant" wrote:
We[vbcol=seagreen]
perticular[vbcol=seagreen]
but[vbcol=seagreen]
server[vbcol=seagreen]
Server[vbcol=seagreen]
server,[vbcol=seagreen]
|||No there is no changes happend, I am able to Open the package and execute the
package from my client pc. But while doing the same on the sever console it
is giving me error. I am convienced that scheduler is not able to run the
package as server is giving the error.
This error is comming only on the Server's Enterprise Manager, not on any
client side.
"Uri Dimant" wrote:

> Well,that means that something was changed (an account, a password)
> Are you sure?
>
>
> "satyaki" <satyaki@.discussions.microsoft.com> wrote in message
> news:14BDAF90-AC4B-4C29-B459-0305DB6877DB@.microsoft.com...
> saved
> It
> I
> We
> perticular
> but
> server
> Server
> server,
>
>
|||Still the only logical reason can be that there somehow is a difference
between your client and the server.
How do you log on on the server when you try to open the DTS via Enterprise
Mgr? Using your own account or rather via a (local) admin account on that
machine ?
If the latter, check if the sql-connection you speak about is based on a
Trusted Connection or on a SQL-login/pwd-connection. If it is trusted you
should verify (or even beter : try to simulate) the account used for
running the SQLAgent is able to connect to the requested database. Likely
something has changed the past week, they just forgot to tell you =)
Good Luck,
Roby
"satyaki" <satyaki@.discussions.microsoft.com> wrote in message
news:33CC2F2F-EE23-46E1-AF5D-650C47170C98@.microsoft.com...[vbcol=seagreen]
> No there is no changes happend, I am able to Open the package and execute
> the
> package from my client pc. But while doing the same on the sever console
> it
> is giving me error. I am convienced that scheduler is not able to run the
> package as server is giving the error.
> This error is comming only on the Server's Enterprise Manager, not on any
> client side.
> "Uri Dimant" wrote:
|||In regards to the packages failing, you need to check the
job history for the DTS packages to determine why they are
failing. Checking the details in the job history will give
you more detailed information on why the packages are
failing to run as schedule.
-Sue
On Mon, 31 Jan 2005 02:09:06 -0800, "satyaki"
<satyaki@.discussions.microsoft.com> wrote:

>We have got a SQL server 2000 loaded on a Windows 2000 advance server. We had
>created some DTS on this server which were scheduled to run on perticular
>time. Few days back all the DTS started failing to execute through scheduler.
>While checking from any client machine the DTS is running successfully but on
>the server machine it is not. When I tried to open the DTS on the server
>console Enterprise Manager it is giving me following error
> Error Source : Microsoft OLE DB Provider for SQL Server
> Error Description : [DBNETLIB][ConnectionOpen (connect()).]SQL Server
>does not exists or access denied
>I had tried with reinstalling the SQL Enterprise manager on the server,
>reregistered the SQLDMO.dll but without any success.
>
>Can anybody help me?
>
>
>
|||I had already checked that, it is giving same error server does not exists or
access denied. this is only happening on the server console enterprise
manager.
I don't thing it is any secured connection problem, nobody has change any
server configurations. Other activity on the enterprise manager is running
perfectly. I am facing this problem only on DTS package opening, may be due
to this the job scheduler is not running as job history is showing the same
problem.
"Sue Hoegemeier" wrote:

> In regards to the packages failing, you need to check the
> job history for the DTS packages to determine why they are
> failing. Checking the details in the job history will give
> you more detailed information on why the packages are
> failing to run as schedule.
> -Sue
> On Mon, 31 Jan 2005 02:09:06 -0800, "satyaki"
> <satyaki@.discussions.microsoft.com> wrote:
>
>
|||i am using sa login in the server enterprise manager to open the DTS. i had
tried with windows authentication, DTS creators login but without any result.
And no body has change any settings on the server/
"Roby Van Hoye" wrote:

> Still the only logical reason can be that there somehow is a difference
> between your client and the server.
> How do you log on on the server when you try to open the DTS via Enterprise
> Mgr? Using your own account or rather via a (local) admin account on that
> machine ?
> If the latter, check if the sql-connection you speak about is based on a
> Trusted Connection or on a SQL-login/pwd-connection. If it is trusted you
> should verify (or even beter : try to simulate) the account used for
> running the SQLAgent is able to connect to the requested database. Likely
> something has changed the past week, they just forgot to tell you =)
> Good Luck,
> Roby
> "satyaki" <satyaki@.discussions.microsoft.com> wrote in message
> news:33CC2F2F-EE23-46E1-AF5D-650C47170C98@.microsoft.com...
>
>

No comments:

Post a Comment