Intermittent Timeout - ExecuteNonQuery On Stored Procedure

Hi All,
I'll do my best to try and describe the issue I'm having with my
application.
I'm writing a VB.Net front end for a SQL 2000 Database. I have a generic
data layer which communicates with the database, and provides classes to the
front end application.
Most of the classes are filled using the stored procedures which fill
datatable which fill properties. However, I have a method in my login class,
which calls the ADO.net method ExecuteNonQuery on a stored procedure to
update a table (I've copied in the procedure T-SQL and the end of the mail -
it's nothing complicated!!!).
Intermittently, the method will not run, and errors on the ExecuteNonQuery
line with the error "Timeout expired. The timeout period elapsed prior to
completion of the operation or the server is not responding."
Before this runs, there is a method which fills a datatable using the Fill
Method of a Data Adapter and this runs everytime. However, the
ExecuteNonQuery does not run, and errors out.
When this does occur, I can open query analyzer and if I try to run any
stored procedures in the database, I get a timeout. Even Altering a stored
procedure times out. I can use other databases and run stored procedure in
them with no problems, but this specific database causes timeouts.
After say 5 minutes the attempt to run the ExecuteNonQuery works and it will
be fine for a while (couple of hours), then it will start to timeout again
for 5-10 mins.
What could be causing this, as it's database specific. Is there any way, I
can have the Database rebuild itself and clear out any dodgy temporary
tables'
Any method which uses a data adapter runs fine all the time, but the
ExecuteNonQuery fails intermittently.
I'm a bit lost really.
Any help is appreciated.
Thanks
Alex
******* Stored Procedure *********
ALTER PROC proc_Utility_UpdateUserLoggedIn
@.UserID int,
@.LoggedIn bit = 0
AS
SET NOCOUNT ON
UPDATE tblUser
SET
LastLogin = GetDate(),
LoggedIn = @.LoggedIn
WHERE UserID = @.UserID
*********************************Hi Alex,
Are you ending properly transactions?
--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com
"Alex Stevens" <AlexStevens_NOSPAMPLEASE@.gcc.co.uk> wrote in message
news:eFahpgUoEHA.2612@.TK2MSFTNGP15.phx.gbl...
> Hi All,
> I'll do my best to try and describe the issue I'm having with my
> application.
> I'm writing a VB.Net front end for a SQL 2000 Database. I have a generic
> data layer which communicates with the database, and provides classes to
> the
> front end application.
> Most of the classes are filled using the stored procedures which fill
> datatable which fill properties. However, I have a method in my login
> class,
> which calls the ADO.net method ExecuteNonQuery on a stored procedure to
> update a table (I've copied in the procedure T-SQL and the end of the
> mail -
> it's nothing complicated!!!).
> Intermittently, the method will not run, and errors on the ExecuteNonQuery
> line with the error "Timeout expired. The timeout period elapsed prior to
> completion of the operation or the server is not responding."
> Before this runs, there is a method which fills a datatable using the Fill
> Method of a Data Adapter and this runs everytime. However, the
> ExecuteNonQuery does not run, and errors out.
> When this does occur, I can open query analyzer and if I try to run any
> stored procedures in the database, I get a timeout. Even Altering a stored
> procedure times out. I can use other databases and run stored procedure in
> them with no problems, but this specific database causes timeouts.
> After say 5 minutes the attempt to run the ExecuteNonQuery works and it
> will
> be fine for a while (couple of hours), then it will start to timeout again
> for 5-10 mins.
> What could be causing this, as it's database specific. Is there any way, I
> can have the Database rebuild itself and clear out any dodgy temporary
> tables'
> Any method which uses a data adapter runs fine all the time, but the
> ExecuteNonQuery fails intermittently.
> I'm a bit lost really.
> Any help is appreciated.
> Thanks
> Alex
>
> ******* Stored Procedure *********
> ALTER PROC proc_Utility_UpdateUserLoggedIn
> @.UserID int,
> @.LoggedIn bit = 0
> AS
> SET NOCOUNT ON
> UPDATE tblUser
> SET
> LastLogin = GetDate(),
> LoggedIn = @.LoggedIn
> WHERE UserID = @.UserID
> *********************************
>|||Hi
Timeouts are caused by SQL not getting it's work finished in time. This
indicates a blocking or performance issue.
Make sure that you have appropriate indexes in place, run sp_who2 and look
for any processes that are blocked by other processes when you run your query
through your VB code or Query Analyser.
Regards
Mike
"Alex Stevens" wrote:
> Hi All,
> I'll do my best to try and describe the issue I'm having with my
> application.
> I'm writing a VB.Net front end for a SQL 2000 Database. I have a generic
> data layer which communicates with the database, and provides classes to the
> front end application.
> Most of the classes are filled using the stored procedures which fill
> datatable which fill properties. However, I have a method in my login class,
> which calls the ADO.net method ExecuteNonQuery on a stored procedure to
> update a table (I've copied in the procedure T-SQL and the end of the mail -
> it's nothing complicated!!!).
> Intermittently, the method will not run, and errors on the ExecuteNonQuery
> line with the error "Timeout expired. The timeout period elapsed prior to
> completion of the operation or the server is not responding."
> Before this runs, there is a method which fills a datatable using the Fill
> Method of a Data Adapter and this runs everytime. However, the
> ExecuteNonQuery does not run, and errors out.
> When this does occur, I can open query analyzer and if I try to run any
> stored procedures in the database, I get a timeout. Even Altering a stored
> procedure times out. I can use other databases and run stored procedure in
> them with no problems, but this specific database causes timeouts.
> After say 5 minutes the attempt to run the ExecuteNonQuery works and it will
> be fine for a while (couple of hours), then it will start to timeout again
> for 5-10 mins.
> What could be causing this, as it's database specific. Is there any way, I
> can have the Database rebuild itself and clear out any dodgy temporary
> tables'
> Any method which uses a data adapter runs fine all the time, but the
> ExecuteNonQuery fails intermittently.
> I'm a bit lost really.
> Any help is appreciated.
> Thanks
> Alex
>
> ******* Stored Procedure *********
> ALTER PROC proc_Utility_UpdateUserLoggedIn
> @.UserID int,
> @.LoggedIn bit = 0
> AS
> SET NOCOUNT ON
> UPDATE tblUser
> SET
> LastLogin = GetDate(),
> LoggedIn = @.LoggedIn
> WHERE UserID = @.UserID
> *********************************
>
>|||I'm not using transactions in the stored procedure........?
"Miha Markic [MVP C#]" <miha at rthand com> wrote in message
news:%23Au3lrUoEHA.3592@.TK2MSFTNGP14.phx.gbl...
> Hi Alex,
> Are you ending properly transactions?
> --
> Miha Markic [MVP C#] - RightHand .NET consulting & development
> miha at rthand com
> www.rthand.com
> "Alex Stevens" <AlexStevens_NOSPAMPLEASE@.gcc.co.uk> wrote in message
> news:eFahpgUoEHA.2612@.TK2MSFTNGP15.phx.gbl...
> > Hi All,
> >
> > I'll do my best to try and describe the issue I'm having with my
> > application.
> >
> > I'm writing a VB.Net front end for a SQL 2000 Database. I have a generic
> > data layer which communicates with the database, and provides classes to
> > the
> > front end application.
> >
> > Most of the classes are filled using the stored procedures which fill
> > datatable which fill properties. However, I have a method in my login
> > class,
> > which calls the ADO.net method ExecuteNonQuery on a stored procedure to
> > update a table (I've copied in the procedure T-SQL and the end of the
> > mail -
> > it's nothing complicated!!!).
> >
> > Intermittently, the method will not run, and errors on the
ExecuteNonQuery
> > line with the error "Timeout expired. The timeout period elapsed prior
to
> > completion of the operation or the server is not responding."
> >
> > Before this runs, there is a method which fills a datatable using the
Fill
> > Method of a Data Adapter and this runs everytime. However, the
> > ExecuteNonQuery does not run, and errors out.
> >
> > When this does occur, I can open query analyzer and if I try to run any
> > stored procedures in the database, I get a timeout. Even Altering a
stored
> > procedure times out. I can use other databases and run stored procedure
in
> > them with no problems, but this specific database causes timeouts.
> >
> > After say 5 minutes the attempt to run the ExecuteNonQuery works and it
> > will
> > be fine for a while (couple of hours), then it will start to timeout
again
> > for 5-10 mins.
> >
> > What could be causing this, as it's database specific. Is there any way,
I
> > can have the Database rebuild itself and clear out any dodgy temporary
> > tables'
> > Any method which uses a data adapter runs fine all the time, but the
> > ExecuteNonQuery fails intermittently.
> >
> > I'm a bit lost really.
> >
> > Any help is appreciated.
> >
> > Thanks
> >
> > Alex
> >
> >
> > ******* Stored Procedure *********
> > ALTER PROC proc_Utility_UpdateUserLoggedIn
> >
> > @.UserID int,
> > @.LoggedIn bit = 0
> >
> > AS
> >
> > SET NOCOUNT ON
> >
> > UPDATE tblUser
> > SET
> > LastLogin = GetDate(),
> > LoggedIn = @.LoggedIn
> >
> > WHERE UserID = @.UserID
> > *********************************
> >
> >
>|||As you can see the stored procedure (at the bottom of the original email) is
an extremely simple update procedure.
The only thiing that has been run before that on the SQL database is a
SELECT statement (posted at the end) which returns a resultset also
implementing the NOLOCK to stop the table being locked on a simple read.
In query analyzer, Select statements work fine, but updates don't.
> Make sure that you have appropriate indexes in place, run sp_who2 and look
> for any processes that are blocked by other processes when you run your
query
> through your VB code or Query Analyser.
The table has an int Primary Key, when the application is started, I
sometimes get two processes one which has a batch end time, and one which
has a batch end time of 01/01/1900 (presumably a Null).
I can't track down where this erroneous process comes from (it is on the
database in question), because it doesn't appear when I set through the
code.
How can I check to see if a process is blocking the UPDATE process'
Thanks
Alex
******Stored Proc*******
ALTER PROC proc_Get_User
---
-- Date Created: 28 April 2004
-- Procedure Description: Standard Get procedure.
-- Created By: Alex Stevens
-- Template version 1.0 Dated: 28/04/2004 12:41:58
-- Generated by CodeSmith 2.5
--
-- Used in Classes:
--
---
@.UserID int = Null,
@.UserName varChar(20) = Null
AS
BEGIN
SELECT dbo.tblUser.*
FROM dbo.tblUser (NOLOCK)
WHERE (@.UserID IS NULL OR UserID = @.UserID) OR
(@.UserName IS NULL OR UserName = @.UserName)
ORDER BY UserName
END
*************
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:F92E78E3-70CF-44C2-824D-4C686642307C@.microsoft.com...
> Hi
> Timeouts are caused by SQL not getting it's work finished in time. This
> indicates a blocking or performance issue.
> Make sure that you have appropriate indexes in place, run sp_who2 and look
> for any processes that are blocked by other processes when you run your
query
> through your VB code or Query Analyser.
> Regards
> Mike
> "Alex Stevens" wrote:
> > Hi All,
> >
> > I'll do my best to try and describe the issue I'm having with my
> > application.
> >
> > I'm writing a VB.Net front end for a SQL 2000 Database. I have a generic
> > data layer which communicates with the database, and provides classes to
the
> > front end application.
> >
> > Most of the classes are filled using the stored procedures which fill
> > datatable which fill properties. However, I have a method in my login
class,
> > which calls the ADO.net method ExecuteNonQuery on a stored procedure to
> > update a table (I've copied in the procedure T-SQL and the end of the
mail -
> > it's nothing complicated!!!).
> >
> > Intermittently, the method will not run, and errors on the
ExecuteNonQuery
> > line with the error "Timeout expired. The timeout period elapsed prior
to
> > completion of the operation or the server is not responding."
> >
> > Before this runs, there is a method which fills a datatable using the
Fill
> > Method of a Data Adapter and this runs everytime. However, the
> > ExecuteNonQuery does not run, and errors out.
> >
> > When this does occur, I can open query analyzer and if I try to run any
> > stored procedures in the database, I get a timeout. Even Altering a
stored
> > procedure times out. I can use other databases and run stored procedure
in
> > them with no problems, but this specific database causes timeouts.
> >
> > After say 5 minutes the attempt to run the ExecuteNonQuery works and it
will
> > be fine for a while (couple of hours), then it will start to timeout
again
> > for 5-10 mins.
> >
> > What could be causing this, as it's database specific. Is there any way,
I
> > can have the Database rebuild itself and clear out any dodgy temporary
> > tables'
> > Any method which uses a data adapter runs fine all the time, but the
> > ExecuteNonQuery fails intermittently.
> >
> > I'm a bit lost really.
> >
> > Any help is appreciated.
> >
> > Thanks
> >
> > Alex
> >
> >
> > ******* Stored Procedure *********
> > ALTER PROC proc_Utility_UpdateUserLoggedIn
> >
> > @.UserID int,
> > @.LoggedIn bit = 0
> >
> > AS
> >
> > SET NOCOUNT ON
> >
> > UPDATE tblUser
> > SET
> > LastLogin = GetDate(),
> > LoggedIn = @.LoggedIn
> >
> > WHERE UserID = @.UserID
> > *********************************
> >
> >
> >sql

intermittent stalling on a query

I've been trying to diagonose a strange problem with an application that I
inherited. Every few days, SQL Server will take between 3 to 4 minutes to
perform a really simple update.
The application that runs against the database is a real-time monitoring
program that communicates to a number of devices. It probably issues about
a dozen queries every second, 80% updates, 10% selects, 10% inserts. There
are no deletes being done. For the most part, all of the queries run in
less than a second. In the application, the CommandTimeout value on the
queries is set to 2 minutes. The application is setup to restart itself on
when a timeout occurs. And since the CommandTimeout is not high enough (2
mins vs 3+ mins), the application will into a non-stop cycle of restarting
itself... Until I go into Query Analyzer, and run a simple update statement
against an arbitrary table; which will take between 3 to 4 minutes to
complete, and then afterwards, the application will start running fine
again. I've seen instances where the application would stay in a restart
cycle for days at a time.
There does not appear to be a deadlock or open transaction. I've tried
running SP_WHO2, SP_LOCK, DBCC OPENTRAN, DBCC CHECKDB and didn't see any
issues.
The application is running on the same computer as the SQL server. It is
the sole application running against the database. The application uses the
SQLOLEDB provider.
The database is about 10 MB, the transaction log is 3 GB (mostly empty).
Server properties: Windows Server 2003 Standard Edition, Pentium 4 2.8 GHz
(hyperthreading-enabled), 512 MB RAM, and plenty of free drive space.
SQL Server settings:
- SQL Server 2000 8.00.818 (SP3)
- Memory is setup for dynamic allocation
- Processor is setup to use the two "instances"
- "Implicit transactions" is checked
- "Close cursor on COMMIT" is checked
- "Auto Grow" is enabled for both the data file and transaction log
- "Auto Update Statistics", "Auto Create Statistics", and "Torn Page
Detection" are checked
There are jobs to backup both the data file and transaction log.
I noticed that the timeouts tend to be from one of two queries (but about
99% of the time, it's one of these queries being called). Each of the
queries is literally a single update statement touching a single table,
wrapped in a stored procedure. And the tables that they update have at most
a dozen records in them.
Things, I've tried,
- I thought it was auto grow causing the stall, but I manually increased the
database size, and the application did not hiccup.
- I also thought it might be statistics related, so I ran a "sp_updatestats"
against the database. The next day, the problem came up again.
- I've tried adding "with recompile" to the stored procedure with no luck
either.
This seems like it might be server configuration issue, but I'm not sure
what else to check.
TYIA for any advice.My bet is still on the Autogrow. First off I assume you mean the db is 10GB
and not MB? If autogrow kicks in it will attempt to grow the file by about
1GB. On a slow disk subsystem this can take a while. If the connection
that issued the command that forced the autogrow times out the growth will
be canceled and you are back to where you started. The next insert or
update may force another growth which may or may not succeed. It is all
about timing and resources. When you manually grow the DB there is no
problem because there is not a statement (insert or update) in the process
of executing that forced the growth so it will succeed. You should always
have plenty of free space in the db and autogrow should never kick in. When
you run low you need to manually grow it at the appropriate time so you
always have enough free space. If you are that low you are too low anyway
since the first time you do a reindex you will need more space. If you
have auto shrink turned on then turn it off immediately. You should also
change the growth to be a fixed amount vs. a percentage. Make it an amount
that can grow in no more than 30 seconds or so. That way you won't get a
timeout if it does kick in.
Andrew J. Kelly SQL MVP
"John Smith" <john@.smith.com> wrote in message
news:OtaoqmFIFHA.2356@.TK2MSFTNGP12.phx.gbl...
> I've been trying to diagonose a strange problem with an application that I
> inherited. Every few days, SQL Server will take between 3 to 4 minutes to
> perform a really simple update.
> The application that runs against the database is a real-time monitoring
> program that communicates to a number of devices. It probably issues
> about a dozen queries every second, 80% updates, 10% selects, 10% inserts.
> There are no deletes being done. For the most part, all of the queries
> run in less than a second. In the application, the CommandTimeout value
> on the queries is set to 2 minutes. The application is setup to restart
> itself on when a timeout occurs. And since the CommandTimeout is not high
> enough (2 mins vs 3+ mins), the application will into a non-stop cycle of
> restarting itself... Until I go into Query Analyzer, and run a simple
> update statement against an arbitrary table; which will take between 3 to
> 4 minutes to complete, and then afterwards, the application will start
> running fine again. I've seen instances where the application would stay
> in a restart cycle for days at a time.
> There does not appear to be a deadlock or open transaction. I've tried
> running SP_WHO2, SP_LOCK, DBCC OPENTRAN, DBCC CHECKDB and didn't see any
> issues.
> The application is running on the same computer as the SQL server. It is
> the sole application running against the database. The application uses
> the SQLOLEDB provider.
> The database is about 10 MB, the transaction log is 3 GB (mostly empty).
> Server properties: Windows Server 2003 Standard Edition, Pentium 4 2.8 GHz
> (hyperthreading-enabled), 512 MB RAM, and plenty of free drive space.
> SQL Server settings:
> - SQL Server 2000 8.00.818 (SP3)
> - Memory is setup for dynamic allocation
> - Processor is setup to use the two "instances"
> - "Implicit transactions" is checked
> - "Close cursor on COMMIT" is checked
> - "Auto Grow" is enabled for both the data file and transaction log
> - "Auto Update Statistics", "Auto Create Statistics", and "Torn Page
> Detection" are checked
> There are jobs to backup both the data file and transaction log.
> I noticed that the timeouts tend to be from one of two queries (but about
> 99% of the time, it's one of these queries being called). Each of the
> queries is literally a single update statement touching a single table,
> wrapped in a stored procedure. And the tables that they update have at
> most a dozen records in them.
> Things, I've tried,
> - I thought it was auto grow causing the stall, but I manually increased
> the database size, and the application did not hiccup.
> - I also thought it might be statistics related, so I ran a
> "sp_updatestats" against the database. The next day, the problem came up
> again.
> - I've tried adding "with recompile" to the stored procedure with no luck
> either.
> This seems like it might be server configuration issue, but I'm not sure
> what else to check.
> TYIA for any advice.
>|||Thanks, I didn't realize the part about the autogrow being canceled on a
timeout.
I checked again, and was off a bit. It's at 30 MB, but still tiny. It
might have been the transaction log that was expanding (is it affected the
same way, by a connection timeout?).
I'll keep a closer eye on this then. Thanks again.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eRL2YkGIFHA.3336@.TK2MSFTNGP10.phx.gbl...
> My bet is still on the Autogrow. First off I assume you mean the db is
> 10GB and not MB? If autogrow kicks in it will attempt to grow the file by
> about 1GB. On a slow disk subsystem this can take a while. If the
> connection that issued the command that forced the autogrow times out the
> growth will be canceled and you are back to where you started. The next
> insert or update may force another growth which may or may not succeed. It
> is all about timing and resources. When you manually grow the DB there is
> no problem because there is not a statement (insert or update) in the
> process of executing that forced the growth so it will succeed. You
> should always have plenty of free space in the db and autogrow should
> never kick in. When you run low you need to manually grow it at the
> appropriate time so you always have enough free space. If you are that
> low you are too low anyway since the first time you do a reindex you will
> need more space. If you have auto shrink turned on then turn it off
> immediately. You should also change the growth to be a fixed amount vs. a
> percentage. Make it an amount that can grow in no more than 30 seconds or
> so. That way you won't get a timeout if it does kick in.
> --
> Andrew J. Kelly SQL MVP
>
> "John Smith" <john@.smith.com> wrote in message
> news:OtaoqmFIFHA.2356@.TK2MSFTNGP12.phx.gbl...
>|||Yes the tran log is essentially the same behavior in that any statements
that require logging will sit and wait until the log is finished expanding.
If you have a 30MB db and a 3GB log you are not doing something right. You
stated that you are doing regular Full and Log backups. If that were the
case and you didn't have any long running open transactions your log file
should only be a few hundred MB at best. Try running DBCC OPENTRAN and see
what it tells you. Also check your backups to make sure they are actually
happening with no errors.
Andrew J. Kelly SQL MVP
"John Smith" <john@.smith.com> wrote in message
news:OX4$t1IIFHA.608@.TK2MSFTNGP10.phx.gbl...
> Thanks, I didn't realize the part about the autogrow being canceled on a
> timeout.
> I checked again, and was off a bit. It's at 30 MB, but still tiny. It
> might have been the transaction log that was expanding (is it affected the
> same way, by a connection timeout?).
> I'll keep a closer eye on this then. Thanks again.
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eRL2YkGIFHA.3336@.TK2MSFTNGP10.phx.gbl...
>

Intermittent SQL Server does not exist or access denied.

Hi, I have a web application which is taking a fair bit of traffic.
It involves a registration process, and then a series of questions which
must be answered. The SQL server receives upwards of 1,000,000 queries a
day.
Unfortunately on a small number of these queries (~500 a day), the ASP pages
are returning that the SQL server does not exist or that access if denied.
Having explored the Microsoft Support Site, and exhausted all possible
solutions, without actually reaching a solution - I was wondering - is it
possible that the server is actually just taking so many requests that it
can't be found? Surely this should return a timeout?
The web box is a Windows 2000 IIS installation, and the SQL box is a
separate Windows 2000 / SQL Server 2000 installation.
Anyone got any ideas?
Many thanks.
MattWhat are you using to handle connections -- TCP/IP sockets, named pipes or
both? I would double check your IIS server and SQL server to make sure the
server and client network utilities match up with connection parameters.
Have you tried using Performance Monitor on the SQL server? You will take a
small performance hit, but you can get some more information on what is
happening when the connection fails. You should probably start off
monitoring a few basic SQL counters -- like for reads, writes and
connections.
When a SQL connection can't be made, the SQL server does not exist or access
denied is actually a common error. In my line of support, it usually means
that a network connection (ipc$) between the client and server can't be
made, but I imagine this is not the case for you.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Matt Pallatt" <matt.pallatt@.bnm.co.uk> wrote in message
news:%23ZMUOpzQEHA.3124@.TK2MSFTNGP12.phx.gbl...
> Hi, I have a web application which is taking a fair bit of traffic.
> It involves a registration process, and then a series of questions which
> must be answered. The SQL server receives upwards of 1,000,000 queries a
> day.
> Unfortunately on a small number of these queries (~500 a day), the ASP
pages
> are returning that the SQL server does not exist or that access if denied.
> Having explored the Microsoft Support Site, and exhausted all possible
> solutions, without actually reaching a solution - I was wondering - is it
> possible that the server is actually just taking so many requests that it
> can't be found? Surely this should return a timeout?
> The web box is a Windows 2000 IIS installation, and the SQL box is a
> separate Windows 2000 / SQL Server 2000 installation.
> Anyone got any ideas?
> Many thanks.
> Matt
>|||So connection/session pooling should be in use for large web based
applications. If you've disabled connection/session pooling then this
would put a heavier burden on the server.
What is your connection Timeout value?
What is running on the server when the timeouts happen?
Is there any blocking?
How many web servers are connecting to the SQL Server?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||We were having the exact same problem. It seems that by stopping SQL Server
from listening on named pipes (ie. just leaving tcp/ip) stopped the problem|||Sorry, may have spoken too soon. Our error have come back.

Intermittent SQL Server does not exist or access denied.

ASP.NET application with intermittent returns of 503 errors with the
following message.
System.Data.SqlClient.SqlException: SQL Server does not exist or access
denied. SQL Server does not exist or access denied.
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of
the exception can be identified using the exception stack trace below.
Servers running Windows 2003 SQL 2000.
This has been a problem for a long time (less than .3% of the time). No
code changes have been made. The only changes was Windows SP1 and post
SP patches on all servers. The patching may have made this issue more
pronounced.
Any suggestions from the experts?
Thanks,
RoxanneWhen they are intermittent they are difficult to track down.
Often those related to network connectivity issues. Have you
checked the event logs on the IIS box - particularly looking
for any network related issues?
-Sue
On 2 Nov 2005 10:32:52 -0800, roxy636@.yahoo.com wrote:

>ASP.NET application with intermittent returns of 503 errors with the
>following message.
>System.Data.SqlClient.SqlException: SQL Server does not exist or access
>denied. SQL Server does not exist or access denied.
>An unhandled exception was generated during the execution of the
>current web request. Information regarding the origin and location of
>the exception can be identified using the exception stack trace below.
>Servers running Windows 2003 SQL 2000.
>This has been a problem for a long time (less than .3% of the time). No
>code changes have been made. The only changes was Windows SP1 and post
>SP patches on all servers. The patching may have made this issue more
>pronounced.
>Any suggestions from the experts?
>Thanks,
>Roxanne|||Search no further...
http://support.microsoft.com/defaul...kb;en-us;328476
Note, this answer took forever to find so I'm posting everywhere...|||So was your solution to enable connection pooling? Or was it simply a
tcp/ip configuration issue. Unless you explicitly disable connection
pooling, then connections should be pooled, were you disabling pooling?
Thanks for any info, we are seeing the exact same symptoms at a client
of ours.|||Connection pooling was disabled for security reasons, so you need to
add registry keys specified in article here:
path:
HKEY_LOCAL_MACHINE\System\CurrentControl
Set\services\Tcpip\Parameters
type: DWORD
name: TcpTimedWaitDelay
value: 30 (decimal)
type: DWORD
name: MaxUserPort
value: 10000 (decimal)
Ultimately is connection ooliing is enabled this shouldn't happen, but
try it anyway. Check netsats from command prompt...if you see around
4000 connections in TIME_WAIT, then that is the problem.|||Thanks, since connection pooling is enabled and this is occuring even
soon after a reboot under low load. I do not suspect we are creating
too many connections to sql, but I do suspect some network
communication problems. I am going to further diagnose thier network
configuration relative to the front and back planes of the web server.
But I will not overlook this as a possibility, so I will also get a
netstat -n Thanks so much for the info..|||Turned out to be Bandwidth Throttling, disabling that option for the
Application Pool alleviated the HTTP 503 errors.

Intermittent SQL Server does not exist or access denied.

ASP.NET application with intermittent returns of 503 errors with the
following message.
System.Data.SqlClient.SqlException: SQL Server does not exist or access
denied. SQL Server does not exist or access denied.
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of
the exception can be identified using the exception stack trace below.
Servers running Windows 2003 SQL 2000.
This has been a problem for a long time (less than .3% of the time). No
code changes have been made. The only changes was Windows SP1 and post
SP patches on all servers. The patching may have made this issue more
pronounced.
Any suggestions from the experts?
Thanks,
Roxanne
When they are intermittent they are difficult to track down.
Often those related to network connectivity issues. Have you
checked the event logs on the IIS box - particularly looking
for any network related issues?
-Sue
On 2 Nov 2005 10:32:52 -0800, roxy636@.yahoo.com wrote:

>ASP.NET application with intermittent returns of 503 errors with the
>following message.
>System.Data.SqlClient.SqlException: SQL Server does not exist or access
>denied. SQL Server does not exist or access denied.
>An unhandled exception was generated during the execution of the
>current web request. Information regarding the origin and location of
>the exception can be identified using the exception stack trace below.
>Servers running Windows 2003 SQL 2000.
>This has been a problem for a long time (less than .3% of the time). No
>code changes have been made. The only changes was Windows SP1 and post
>SP patches on all servers. The patching may have made this issue more
>pronounced.
>Any suggestions from the experts?
>Thanks,
>Roxanne
|||Search no further...
http://support.microsoft.com/default...b;en-us;328476
Note, this answer took forever to find so I'm posting everywhere...
|||So was your solution to enable connection pooling? Or was it simply a
tcp/ip configuration issue. Unless you explicitly disable connection
pooling, then connections should be pooled, were you disabling pooling?
Thanks for any info, we are seeing the exact same symptoms at a client
of ours.
|||Connection pooling was disabled for security reasons, so you need to
add registry keys specified in article here:
path:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\servic es\Tcpip\Parameters
type: DWORD
name: TcpTimedWaitDelay
value: 30 (decimal)
type: DWORD
name: MaxUserPort
value: 10000 (decimal)
Ultimately is connection ooliing is enabled this shouldn't happen, but
try it anyway. Check netsats from command prompt...if you see around
4000 connections in TIME_WAIT, then that is the problem.
|||Thanks, since connection pooling is enabled and this is occuring even
soon after a reboot under low load. I do not suspect we are creating
too many connections to sql, but I do suspect some network
communication problems. I am going to further diagnose thier network
configuration relative to the front and back planes of the web server.
But I will not overlook this as a possibility, so I will also get a
netstat -n Thanks so much for the info..
|||Turned out to be Bandwidth Throttling, disabling that option for the
Application Pool alleviated the HTTP 503 errors.

Intermittent SQL Server does not exist or access denied.

Hi, I have a web application which is taking a fair bit of traffic.
It involves a registration process, and then a series of questions which
must be answered. The SQL server receives upwards of 1,000,000 queries a
day.
Unfortunately on a small number of these queries (~500 a day), the ASP pages
are returning that the SQL server does not exist or that access if denied.
Having explored the Microsoft Support Site, and exhausted all possible
solutions, without actually reaching a solution - I was wondering - is it
possible that the server is actually just taking so many requests that it
can't be found? Surely this should return a timeout?
The web box is a windows 2000 IIS installation, and the SQL box is a
separate Windows 2000 / SQL Server 2000 installation.
Anyone got any ideas?
Many thanks.
Matt
What are you using to handle connections -- TCP/IP sockets, named pipes or
both? I would double check your IIS server and SQL server to make sure the
server and client network utilities match up with connection parameters.
Have you tried using Performance Monitor on the SQL server? You will take a
small performance hit, but you can get some more information on what is
happening when the connection fails. You should probably start off
monitoring a few basic SQL counters -- like for reads, writes and
connections.
When a SQL connection can't be made, the SQL server does not exist or access
denied is actually a common error. In my line of support, it usually means
that a network connection (ipc$) between the client and server can't be
made, but I imagine this is not the case for you.
************************************************** *****************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
************************************************** *****************
"Matt Pallatt" <matt.pallatt@.bnm.co.uk> wrote in message
news:%23ZMUOpzQEHA.3124@.TK2MSFTNGP12.phx.gbl...
> Hi, I have a web application which is taking a fair bit of traffic.
> It involves a registration process, and then a series of questions which
> must be answered. The SQL server receives upwards of 1,000,000 queries a
> day.
> Unfortunately on a small number of these queries (~500 a day), the ASP
pages
> are returning that the SQL server does not exist or that access if denied.
> Having explored the Microsoft Support Site, and exhausted all possible
> solutions, without actually reaching a solution - I was wondering - is it
> possible that the server is actually just taking so many requests that it
> can't be found? Surely this should return a timeout?
> The web box is a windows 2000 IIS installation, and the SQL box is a
> separate Windows 2000 / SQL Server 2000 installation.
> Anyone got any ideas?
> Many thanks.
> Matt
>
|||So connection/session pooling should be in use for large web based
applications. If you've disabled connection/session pooling then this
would put a heavier burden on the server.
What is your connection Timeout value?
What is running on the server when the timeouts happen?
Is there any blocking?
How many web servers are connecting to the SQL Server?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||We were having the exact same problem. It seems that by stopping SQL
Server from listening on named pipes (ie. just leaving tcp/ip) stopped
the problem
chudles
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message245192.html
|||Sorry, may have spoken too soon. Our error have come back.
chudles
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message245192.html

Intermittent SQL 7 Login problem

Access 2000 application on client can log-in to SQL server using one of the SQL server logins.

Problem is that from certain clients you can log in using ANY id.

From other clients, the login attempt produces the SQL Server login box.

Any ideas why this might be ?

Client is Win2000.

All help would be appreciated!Have u tried connecting to sql from same box with diff network usernames ?

U prob running integrated security ?|||The login box should not come up at all ! That's the problem.

For the clients where it is the correct behaviour, you do not see the login box at all after starting the application.

However, when you start the application from some clients on the network, then the login box appears ...

Thanks.|||Sorry I'm not familiar with Access 2000 very much.

I was wondering wheter some clients are getting into sql via integrated security - taking the clients network login credentials by default - & if that fails the sql security login then the Login Box appears

Have u tried connecting to sql from same box with diff network usernames

Is it Box or user specific SQL Security Access problem.|||Try WINDOWS AUTHENTICATION on SQLSErver side.|||Originally posted by Satya
Try WINDOWS AUTHENTICATION on SQLSErver side.

Hi Satya -
I do not understand - could you please explain what you mean in more detail?

Many thanks.

Intermittent Slowdown Of SQL Server 2000

Hi,
I have been struggling to identify the cause of an application go slow
that happens perhaps once a month or a day or two after the server has
been rebooted. The application is a web based ASP app that uses SQL
server 2000, both on the same box. This has been occuring for at least
6 months, probably longer and the only way I have found to overcome
this problem without a server reboot is to restart to the SQL service.

>From my investigations I am assuming that the problem is SQL server
related but I am unable to identify the root cause of the problem and
was wondering if anyone can offer suggestions to help me fix this
issue.
Many Thanks
This sounds like this is a blocking problem. You can try to identify
the blocking SPID. If you run this SQL Statement, you'll get the heads
for the blocking chain:
select blocker.spid
from master..sysprocesses blocker inner join master..sysprocesses
blocked
on blocker.spid = blocked.blocked
where blocker.blocked = 0
After you get the blocking spid you can chek what the process is doing
and who is running it with sp_who2 and dbcc inputbuffer.
Adi
Ham wrote:
> Hi,
> I have been struggling to identify the cause of an application go slow
> that happens perhaps once a month or a day or two after the server has
> been rebooted. The application is a web based ASP app that uses SQL
> server 2000, both on the same box. This has been occuring for at least
> 6 months, probably longer and the only way I have found to overcome
> this problem without a server reboot is to restart to the SQL service.
> related but I am unable to identify the root cause of the problem and
> was wondering if anyone can offer suggestions to help me fix this
> issue.
> Many Thanks
|||Hi,
Try using fixed memory area for SQL Server.
Also to start with basics
Use SQL Profiler to capture the events at that time.
Thanks
Ajay
Adi wrote:[vbcol=seagreen]
> This sounds like this is a blocking problem. You can try to identify
> the blocking SPID. If you run this SQL Statement, you'll get the heads
> for the blocking chain:
> select blocker.spid
> from master..sysprocesses blocker inner join master..sysprocesses
> blocked
> on blocker.spid = blocked.blocked
> where blocker.blocked = 0
> After you get the blocking spid you can chek what the process is doing
> and who is running it with sp_who2 and dbcc inputbuffer.
> Adi
> Ham wrote:
|||Thanks all, I will try these when the problem next occurs.
Thanks Again
On 23 Jan, 10:50, "Adi" <adic...@.hotmail.com> wrote:[vbcol=seagreen]
> This sounds like this is a blocking problem. You can try to identify
> the blocking SPID. If you run thisSQLStatement, you'll get the heads
> for the blocking chain:
> select blocker.spid
> from master..sysprocesses blocker inner join master..sysprocesses
> blocked
> on blocker.spid = blocked.blocked
> where blocker.blocked = 0
> After you get the blocking spid you can chek what the process is doing
> and who is running it with sp_who2 and dbcc inputbuffer.
> Adi
>
> Ham wrote:
>
sql

Intermittent Slowdown Of SQL Server 2000

Hi,
I have been struggling to identify the cause of an application go slow
that happens perhaps once a month or a day or two after the server has
been rebooted. The application is a web based ASP app that uses SQL
server 2000, both on the same box. This has been occuring for at least
6 months, probably longer and the only way I have found to overcome
this problem without a server reboot is to restart to the SQL service.
>From my investigations I am assuming that the problem is SQL server
related but I am unable to identify the root cause of the problem and
was wondering if anyone can offer suggestions to help me fix this
issue.
Many ThanksThis sounds like this is a blocking problem. You can try to identify
the blocking SPID. If you run this SQL Statement, you'll get the heads
for the blocking chain:
select blocker.spid
from master..sysprocesses blocker inner join master..sysprocesses
blocked
on blocker.spid = blocked.blocked
where blocker.blocked = 0
After you get the blocking spid you can chek what the process is doing
and who is running it with sp_who2 and dbcc inputbuffer.
Adi
Ham wrote:
> Hi,
> I have been struggling to identify the cause of an application go slow
> that happens perhaps once a month or a day or two after the server has
> been rebooted. The application is a web based ASP app that uses SQL
> server 2000, both on the same box. This has been occuring for at least
> 6 months, probably longer and the only way I have found to overcome
> this problem without a server reboot is to restart to the SQL service.
> >From my investigations I am assuming that the problem is SQL server
> related but I am unable to identify the root cause of the problem and
> was wondering if anyone can offer suggestions to help me fix this
> issue.
> Many Thanks|||Hi,
Try using fixed memory area for SQL Server.
Also to start with basics
Use SQL Profiler to capture the events at that time.
Thanks
Ajay
Adi wrote:
> This sounds like this is a blocking problem. You can try to identify
> the blocking SPID. If you run this SQL Statement, you'll get the heads
> for the blocking chain:
> select blocker.spid
> from master..sysprocesses blocker inner join master..sysprocesses
> blocked
> on blocker.spid = blocked.blocked
> where blocker.blocked = 0
> After you get the blocking spid you can chek what the process is doing
> and who is running it with sp_who2 and dbcc inputbuffer.
> Adi
> Ham wrote:
> > Hi,
> >
> > I have been struggling to identify the cause of an application go slow
> > that happens perhaps once a month or a day or two after the server has
> > been rebooted. The application is a web based ASP app that uses SQL
> > server 2000, both on the same box. This has been occuring for at least
> > 6 months, probably longer and the only way I have found to overcome
> > this problem without a server reboot is to restart to the SQL service.
> >
> > >From my investigations I am assuming that the problem is SQL server
> > related but I am unable to identify the root cause of the problem and
> > was wondering if anyone can offer suggestions to help me fix this
> > issue.
> >
> > Many Thanks|||Thanks all, I will try these when the problem next occurs.
Thanks Again
On 23 Jan, 10:50, "Adi" <adic...@.hotmail.com> wrote:
> This sounds like this is a blocking problem. You can try to identify
> the blocking SPID. If you run thisSQLStatement, you'll get the heads
> for the blocking chain:
> select blocker.spid
> from master..sysprocesses blocker inner join master..sysprocesses
> blocked
> on blocker.spid = blocked.blocked
> where blocker.blocked = 0
> After you get the blocking spid you can chek what the process is doing
> and who is running it with sp_who2 and dbcc inputbuffer.
> Adi
>
> Ham wrote:
> > Hi,
> > I have been struggling to identify the cause of an application go slow
> > that happens perhaps once a month or a day or two after the server has
> > been rebooted. The application is a web based ASP app that usesSQL
> > server 2000, both on the same box. This has been occuring for at least
> > 6 months, probably longer and the only way I have found to overcome
> > this problem without a server reboot is to restart to theSQLservice.
> > >From my investigations I am assuming that the problem isSQLserver
> > related but I am unable to identify the root cause of the problem and
> > was wondering if anyone can offer suggestions to help me fix this
> > issue.
> > Many Thanks- Hide quoted text -- Show quoted text -

Intermittent Slowdown Of SQL Server 2000

Hi,
I have been struggling to identify the cause of an application go slow
that happens perhaps once a month or a day or two after the server has
been rebooted. The application is a web based ASP app that uses SQL
server 2000, both on the same box. This has been occuring for at least
6 months, probably longer and the only way I have found to overcome
this problem without a server reboot is to restart to the SQL service.

>From my investigations I am assuming that the problem is SQL server
related but I am unable to identify the root cause of the problem and
was wondering if anyone can offer suggestions to help me fix this
issue.
Many ThanksThis sounds like this is a blocking problem. You can try to identify
the blocking SPID. If you run this SQL Statement, you'll get the heads
for the blocking chain:
select blocker.spid
from master..sysprocesses blocker inner join master..sysprocesses
blocked
on blocker.spid = blocked.blocked
where blocker.blocked = 0
After you get the blocking spid you can chek what the process is doing
and who is running it with sp_who2 and dbcc inputbuffer.
Adi
Ham wrote:
> Hi,
> I have been struggling to identify the cause of an application go slow
> that happens perhaps once a month or a day or two after the server has
> been rebooted. The application is a web based ASP app that uses SQL
> server 2000, both on the same box. This has been occuring for at least
> 6 months, probably longer and the only way I have found to overcome
> this problem without a server reboot is to restart to the SQL service.
>
> related but I am unable to identify the root cause of the problem and
> was wondering if anyone can offer suggestions to help me fix this
> issue.
> Many Thanks|||Hi,
Try using fixed memory area for SQL Server.
Also to start with basics
Use SQL Profiler to capture the events at that time.
Thanks
Ajay
Adi wrote:[vbcol=seagreen]
> This sounds like this is a blocking problem. You can try to identify
> the blocking SPID. If you run this SQL Statement, you'll get the heads
> for the blocking chain:
> select blocker.spid
> from master..sysprocesses blocker inner join master..sysprocesses
> blocked
> on blocker.spid = blocked.blocked
> where blocker.blocked = 0
> After you get the blocking spid you can chek what the process is doing
> and who is running it with sp_who2 and dbcc inputbuffer.
> Adi
> Ham wrote:|||Thanks all, I will try these when the problem next occurs.
Thanks Again
On 23 Jan, 10:50, "Adi" <adic...@.hotmail.com> wrote:[vbcol=seagreen]
> This sounds like this is a blocking problem. You can try to identify
> the blocking SPID. If you run thisSQLStatement, you'll get the heads
> for the blocking chain:
> select blocker.spid
> from master..sysprocesses blocker inner join master..sysprocesses
> blocked
> on blocker.spid = blocked.blocked
> where blocker.blocked = 0
> After you get the blocking spid you can chek what the process is doing
> and who is running it with sp_who2 and dbcc inputbuffer.
> Adi
>
> Ham wrote:
>
>
>

Intermittent Login failure at boot

I have a Windows Service middleware application that depends on SQL
Server. We are migrating from an existing Windows 2000 server/
SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
boot time and more often than not, the middleware application fails to
start and SQLServer reports a Failure Audit saying the Login failed
for the user 'SomeUser'. This is the account the middleware uses, it
is a SQLServer account and not a Windows account.
But once the machine is booted and I login to the server, I can start
the middleware application successfully using the Services control
panel. I'm assuming that despite the dependency of my middleware
service on the SQLServer service, SQLServer is not sufficiently
initialised to accept client connections at the point that my
middleware service tries to connect. I can't say whether this is
peculiar to SQLServer Express because to see if it also occurs with
SQLServer Standard 2005 I would need to reinstall and configure the
operating system and application software.
If there is no workaround for this, the only solution I can think of
(without going to Windows 2003 Standard and SQLServer 2005 Standard)
is to write another Windows Service to check whether or not my
middleware started successfully and to start it if it failed to start.
Any help with this problem would be much appreciated.
Thanks
Go through the SQL Server log to get a better idea if it's
just a timing issue...which I would guess it probably is.
You should see the login failure with a date time as well as
when the database the middleware uses is available, when SQL
is ready to accept client connections. You would also want
to check the state of the login failure to see the cause of
the failure.
But...going through the log should give you more information
to understand what's going on in your situation.
-Sue
On Tue, 31 Jul 2007 17:46:13 -0700, Dave
<pigwin32@.gmail.com> wrote:

>I have a Windows Service middleware application that depends on SQL
>Server. We are migrating from an existing Windows 2000 server/
>SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
>boot time and more often than not, the middleware application fails to
>start and SQLServer reports a Failure Audit saying the Login failed
>for the user 'SomeUser'. This is the account the middleware uses, it
>is a SQLServer account and not a Windows account.
>But once the machine is booted and I login to the server, I can start
>the middleware application successfully using the Services control
>panel. I'm assuming that despite the dependency of my middleware
>service on the SQLServer service, SQLServer is not sufficiently
>initialised to accept client connections at the point that my
>middleware service tries to connect. I can't say whether this is
>peculiar to SQLServer Express because to see if it also occurs with
>SQLServer Standard 2005 I would need to reinstall and configure the
>operating system and application software.
>If there is no workaround for this, the only solution I can think of
>(without going to Windows 2003 Standard and SQLServer 2005 Standard)
>is to write another Windows Service to check whether or not my
>middleware started successfully and to start it if it failed to start.
>Any help with this problem would be much appreciated.
>Thanks

Intermittent Login failure at boot

I have a Windows Service middleware application that depends on SQL
Server. We are migrating from an existing Windows 2000 server/
SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
boot time and more often than not, the middleware application fails to
start and SQLServer reports a Failure Audit saying the Login failed
for the user 'SomeUser'. This is the account the middleware uses, it
is a SQLServer account and not a Windows account.
But once the machine is booted and I login to the server, I can start
the middleware application successfully using the Services control
panel. I'm assuming that despite the dependency of my middleware
service on the SQLServer service, SQLServer is not sufficiently
initialised to accept client connections at the point that my
middleware service tries to connect. I can't say whether this is
peculiar to SQLServer Express because to see if it also occurs with
SQLServer Standard 2005 I would need to reinstall and configure the
operating system and application software.
If there is no workaround for this, the only solution I can think of
(without going to Windows 2003 Standard and SQLServer 2005 Standard)
is to write another Windows Service to check whether or not my
middleware started successfully and to start it if it failed to start.
Any help with this problem would be much appreciated.
ThanksGo through the SQL Server log to get a better idea if it's
just a timing issue...which I would guess it probably is.
You should see the login failure with a date time as well as
when the database the middleware uses is available, when SQL
is ready to accept client connections. You would also want
to check the state of the login failure to see the cause of
the failure.
But...going through the log should give you more information
to understand what's going on in your situation.
-Sue
On Tue, 31 Jul 2007 17:46:13 -0700, Dave
<pigwin32@.gmail.com> wrote:

>I have a Windows Service middleware application that depends on SQL
>Server. We are migrating from an existing Windows 2000 server/
>SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
>boot time and more often than not, the middleware application fails to
>start and SQLServer reports a Failure Audit saying the Login failed
>for the user 'SomeUser'. This is the account the middleware uses, it
>is a SQLServer account and not a Windows account.
>But once the machine is booted and I login to the server, I can start
>the middleware application successfully using the Services control
>panel. I'm assuming that despite the dependency of my middleware
>service on the SQLServer service, SQLServer is not sufficiently
>initialised to accept client connections at the point that my
>middleware service tries to connect. I can't say whether this is
>peculiar to SQLServer Express because to see if it also occurs with
>SQLServer Standard 2005 I would need to reinstall and configure the
>operating system and application software.
>If there is no workaround for this, the only solution I can think of
>(without going to Windows 2003 Standard and SQLServer 2005 Standard)
>is to write another Windows Service to check whether or not my
>middleware started successfully and to start it if it failed to start.
>Any help with this problem would be much appreciated.
>Thankssql

Intermittent connection loss?

Hi all,
I have a .Net windows application that uses the micrsoft application block
to make calls to the database. I am doing a few thousand records that must
be inserted. I have a problem where on occasion I get an exception that
says "SQL Server does not exist or access denied." This seems to be an
intermittent problem, and profiler has not turned up any info. The server is
running locally, so I don't think it is a network issue.
Anybody have any ideas?
Thanks
J
Are you running the .NET application using TCP/IP or Shared Memory?
Check the sysprocesses table when your application is running & look at the
net_library column to confirm.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Kevin,
I get a timeout period elapsed error when trying to open a connection on a
machine where the server is local. It does not occur when running the same
app on another client on the network. It is a .net application using the
SQLClient. If I turn off shared memory protocol for clients on the server the
error does not occur. Is there an issue with shared memory access and .Net?
"Kevin McDonnell [MSFT]" wrote:

> Are you running the .NET application using TCP/IP or Shared Memory?
> Check the sysprocesses table when your application is running & look at the
> net_library column to confirm.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||There may be an issue. I would open a case with a VC engineer in the
Webdata group to investigate.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Intermittent Connection Issue - How to Monitor

We have a 3rd party application which uses a connection to a SQL
Server 2005 database. It intermittently loses connnection to the
database and displays an error. The vendor is playing hardball with
resolving the issues. What we would like to do is have a small
application that can run on the machine the client applilcation is
installed on and make connection checks and logs. This way if both
loose connection we can rule out the 3rd party software as being the
issue. However, if theirs looses connection and the monitor
application does not notice anything we can use that information as
leverage for dealing with the vendor.
Is there any such application out there that would do this?
Thanks in advance.
Try this tool:
http://www.paessler.com/ipcheck/download
It has a free version that can be use to check every 15 minutes.
Thank you
Lucas
<lavaice@.gmail.com> wrote in message
news:1180719965.172880.52790@.g4g2000hsf.googlegrou ps.com...
> We have a 3rd party application which uses a connection to a SQL
> Server 2005 database. It intermittently loses connnection to the
> database and displays an error. The vendor is playing hardball with
> resolving the issues. What we would like to do is have a small
> application that can run on the machine the client applilcation is
> installed on and make connection checks and logs. This way if both
> loose connection we can rule out the 3rd party software as being the
> issue. However, if theirs looses connection and the monitor
> application does not notice anything we can use that information as
> leverage for dealing with the vendor.
> Is there any such application out there that would do this?
> Thanks in advance.
>
|||What we are looking for is something that would actually establish a
SQL connection to the database and report back if and when it was
interrupted instead of just port monitoring or service monitoring.
Thanks
Jon
On Jun 1, 3:29 pm, "Lucas Kartawidjaja" <luk...@.hotmail.com> wrote:[vbcol=seagreen]
> Try this tool:http://www.paessler.com/ipcheck/download
> It has a free version that can be use to check every 15 minutes.
> Thank you
> Lucas
> <lava...@.gmail.com> wrote in message
> news:1180719965.172880.52790@.g4g2000hsf.googlegrou ps.com...
>
|||So - write a little script that loops until an error is encountered and does
nothing but execute some sort of trivial statement. Use QA (or SMS or isql
or whatever tool you have) to execute it. You may want to look up WAITFOR
in BOL. Or perhaps just set up the profiler to monitor the dbms.
sql

Intermittent Connection Issue - How to Monitor

We have a 3rd party application which uses a connection to a SQL
Server 2005 database. It intermittently loses connnection to the
database and displays an error. The vendor is playing hardball with
resolving the issues. What we would like to do is have a small
application that can run on the machine the client applilcation is
installed on and make connection checks and logs. This way if both
loose connection we can rule out the 3rd party software as being the
issue. However, if theirs looses connection and the monitor
application does not notice anything we can use that information as
leverage for dealing with the vendor.
Is there any such application out there that would do this?
Thanks in advance.Try this tool:
http://www.paessler.com/ipcheck/download
It has a free version that can be use to check every 15 minutes.
Thank you
Lucas
<lavaice@.gmail.com> wrote in message
news:1180719965.172880.52790@.g4g2000hsf.googlegroups.com...
> We have a 3rd party application which uses a connection to a SQL
> Server 2005 database. It intermittently loses connnection to the
> database and displays an error. The vendor is playing hardball with
> resolving the issues. What we would like to do is have a small
> application that can run on the machine the client applilcation is
> installed on and make connection checks and logs. This way if both
> loose connection we can rule out the 3rd party software as being the
> issue. However, if theirs looses connection and the monitor
> application does not notice anything we can use that information as
> leverage for dealing with the vendor.
> Is there any such application out there that would do this?
> Thanks in advance.
>

Intermittent Connection Issue - How to Monitor

We have a 3rd party application which uses a connection to a SQL
Server 2005 database. It intermittently loses connnection to the
database and displays an error. The vendor is playing hardball with
resolving the issues. What we would like to do is have a small
application that can run on the machine the client applilcation is
installed on and make connection checks and logs. This way if both
loose connection we can rule out the 3rd party software as being the
issue. However, if theirs looses connection and the monitor
application does not notice anything we can use that information as
leverage for dealing with the vendor.
Is there any such application out there that would do this?
Thanks in advance.Try this tool:
http://www.paessler.com/ipcheck/download
It has a free version that can be use to check every 15 minutes.
Thank you
Lucas
<lavaice@.gmail.com> wrote in message
news:1180719965.172880.52790@.g4g2000hsf.googlegroups.com...
> We have a 3rd party application which uses a connection to a SQL
> Server 2005 database. It intermittently loses connnection to the
> database and displays an error. The vendor is playing hardball with
> resolving the issues. What we would like to do is have a small
> application that can run on the machine the client applilcation is
> installed on and make connection checks and logs. This way if both
> loose connection we can rule out the 3rd party software as being the
> issue. However, if theirs looses connection and the monitor
> application does not notice anything we can use that information as
> leverage for dealing with the vendor.
> Is there any such application out there that would do this?
> Thanks in advance.
>|||What we are looking for is something that would actually establish a
SQL connection to the database and report back if and when it was
interrupted instead of just port monitoring or service monitoring.
Thanks
Jon
On Jun 1, 3:29 pm, "Lucas Kartawidjaja" <luk...@.hotmail.com> wrote:
> Try this tool:http://www.paessler.com/ipcheck/download
> It has a free version that can be use to check every 15 minutes.
> Thank you
> Lucas
> <lava...@.gmail.com> wrote in message
> news:1180719965.172880.52790@.g4g2000hsf.googlegroups.com...
> > We have a 3rd party application which uses a connection to a SQL
> > Server 2005 database. It intermittently loses connnection to the
> > database and displays an error. The vendor is playing hardball with
> > resolving the issues. What we would like to do is have a small
> > application that can run on the machine the client applilcation is
> > installed on and make connection checks and logs. This way if both
> > loose connection we can rule out the 3rd party software as being the
> > issue. However, if theirs looses connection and the monitor
> > application does not notice anything we can use that information as
> > leverage for dealing with the vendor.
> > Is there any such application out there that would do this?
> > Thanks in advance.|||So - write a little script that loops until an error is encountered and does
nothing but execute some sort of trivial statement. Use QA (or SMS or isql
or whatever tool you have) to execute it. You may want to look up WAITFOR
in BOL. Or perhaps just set up the profiler to monitor the dbms.

Intermitent problem : New transaction cannot enlist in the specified transaction coordinat

I have a Windows 2003 Application Server. When I dont use the
Application for about 15 minutes, I get the error : "New transaction
cannot enlist in the specified transaction coordinator" when trying to
do a transaction with the Database server.
When I got the error, if I keep trying to do a transaction, eventually
the transaction process restart to work until I keep it inactive for
about 15 minutes.
I did some test with the application and with DTCTester. When it dont
work with the application it dont work with DTCTester
(http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
- The application server is Windows 2003 SP1
- This server connect to a Cluster SQL Server 2000 database intalled on
Windows 2003 servers .
- The two servers are in two differents Network zone.
- All ports are opened between Database servers and application
servers.
- MSDTC is started on the Application and Database server.
- In security configuration of MSDTC of the Application server the
option "No Authentication Required is selected". This option is not
selected on the Database server because the service pack 1 is not
installed.
- Database computers names are in the host file of the application
server and application server name is in the host file of the SQL
Server.
I did some test with another Database server (SQL Server 2000 on
windows 2000) and it always works, but these two server are in the same
zone.
I would like to know if someone have an idea why the transaction stop
to works after about 15 minutes and restart to work if I keep trying.
Thank you very much.
DavidHi Dave
I am not sure what you mean by different zones? Is this a different sub-net?
It is not clear if you are seeing exactly the same symptoms with DTC tester
or if it never works?
As the problem is intermittent it sounds like a network type issue rather
than the components. You may want to try changing network cards and
hubs/switches to see if it continues to fail. Also if there are any firewalls
make sure they are configured correctly, also make sure that no antivirus or
intrusion detection software is causing a conflict.
John
"Dave960" wrote:
> I have a Windows 2003 Application Server. When I dont use the
> Application for about 15 minutes, I get the error : "New transaction
> cannot enlist in the specified transaction coordinator" when trying to
> do a transaction with the Database server.
> When I got the error, if I keep trying to do a transaction, eventually
> the transaction process restart to work until I keep it inactive for
> about 15 minutes.
> I did some test with the application and with DTCTester. When it dont
> work with the application it dont work with DTCTester
> (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> - The application server is Windows 2003 SP1
> - This server connect to a Cluster SQL Server 2000 database intalled on
> Windows 2003 servers .
> - The two servers are in two differents Network zone.
> - All ports are opened between Database servers and application
> servers.
> - MSDTC is started on the Application and Database server.
> - In security configuration of MSDTC of the Application server the
> option "No Authentication Required is selected". This option is not
> selected on the Database server because the service pack 1 is not
> installed.
> - Database computers names are in the host file of the application
> server and application server name is in the host file of the SQL
> Server.
>
> I did some test with another Database server (SQL Server 2000 on
> windows 2000) and it always works, but these two server are in the same
> zone.
> I would like to know if someone have an idea why the transaction stop
> to works after about 15 minutes and restart to work if I keep trying.
> Thank you very much.
> David
>|||Hi John,
Thank's for your reply :)
- By different zone I mean different sub-net.
- I'm seeing exactly the same problem with dtctester. After a couple of
try it work's and if I do nothing for about 15 minutes it stop to work
until I try dtctester for a couple of try ( 2 to 20).
If I run a transaction between the application server and the SQL
server every 5-10 minutes, transaction always work.
The transaction process always work with another Database server
(Server2) in the same zone as my application server, so I think it's
not hardware related. But there is difference with this second server,
it run on windows 2000 and is not in a cluster.
If I do the dtctester test with the Database server (Server1 - the one
that I have problem with) with another application server in the Dabase
server sub-net it always works.
Another thing, I'm always able to retrieve data from the Database
server, I just have problem with transactions.
>From what I see it look like a network problem, but I dont see why
after about 15 minutes of inactivity it strop to work ?
If you have any ideas, let me know.
Thanks a lot.
David
It look similar to this problem :
http://groups.google.ca/group/microsoft.public.platformsdk.complus_mts/browse_thread/thread/da9b915896c6d8a1/66b4518597052cfb?lnk=st&q=&rnum=1&hl=en#66b4518597052cfb
John Bell wrote:
> Hi Dave
> I am not sure what you mean by different zones? Is this a different sub-net?
> It is not clear if you are seeing exactly the same symptoms with DTC tester
> or if it never works?
> As the problem is intermittent it sounds like a network type issue rather
> than the components. You may want to try changing network cards and
> hubs/switches to see if it continues to fail. Also if there are any firewalls
> make sure they are configured correctly, also make sure that no antivirus or
> intrusion detection software is causing a conflict.
> John
>
> "Dave960" wrote:
> > I have a Windows 2003 Application Server. When I dont use the
> > Application for about 15 minutes, I get the error : "New transaction
> > cannot enlist in the specified transaction coordinator" when trying to
> > do a transaction with the Database server.
> >
> > When I got the error, if I keep trying to do a transaction, eventually
> > the transaction process restart to work until I keep it inactive for
> > about 15 minutes.
> >
> > I did some test with the application and with DTCTester. When it dont
> > work with the application it dont work with DTCTester
> > (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> >
> > - The application server is Windows 2003 SP1
> >
> > - This server connect to a Cluster SQL Server 2000 database intalled on
> > Windows 2003 servers .
> >
> > - The two servers are in two differents Network zone.
> >
> > - All ports are opened between Database servers and application
> > servers.
> >
> > - MSDTC is started on the Application and Database server.
> >
> > - In security configuration of MSDTC of the Application server the
> > option "No Authentication Required is selected". This option is not
> > selected on the Database server because the service pack 1 is not
> > installed.
> >
> > - Database computers names are in the host file of the application
> > server and application server name is in the host file of the SQL
> > Server.
> >
> >
> >
> > I did some test with another Database server (SQL Server 2000 on
> > windows 2000) and it always works, but these two server are in the same
> > zone.
> >
> > I would like to know if someone have an idea why the transaction stop
> > to works after about 15 minutes and restart to work if I keep trying.
> >
> > Thank you very much.
> >
> > David
> >
> >|||Hi Dave
It is not clear why you need a distributed transaction, from what you say it
is only
the one server being used at any one time?
John
"Dave960" wrote:
> Hi John,
> Thank's for your reply :)
> - By different zone I mean different sub-net.
> - I'm seeing exactly the same problem with dtctester. After a couple of
> try it work's and if I do nothing for about 15 minutes it stop to work
> until I try dtctester for a couple of try ( 2 to 20).
> If I run a transaction between the application server and the SQL
> server every 5-10 minutes, transaction always work.
> The transaction process always work with another Database server
> (Server2) in the same zone as my application server, so I think it's
> not hardware related. But there is difference with this second server,
> it run on windows 2000 and is not in a cluster.
> If I do the dtctester test with the Database server (Server1 - the one
> that I have problem with) with another application server in the Dabase
> server sub-net it always works.
> Another thing, I'm always able to retrieve data from the Database
> server, I just have problem with transactions.
> >From what I see it look like a network problem, but I dont see why
> after about 15 minutes of inactivity it strop to work ?
> If you have any ideas, let me know.
> Thanks a lot.
> David
>
> It look similar to this problem :
> http://groups.google.ca/group/microsoft.public.platformsdk.complus_mts/browse_thread/thread/da9b915896c6d8a1/66b4518597052cfb?lnk=st&q=&rnum=1&hl=en#66b4518597052cfb
> John Bell wrote:
> > Hi Dave
> >
> > I am not sure what you mean by different zones? Is this a different sub-net?
> > It is not clear if you are seeing exactly the same symptoms with DTC tester
> > or if it never works?
> >
> > As the problem is intermittent it sounds like a network type issue rather
> > than the components. You may want to try changing network cards and
> > hubs/switches to see if it continues to fail. Also if there are any firewalls
> > make sure they are configured correctly, also make sure that no antivirus or
> > intrusion detection software is causing a conflict.
> >
> > John
> >
> >
> > "Dave960" wrote:
> >
> > > I have a Windows 2003 Application Server. When I dont use the
> > > Application for about 15 minutes, I get the error : "New transaction
> > > cannot enlist in the specified transaction coordinator" when trying to
> > > do a transaction with the Database server.
> > >
> > > When I got the error, if I keep trying to do a transaction, eventually
> > > the transaction process restart to work until I keep it inactive for
> > > about 15 minutes.
> > >
> > > I did some test with the application and with DTCTester. When it dont
> > > work with the application it dont work with DTCTester
> > > (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> > >
> > > - The application server is Windows 2003 SP1
> > >
> > > - This server connect to a Cluster SQL Server 2000 database intalled on
> > > Windows 2003 servers .
> > >
> > > - The two servers are in two differents Network zone.
> > >
> > > - All ports are opened between Database servers and application
> > > servers.
> > >
> > > - MSDTC is started on the Application and Database server.
> > >
> > > - In security configuration of MSDTC of the Application server the
> > > option "No Authentication Required is selected". This option is not
> > > selected on the Database server because the service pack 1 is not
> > > installed.
> > >
> > > - Database computers names are in the host file of the application
> > > server and application server name is in the host file of the SQL
> > > Server.
> > >
> > >
> > >
> > > I did some test with another Database server (SQL Server 2000 on
> > > windows 2000) and it always works, but these two server are in the same
> > > zone.
> > >
> > > I would like to know if someone have an idea why the transaction stop
> > > to works after about 15 minutes and restart to work if I keep trying.
> > >
> > > Thank you very much.
> > >
> > > David
> > >
> > >
>|||Hi John,
The application server run COM+ components that use distributed
transaction for certain type of query to the database.
This application is already running on another server, we just want to
switch this application to a new server that is in a different sub-net.
If there's missing informations, dont hesitate to ask me.
Thanks !!!
David
John Bell wrote:
> Hi Dave
> It is not clear why you need a distributed transaction, from what you say it
> is only
> the one server being used at any one time?
> John
>
> "Dave960" wrote:
> > Hi John,
> >
> > Thank's for your reply :)
> >
> > - By different zone I mean different sub-net.
> > - I'm seeing exactly the same problem with dtctester. After a couple of
> > try it work's and if I do nothing for about 15 minutes it stop to work
> > until I try dtctester for a couple of try ( 2 to 20).
> >
> > If I run a transaction between the application server and the SQL
> > server every 5-10 minutes, transaction always work.
> >
> > The transaction process always work with another Database server
> > (Server2) in the same zone as my application server, so I think it's
> > not hardware related. But there is difference with this second server,
> > it run on windows 2000 and is not in a cluster.
> >
> > If I do the dtctester test with the Database server (Server1 - the one
> > that I have problem with) with another application server in the Dabase
> > server sub-net it always works.
> >
> > Another thing, I'm always able to retrieve data from the Database
> > server, I just have problem with transactions.
> >
> > >From what I see it look like a network problem, but I dont see why
> > after about 15 minutes of inactivity it strop to work ?
> >
> > If you have any ideas, let me know.
> >
> > Thanks a lot.
> >
> > David
> >
> >
> > It look similar to this problem :
> > http://groups.google.ca/group/microsoft.public.platformsdk.complus_mts/browse_thread/thread/da9b915896c6d8a1/66b4518597052cfb?lnk=st&q=&rnum=1&hl=en#66b4518597052cfb
> >
> > John Bell wrote:
> > > Hi Dave
> > >
> > > I am not sure what you mean by different zones? Is this a different sub-net?
> > > It is not clear if you are seeing exactly the same symptoms with DTC tester
> > > or if it never works?
> > >
> > > As the problem is intermittent it sounds like a network type issue rather
> > > than the components. You may want to try changing network cards and
> > > hubs/switches to see if it continues to fail. Also if there are any firewalls
> > > make sure they are configured correctly, also make sure that no antivirus or
> > > intrusion detection software is causing a conflict.
> > >
> > > John
> > >
> > >
> > > "Dave960" wrote:
> > >
> > > > I have a Windows 2003 Application Server. When I dont use the
> > > > Application for about 15 minutes, I get the error : "New transaction
> > > > cannot enlist in the specified transaction coordinator" when trying to
> > > > do a transaction with the Database server.
> > > >
> > > > When I got the error, if I keep trying to do a transaction, eventually
> > > > the transaction process restart to work until I keep it inactive for
> > > > about 15 minutes.
> > > >
> > > > I did some test with the application and with DTCTester. When it dont
> > > > work with the application it dont work with DTCTester
> > > > (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> > > >
> > > > - The application server is Windows 2003 SP1
> > > >
> > > > - This server connect to a Cluster SQL Server 2000 database intalled on
> > > > Windows 2003 servers .
> > > >
> > > > - The two servers are in two differents Network zone.
> > > >
> > > > - All ports are opened between Database servers and application
> > > > servers.
> > > >
> > > > - MSDTC is started on the Application and Database server.
> > > >
> > > > - In security configuration of MSDTC of the Application server the
> > > > option "No Authentication Required is selected". This option is not
> > > > selected on the Database server because the service pack 1 is not
> > > > installed.
> > > >
> > > > - Database computers names are in the host file of the application
> > > > server and application server name is in the host file of the SQL
> > > > Server.
> > > >
> > > >
> > > >
> > > > I did some test with another Database server (SQL Server 2000 on
> > > > windows 2000) and it always works, but these two server are in the same
> > > > zone.
> > > >
> > > > I would like to know if someone have an idea why the transaction stop
> > > > to works after about 15 minutes and restart to work if I keep trying.
> > > >
> > > > Thank you very much.
> > > >
> > > > David
> > > >
> > > >
> >
> >|||Hi Dave
As this is intermitten, it implies that it is set up correctly and something
other than SQL Server is causing this to fail. Have you checked for intrusion
detection or virus checkers being active at this time?
John
"Dave960" wrote:
> Hi John,
> The application server run COM+ components that use distributed
> transaction for certain type of query to the database.
> This application is already running on another server, we just want to
> switch this application to a new server that is in a different sub-net.
> If there's missing informations, dont hesitate to ask me.
> Thanks !!!
> David
>
> John Bell wrote:
> > Hi Dave
> >
> > It is not clear why you need a distributed transaction, from what you say it
> > is only
> > the one server being used at any one time?
> >
> > John
> >
> >
> >
> > "Dave960" wrote:
> >
> > > Hi John,
> > >
> > > Thank's for your reply :)
> > >
> > > - By different zone I mean different sub-net.
> > > - I'm seeing exactly the same problem with dtctester. After a couple of
> > > try it work's and if I do nothing for about 15 minutes it stop to work
> > > until I try dtctester for a couple of try ( 2 to 20).
> > >
> > > If I run a transaction between the application server and the SQL
> > > server every 5-10 minutes, transaction always work.
> > >
> > > The transaction process always work with another Database server
> > > (Server2) in the same zone as my application server, so I think it's
> > > not hardware related. But there is difference with this second server,
> > > it run on windows 2000 and is not in a cluster.
> > >
> > > If I do the dtctester test with the Database server (Server1 - the one
> > > that I have problem with) with another application server in the Dabase
> > > server sub-net it always works.
> > >
> > > Another thing, I'm always able to retrieve data from the Database
> > > server, I just have problem with transactions.
> > >
> > > >From what I see it look like a network problem, but I dont see why
> > > after about 15 minutes of inactivity it strop to work ?
> > >
> > > If you have any ideas, let me know.
> > >
> > > Thanks a lot.
> > >
> > > David
> > >
> > >
> > > It look similar to this problem :
> > > http://groups.google.ca/group/microsoft.public.platformsdk.complus_mts/browse_thread/thread/da9b915896c6d8a1/66b4518597052cfb?lnk=st&q=&rnum=1&hl=en#66b4518597052cfb
> > >
> > > John Bell wrote:
> > > > Hi Dave
> > > >
> > > > I am not sure what you mean by different zones? Is this a different sub-net?
> > > > It is not clear if you are seeing exactly the same symptoms with DTC tester
> > > > or if it never works?
> > > >
> > > > As the problem is intermittent it sounds like a network type issue rather
> > > > than the components. You may want to try changing network cards and
> > > > hubs/switches to see if it continues to fail. Also if there are any firewalls
> > > > make sure they are configured correctly, also make sure that no antivirus or
> > > > intrusion detection software is causing a conflict.
> > > >
> > > > John
> > > >
> > > >
> > > > "Dave960" wrote:
> > > >
> > > > > I have a Windows 2003 Application Server. When I dont use the
> > > > > Application for about 15 minutes, I get the error : "New transaction
> > > > > cannot enlist in the specified transaction coordinator" when trying to
> > > > > do a transaction with the Database server.
> > > > >
> > > > > When I got the error, if I keep trying to do a transaction, eventually
> > > > > the transaction process restart to work until I keep it inactive for
> > > > > about 15 minutes.
> > > > >
> > > > > I did some test with the application and with DTCTester. When it dont
> > > > > work with the application it dont work with DTCTester
> > > > > (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> > > > >
> > > > > - The application server is Windows 2003 SP1
> > > > >
> > > > > - This server connect to a Cluster SQL Server 2000 database intalled on
> > > > > Windows 2003 servers .
> > > > >
> > > > > - The two servers are in two differents Network zone.
> > > > >
> > > > > - All ports are opened between Database servers and application
> > > > > servers.
> > > > >
> > > > > - MSDTC is started on the Application and Database server.
> > > > >
> > > > > - In security configuration of MSDTC of the Application server the
> > > > > option "No Authentication Required is selected". This option is not
> > > > > selected on the Database server because the service pack 1 is not
> > > > > installed.
> > > > >
> > > > > - Database computers names are in the host file of the application
> > > > > server and application server name is in the host file of the SQL
> > > > > Server.
> > > > >
> > > > >
> > > > >
> > > > > I did some test with another Database server (SQL Server 2000 on
> > > > > windows 2000) and it always works, but these two server are in the same
> > > > > zone.
> > > > >
> > > > > I would like to know if someone have an idea why the transaction stop
> > > > > to works after about 15 minutes and restart to work if I keep trying.
> > > > >
> > > > > Thank you very much.
> > > > >
> > > > > David
> > > > >
> > > > >
> > >
> > >
>|||Hi Dave
You may also want to check out
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306843
John
"Dave960" wrote:
> Hi John,
> The application server run COM+ components that use distributed
> transaction for certain type of query to the database.
> This application is already running on another server, we just want to
> switch this application to a new server that is in a different sub-net.
> If there's missing informations, dont hesitate to ask me.
> Thanks !!!
> David
>
> John Bell wrote:
> > Hi Dave
> >
> > It is not clear why you need a distributed transaction, from what you say it
> > is only
> > the one server being used at any one time?
> >
> > John
> >
> >
> >
> > "Dave960" wrote:
> >
> > > Hi John,
> > >
> > > Thank's for your reply :)
> > >
> > > - By different zone I mean different sub-net.
> > > - I'm seeing exactly the same problem with dtctester. After a couple of
> > > try it work's and if I do nothing for about 15 minutes it stop to work
> > > until I try dtctester for a couple of try ( 2 to 20).
> > >
> > > If I run a transaction between the application server and the SQL
> > > server every 5-10 minutes, transaction always work.
> > >
> > > The transaction process always work with another Database server
> > > (Server2) in the same zone as my application server, so I think it's
> > > not hardware related. But there is difference with this second server,
> > > it run on windows 2000 and is not in a cluster.
> > >
> > > If I do the dtctester test with the Database server (Server1 - the one
> > > that I have problem with) with another application server in the Dabase
> > > server sub-net it always works.
> > >
> > > Another thing, I'm always able to retrieve data from the Database
> > > server, I just have problem with transactions.
> > >
> > > >From what I see it look like a network problem, but I dont see why
> > > after about 15 minutes of inactivity it strop to work ?
> > >
> > > If you have any ideas, let me know.
> > >
> > > Thanks a lot.
> > >
> > > David
> > >
> > >
> > > It look similar to this problem :
> > > http://groups.google.ca/group/microsoft.public.platformsdk.complus_mts/browse_thread/thread/da9b915896c6d8a1/66b4518597052cfb?lnk=st&q=&rnum=1&hl=en#66b4518597052cfb
> > >
> > > John Bell wrote:
> > > > Hi Dave
> > > >
> > > > I am not sure what you mean by different zones? Is this a different sub-net?
> > > > It is not clear if you are seeing exactly the same symptoms with DTC tester
> > > > or if it never works?
> > > >
> > > > As the problem is intermittent it sounds like a network type issue rather
> > > > than the components. You may want to try changing network cards and
> > > > hubs/switches to see if it continues to fail. Also if there are any firewalls
> > > > make sure they are configured correctly, also make sure that no antivirus or
> > > > intrusion detection software is causing a conflict.
> > > >
> > > > John
> > > >
> > > >
> > > > "Dave960" wrote:
> > > >
> > > > > I have a Windows 2003 Application Server. When I dont use the
> > > > > Application for about 15 minutes, I get the error : "New transaction
> > > > > cannot enlist in the specified transaction coordinator" when trying to
> > > > > do a transaction with the Database server.
> > > > >
> > > > > When I got the error, if I keep trying to do a transaction, eventually
> > > > > the transaction process restart to work until I keep it inactive for
> > > > > about 15 minutes.
> > > > >
> > > > > I did some test with the application and with DTCTester. When it dont
> > > > > work with the application it dont work with DTCTester
> > > > > (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> > > > >
> > > > > - The application server is Windows 2003 SP1
> > > > >
> > > > > - This server connect to a Cluster SQL Server 2000 database intalled on
> > > > > Windows 2003 servers .
> > > > >
> > > > > - The two servers are in two differents Network zone.
> > > > >
> > > > > - All ports are opened between Database servers and application
> > > > > servers.
> > > > >
> > > > > - MSDTC is started on the Application and Database server.
> > > > >
> > > > > - In security configuration of MSDTC of the Application server the
> > > > > option "No Authentication Required is selected". This option is not
> > > > > selected on the Database server because the service pack 1 is not
> > > > > installed.
> > > > >
> > > > > - Database computers names are in the host file of the application
> > > > > server and application server name is in the host file of the SQL
> > > > > Server.
> > > > >
> > > > >
> > > > >
> > > > > I did some test with another Database server (SQL Server 2000 on
> > > > > windows 2000) and it always works, but these two server are in the same
> > > > > zone.
> > > > >
> > > > > I would like to know if someone have an idea why the transaction stop
> > > > > to works after about 15 minutes and restart to work if I keep trying.
> > > > >
> > > > > Thank you very much.
> > > > >
> > > > > David
> > > > >
> > > > >
> > >
> > >
>|||Hi John,
- I have the same problem if I desactivate the Antivirus sofware.
- I already follow the steps list in this link and DTCPing always
works.
If you have any other ideas, let me know.
Thanks
David
John Bell wrote:
> Hi Dave
> You may also want to check out
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306843
> John
> "Dave960" wrote:
> > Hi John,
> >
> > The application server run COM+ components that use distributed
> > transaction for certain type of query to the database.
> >
> > This application is already running on another server, we just want to
> > switch this application to a new server that is in a different sub-net.
> >
> > If there's missing informations, dont hesitate to ask me.
> >
> > Thanks !!!
> >
> > David
> >
> >
> > John Bell wrote:
> > > Hi Dave
> > >
> > > It is not clear why you need a distributed transaction, from what you say it
> > > is only
> > > the one server being used at any one time?
> > >
> > > John
> > >
> > >
> > >
> > > "Dave960" wrote:
> > >
> > > > Hi John,
> > > >
> > > > Thank's for your reply :)
> > > >
> > > > - By different zone I mean different sub-net.
> > > > - I'm seeing exactly the same problem with dtctester. After a couple of
> > > > try it work's and if I do nothing for about 15 minutes it stop to work
> > > > until I try dtctester for a couple of try ( 2 to 20).
> > > >
> > > > If I run a transaction between the application server and the SQL
> > > > server every 5-10 minutes, transaction always work.
> > > >
> > > > The transaction process always work with another Database server
> > > > (Server2) in the same zone as my application server, so I think it's
> > > > not hardware related. But there is difference with this second server,
> > > > it run on windows 2000 and is not in a cluster.
> > > >
> > > > If I do the dtctester test with the Database server (Server1 - the one
> > > > that I have problem with) with another application server in the Dabase
> > > > server sub-net it always works.
> > > >
> > > > Another thing, I'm always able to retrieve data from the Database
> > > > server, I just have problem with transactions.
> > > >
> > > > >From what I see it look like a network problem, but I dont see why
> > > > after about 15 minutes of inactivity it strop to work ?
> > > >
> > > > If you have any ideas, let me know.
> > > >
> > > > Thanks a lot.
> > > >
> > > > David
> > > >
> > > >
> > > > It look similar to this problem :
> > > > http://groups.google.ca/group/microsoft.public.platformsdk.complus_mts/browse_thread/thread/da9b915896c6d8a1/66b4518597052cfb?lnk=st&q=&rnum=1&hl=en#66b4518597052cfb
> > > >
> > > > John Bell wrote:
> > > > > Hi Dave
> > > > >
> > > > > I am not sure what you mean by different zones? Is this a different sub-net?
> > > > > It is not clear if you are seeing exactly the same symptoms with DTC tester
> > > > > or if it never works?
> > > > >
> > > > > As the problem is intermittent it sounds like a network type issue rather
> > > > > than the components. You may want to try changing network cards and
> > > > > hubs/switches to see if it continues to fail. Also if there are any firewalls
> > > > > make sure they are configured correctly, also make sure that no antivirus or
> > > > > intrusion detection software is causing a conflict.
> > > > >
> > > > > John
> > > > >
> > > > >
> > > > > "Dave960" wrote:
> > > > >
> > > > > > I have a Windows 2003 Application Server. When I dont use the
> > > > > > Application for about 15 minutes, I get the error : "New transaction
> > > > > > cannot enlist in the specified transaction coordinator" when trying to
> > > > > > do a transaction with the Database server.
> > > > > >
> > > > > > When I got the error, if I keep trying to do a transaction, eventually
> > > > > > the transaction process restart to work until I keep it inactive for
> > > > > > about 15 minutes.
> > > > > >
> > > > > > I did some test with the application and with DTCTester. When it dont
> > > > > > work with the application it dont work with DTCTester
> > > > > > (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> > > > > >
> > > > > > - The application server is Windows 2003 SP1
> > > > > >
> > > > > > - This server connect to a Cluster SQL Server 2000 database intalled on
> > > > > > Windows 2003 servers .
> > > > > >
> > > > > > - The two servers are in two differents Network zone.
> > > > > >
> > > > > > - All ports are opened between Database servers and application
> > > > > > servers.
> > > > > >
> > > > > > - MSDTC is started on the Application and Database server.
> > > > > >
> > > > > > - In security configuration of MSDTC of the Application server the
> > > > > > option "No Authentication Required is selected". This option is not
> > > > > > selected on the Database server because the service pack 1 is not
> > > > > > installed.
> > > > > >
> > > > > > - Database computers names are in the host file of the application
> > > > > > server and application server name is in the host file of the SQL
> > > > > > Server.
> > > > > >
> > > > > >
> > > > > >
> > > > > > I did some test with another Database server (SQL Server 2000 on
> > > > > > windows 2000) and it always works, but these two server are in the same
> > > > > > zone.
> > > > > >
> > > > > > I would like to know if someone have an idea why the transaction stop
> > > > > > to works after about 15 minutes and restart to work if I keep trying.
> > > > > >
> > > > > > Thank you very much.
> > > > > >
> > > > > > David
> > > > > >
> > > > > >
> > > >
> > > >
> >
> >