Failed to start jobs in sql agent after restart service

We have clustered sql2005 (sp2) installed in win2003 (sp2). Recently, we
encountered a problem which failed to start jobs in sql agent after restart
mssql server and aql agent services. It failed with exception error in the
job status dialogue.
There is no error message in event viewer and we found an error aqlagent.out
it shows
2007-07-28 02:08:11 - ! [165] ODBC Error: 0, Unable to complete login
process due to delay in opening server connection [SQLSTATE 08001]
Kindly advise and thanks in advanceCheck your service account (SQLAgent) and permissions related to this job.
Plus, check your cluster resources pertaining to SQL Agent service
"stephanie" <stephanie@.discussions.microsoft.com> wrote in message
news:754761F4-D5A9-460F-904A-BA0FC63CFBC6@.microsoft.com...
> We have clustered sql2005 (sp2) installed in win2003 (sp2). Recently, we
> encountered a problem which failed to start jobs in sql agent after
> restart
> mssql server and aql agent services. It failed with exception error in
> the
> job status dialogue.
>
> There is no error message in event viewer and we found an error
> aqlagent.out
> it shows
>
> 2007-07-28 02:08:11 - ! [165] ODBC Error: 0, Unable to complete login
> process due to delay in opening server connection [SQLSTATE 08001]
>
> Kindly advise and thanks in advance
>|||This problem only exist in node A. If failover to Node B , the agent works
normally.
the sql agent service a/c is an administrator. I compared the permission and
sql agent setting in cluster admin. Thery are the same
Kindly advise. Thanks a lot.
"bass_player [SBS-MVP]" wrote:

> Check your service account (SQLAgent) and permissions related to this job.
> Plus, check your cluster resources pertaining to SQL Agent service
>
> "stephanie" <stephanie@.discussions.microsoft.com> wrote in message
> news:754761F4-D5A9-460F-904A-BA0FC63CFBC6@.microsoft.com...
>
>

Failed to start jobs in sql agent after restart service

We have clustered sql2005 (sp2) installed in win2003 (sp2). Recently, we
encountered a problem which failed to start jobs in sql agent after restart
mssql server and aql agent services. It failed with exception error in the
job status dialogue.
There is no error message in event viewer and we found an error aqlagent.out
it shows
2007-07-28 02:08:11 - ! [165] ODBC Error: 0, Unable to complete login
process due to delay in opening server connection [SQLSTATE 08001]
Kindly advise and thanks in advanceCheck your service account (SQLAgent) and permissions related to this job.
Plus, check your cluster resources pertaining to SQL Agent service
"stephanie" <stephanie@.discussions.microsoft.com> wrote in message
news:754761F4-D5A9-460F-904A-BA0FC63CFBC6@.microsoft.com...
> We have clustered sql2005 (sp2) installed in win2003 (sp2). Recently, we
> encountered a problem which failed to start jobs in sql agent after
> restart
> mssql server and aql agent services. It failed with exception error in
> the
> job status dialogue.
>
> There is no error message in event viewer and we found an error
> aqlagent.out
> it shows
>
> 2007-07-28 02:08:11 - ! [165] ODBC Error: 0, Unable to complete login
> process due to delay in opening server connection [SQLSTATE 08001]
>
> Kindly advise and thanks in advance
>|||This problem only exist in node A. If failover to Node B , the agent works
normally.
the sql agent service a/c is an administrator. I compared the permission and
sql agent setting in cluster admin. Thery are the same
Kindly advise. Thanks a lot.
"bass_player [SBS-MVP]" wrote:
> Check your service account (SQLAgent) and permissions related to this job.
> Plus, check your cluster resources pertaining to SQL Agent service
>
> "stephanie" <stephanie@.discussions.microsoft.com> wrote in message
> news:754761F4-D5A9-460F-904A-BA0FC63CFBC6@.microsoft.com...
> > We have clustered sql2005 (sp2) installed in win2003 (sp2). Recently, we
> > encountered a problem which failed to start jobs in sql agent after
> > restart
> > mssql server and aql agent services. It failed with exception error in
> > the
> > job status dialogue.
> >
> >
> >
> > There is no error message in event viewer and we found an error
> > aqlagent.out
> >
> > it shows
> >
> >
> >
> > 2007-07-28 02:08:11 - ! [165] ODBC Error: 0, Unable to complete login
> > process due to delay in opening server connection [SQLSTATE 08001]
> >
> >
> >
> > Kindly advise and thanks in advance
> >
>
>

Failed to enable constraints

Hello there,

I have a table under SQL2005 express with 8 fields with a primaryKey defined.

In my BLL in the table adapter there is one "SELECT DISTINCT prodCAT from prods"

The prodCAT is a nvarchar(50) and it is not part of an index or primaryKey.

When I preview the data from my BLL I get the correct data.

I defined a new web form (aspx) and put a ddl (dropDownList) with an objectdataSource that relates to the above sql function/command

and I get a

"Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints."

BTW when I defined the above SQL in the BLL I got a "The new command text makes the function return data with schema different from the schema of the main query"

Any suggestions?

Does your BLL return a dataset? If so you shoudl not get the behaviour described.|||

yes, it should return a dataset.

|||

sorry,

it return a data table

|||Try changing it to return a dataset.|||How do I do that??|||Look athttp://www.dotnetjunkies.com/QuickStartv20/howto/doc/adoplus/GetDataFromDB.aspx ADO.NET: Populate a DataSet from a Database|||

First thanx a lot

If I populate the dataset using this technique by-pass the BLL. Is it the correct way to do things??

best regards

|||There are times when a Business Logic Layer is useful - this does not look like one! You could of course put an entry into the BLL that calls the layer below to get a dataset and pass it up to the GUI.

Failed DTS Package locks user out of SQL2005 (Windows Authentication) ... for good!

Would be interested in any advice or comment on the issue we are experiencing with SQL 2005.

In order to test some DTS package migrations, we simply created a DTS package on SQL 2000 (using Export) to copy all database objects from one database to another.

Then we restored the source database on SQL 2005 server, migrated the DTS package, and tried to execute it.

The package migrated 'fine', ran part way, and then failed. Since then we have been unable to connect to the server (Database Engine, or Integration Services) using Windows Authentication. (Error 18456, Sev 16, State 11).

We can connect to the Database Engine using SQL Authentication (but not to Integration Services which only allows Windows Authentication).

We have been able to replicate this consistently - every annoying time we've tried it!

(Reinstalling SQL Server does 'fix' the issue ... until you try a similar package again).

Are you saying that you can't connect to Integration Services? From your post the Database Engine is fine, and 'locks user out' is misleading as the account is not locked out.

What does the package try or fail to do (and which step)?
What appears in the application event log when you fail to connect to IS?
Is IS service still running?|||

Thanks for your reply. Allow me to attempt to answer your queries.

Both Integration Services and Database Engine (MSSQLSERVER) are still running. As stated, we can connect to the Database Engine using SQL Authentication, but Windows Authentication (no matter what account) no longer works to either the Database Engine or Integration Services.

OK, perhaps my terminology is not quite correct - it's not an account lock-out, but that's pretty much the symptom. Perhaps I should say "Windows Authentication is broken"?

Sample Event Log (descending timestamp order ie. same as in event log viewer):

MSSQLSERVER Failure Audit (4) 18456 SERVER\Administrator Login failed for user 'SERVER\Administrator'. [CLIENT: <local machine>]

SQLISPackage Error None 12291 SERVER\Administrator SERVER "Package ""DTS_TEST"" failed."

SQLISPackage Error None 12291 SERVER\Administrator SERVER "Package ""ShellPackage"" failed."

SQLISPackage Information None 12288 SERVER\Administrator SERVER "Package ""ShellPackage"" started."

SQLISPackage Information None 12288 SERVER\Administrator SERVER "Package ""DTS_TEST"" started."

At this stage I can't determine which step in the package is broken, but that's not my biggest issue at this point. Why Windows Authentication "breaks", and how to fix it is my real concern.

Fail to remotely connect to SQL 2005 named instance

I have 2 instances on a remote machine:
- SQL Server 2000 - default instance
- SQL Server 2005 Standard - named instance called: SQL2005.
I am able to connect to SQL2005 from within the remote machine itself
(loopback). I am also able to connect to the SQL 2000 engine remotely
(remember - it is in default instance).
I am NOT able to connect to SQL2005 engine remotely. I enter server name:
remote\SQL2005, user name: sa, password: xxx, but I get "SQL Server does not
exist or access denied". Trying from various clients: Management Studio, UDL
file, connection string, etc.
I marked "Local and remote connections" in Surface Area Configuration;
TCP/IP is enabled and I have no problem of port definitions (all standard -
1433).
I have no firewall or other limitation accessing that remote machine at all.
I checked all Microsoft docs about SQL connectivity issues - that didn't
help.
I'd appreciate any help...
OferStart the SQL Browser service or connect to the named instance via the IP
address and port number.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Ofer Zelig" <ofer@.newsgroups.nospam> wrote in message
news:%23GhXSTBVGHA.5852@.TK2MSFTNGP10.phx.gbl...
>I have 2 instances on a remote machine:
> - SQL Server 2000 - default instance
> - SQL Server 2005 Standard - named instance called: SQL2005.
> I am able to connect to SQL2005 from within the remote machine itself
> (loopback). I am also able to connect to the SQL 2000 engine remotely
> (remember - it is in default instance).
> I am NOT able to connect to SQL2005 engine remotely. I enter server name:
> remote\SQL2005, user name: sa, password: xxx, but I get "SQL Server does
> not
> exist or access denied". Trying from various clients: Management Studio,
> UDL
> file, connection string, etc.
> I marked "Local and remote connections" in Surface Area Configuration;
> TCP/IP is enabled and I have no problem of port definitions (all
> standard -
> 1433).
> I have no firewall or other limitation accessing that remote machine at
> all.
> I checked all Microsoft docs about SQL connectivity issues - that didn't
> help.
> I'd appreciate any help...
> Ofer
>|||SQL Browser doesn't work.
About the IP number - which IP should I use? As far as I know, it is the
same 1433 port as in SQL 2000.
What should be the full server name if the machine is called "remote" and
the SQL 2005 instance is called "SQL2005" ? Isn't it: remote\SQL2005 ?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23cP4edCVGHA.5828@.TK2MSFTNGP10.phx.gbl...
> Start the SQL Browser service or connect to the named instance via the IP
> address and port number.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Ofer Zelig" <ofer@.newsgroups.nospam> wrote in message
> news:%23GhXSTBVGHA.5852@.TK2MSFTNGP10.phx.gbl...
name:[vbcol=seagreen]
>|||Hello Ofer,
May I suggest that we focus on the theard in setup newsgroup? This might be
easier for community to track this issue. Thanks.
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "Ofer Zelig" <ofer@.newsgroups.nospam>
>References: <#GhXSTBVGHA.5852@.TK2MSFTNGP10.phx.gbl>
<#cP4edCVGHA.5828@.TK2MSFTNGP10.phx.gbl>
>Subject: Re: Fail to remotely connect to SQL 2005 named instance
>Date: Sun, 2 Apr 2006 15:13:30 +0200
>Lines: 53
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
>Message-ID: <OLnTq8kVGHA.6084@.TK2MSFTNGP14.phx.gbl>
>Newsgroups:
microsoft.public.sqlserver.setup,microsoft.public.sqlserver.connect
>NNTP-Posting-Host: line134-75.adsl.actcom.co.il 192.115.134.75
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:47287
microsoft.public.sqlserver.setup:76030
>X-Tomcat-NG: microsoft.public.sqlserver.connect
>SQL Browser doesn't work.
>About the IP number - which IP should I use? As far as I know, it is the
>same 1433 port as in SQL 2000.
>What should be the full server name if the machine is called "remote" and
>the SQL 2005 instance is called "SQL2005" ? Isn't it: remote\SQL2005 ?
>
>"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
>news:%23cP4edCVGHA.5828@.TK2MSFTNGP10.phx.gbl...
>name:
does[vbcol=seagreen]
Studio,[vbcol=seagreen]
didn't[vbcol=seagreen]
>
>

Fail to remotely connect to SQL 2005 named instance

I have 2 instances on a remote machine:
- SQL Server 2000 - default instance
- SQL Server 2005 Standard - named instance called: SQL2005.
I am able to connect to SQL2005 from within the remote machine itself
(loopback). I am also able to connect to the SQL 2000 engine remotely
(remember - it is in default instance).
I am NOT able to connect to SQL2005 engine remotely. I enter server name:
remote\SQL2005, user name: sa, password: xxx, but I get "SQL Server does not
exist or access denied". Trying from various clients: Management Studio, UDL
file, connection string, etc.
I marked "Local and remote connections" in Surface Area Configuration;
TCP/IP is enabled and I have no problem of port definitions (all standard -
1433).
I have no firewall or other limitation accessing that remote machine at all.
I checked all Microsoft docs about SQL connectivity issues - that didn't
help.
I'd appreciate any help...
Ofer
Start the SQL Browser service or connect to the named instance via the IP
address and port number.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Ofer Zelig" <ofer@.newsgroups.nospam> wrote in message
news:%23GhXSTBVGHA.5852@.TK2MSFTNGP10.phx.gbl...
>I have 2 instances on a remote machine:
> - SQL Server 2000 - default instance
> - SQL Server 2005 Standard - named instance called: SQL2005.
> I am able to connect to SQL2005 from within the remote machine itself
> (loopback). I am also able to connect to the SQL 2000 engine remotely
> (remember - it is in default instance).
> I am NOT able to connect to SQL2005 engine remotely. I enter server name:
> remote\SQL2005, user name: sa, password: xxx, but I get "SQL Server does
> not
> exist or access denied". Trying from various clients: Management Studio,
> UDL
> file, connection string, etc.
> I marked "Local and remote connections" in Surface Area Configuration;
> TCP/IP is enabled and I have no problem of port definitions (all
> standard -
> 1433).
> I have no firewall or other limitation accessing that remote machine at
> all.
> I checked all Microsoft docs about SQL connectivity issues - that didn't
> help.
> I'd appreciate any help...
> Ofer
>
|||SQL Browser doesn't work.
About the IP number - which IP should I use? As far as I know, it is the
same 1433 port as in SQL 2000.
What should be the full server name if the machine is called "remote" and
the SQL 2005 instance is called "SQL2005" ? Isn't it: remote\SQL2005 ?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23cP4edCVGHA.5828@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Start the SQL Browser service or connect to the named instance via the IP
> address and port number.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Ofer Zelig" <ofer@.newsgroups.nospam> wrote in message
> news:%23GhXSTBVGHA.5852@.TK2MSFTNGP10.phx.gbl...
name:
>
|||Hello Ofer,
May I suggest that we focus on the theard in setup newsgroup? This might be
easier for community to track this issue. Thanks.
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "Ofer Zelig" <ofer@.newsgroups.nospam>
>References: <#GhXSTBVGHA.5852@.TK2MSFTNGP10.phx.gbl>
<#cP4edCVGHA.5828@.TK2MSFTNGP10.phx.gbl>
>Subject: Re: Fail to remotely connect to SQL 2005 named instance
>Date: Sun, 2 Apr 2006 15:13:30 +0200
>Lines: 53
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
>Message-ID: <OLnTq8kVGHA.6084@.TK2MSFTNGP14.phx.gbl>
>Newsgroups:
microsoft.public.sqlserver.setup,microsoft.public. sqlserver.connect
>NNTP-Posting-Host: line134-75.adsl.actcom.co.il 192.115.134.75
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP14.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:47287
microsoft.public.sqlserver.setup:76030[vbcol=seagreen]
>X-Tomcat-NG: microsoft.public.sqlserver.connect
>SQL Browser doesn't work.
>About the IP number - which IP should I use? As far as I know, it is the
>same 1433 port as in SQL 2000.
>What should be the full server name if the machine is called "remote" and
>the SQL 2005 instance is called "SQL2005" ? Isn't it: remote\SQL2005 ?
>
>"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
>news:%23cP4edCVGHA.5828@.TK2MSFTNGP10.phx.gbl...
>name:
does[vbcol=seagreen]
Studio,[vbcol=seagreen]
didn't
>
>