[ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired] 
Author Message
 [ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired]

I recently upgraded my Server (new machine) and copied our companies
exsisting website to it.
Our website has a lot of database connectivity using ASP.
My installation is the following: PROLIANT 5500 512Mb 27Gb Raid 5 -> NT4SP6
NTOP SQL7 SS3C-SP3.
The only difference on this install which differs from my last is that I
have NTSP6.
The same code that I had before which worked great is now cauing SQL
Timeouts to dozens of my customers.
I've experienced it myself, however its not like it hangs for a few seconds
and returns the timeout, it just returns the Timeout immediatly.
If I click refresh it works fine. Its really hard to reproduce & I don't
know whats causing it.
I've set the CommandTimeout to 30 seconds in most of my code but it doesn't
seem to help.
Has anyone experienced this problem or have any suggestions?

Thanks,

Alberto.

The exact error says:

Microsoft OLE DB Provider for ODBC Drivers error '80040e14'

[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
message: Timeout expired]

/configurator/default.asp, line 39    <-- Pointing to line which executed
the db connection.

----------------------------------------------------------------------------
----------------------------------

cmdDS.CommandText = "WCFG_CreateQuoteHeader"
  Set prm = cmdDS.CreateParameter("UserCode", adInteger, adParamInput, ,
UserCode)
  cmdDS.Parameters.Append prm
  Set prm = cmdDS.CreateParameter("QuoteID", adInteger, adParamOutput)
  cmdDS.Parameters.Append prm
Set rs = cmdDS.Execute            <--- Line 39



Tue, 07 May 2002 03:00:00 GMT
 [ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired]

Thank you !



Quote:
> I recently upgraded my Server (new machine) and copied our companies
> exsisting website to it.
> Our website has a lot of database connectivity using ASP.
> My installation is the following: PROLIANT 5500 512Mb 27Gb Raid 5 ->
NT4SP6
> NTOP SQL7 SS3C-SP3.
> The only difference on this install which differs from my last is that I
> have NTSP6.
> The same code that I had before which worked great is now cauing SQL
> Timeouts to dozens of my customers.
> I've experienced it myself, however its not like it hangs for a few
seconds
> and returns the timeout, it just returns the Timeout immediatly.
> If I click refresh it works fine. Its really hard to reproduce & I don't
> know whats causing it.
> I've set the CommandTimeout to 30 seconds in most of my code but it
doesn't
> seem to help.
> Has anyone experienced this problem or have any suggestions?

> Thanks,

> Alberto.

> The exact error says:

> Microsoft OLE DB Provider for ODBC Drivers error '80040e14'

> [Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
> message: Timeout expired]

> /configurator/default.asp, line 39    <-- Pointing to line which executed
> the db connection.

> --------------------------------------------------------------------------
--
> ----------------------------------

> cmdDS.CommandText = "WCFG_CreateQuoteHeader"
>   Set prm = cmdDS.CreateParameter("UserCode", adInteger, adParamInput, ,
> UserCode)
>   cmdDS.Parameters.Append prm
>   Set prm = cmdDS.CreateParameter("QuoteID", adInteger, adParamOutput)
>   cmdDS.Parameters.Append prm
> Set rs = cmdDS.Execute            <--- Line 39



Wed, 08 May 2002 03:00:00 GMT
 [ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired]
I had a problem when I upgraded to MDAC 2.1 SP2 4202.3 and NT SP5 which made
my existing code crash with a "Fatal Error" message from OLE DB.

None of my asp code which made connections to SQL worked. I went back to
MDAC 2.1 SP1 3711.9 and the error ceased. There are several theories on
this: the required installation order and a bug on MDAC SP2.

Why am I pointing to MDAC as a suspect? Because if your code worked fine
before and SP6 brought about the problem, it could only be due to something
related to the SQL drivers or OLEDB drivers.

Which MDAC service pack are you using? Check the version tab on the
properties of the msado15.dll under c:/Program Files/Common
Files/System/ado/msado15.dll.

To uninstall then MDAC dlls use the ClsIdView utility available somewhere on
microsoft.com

Hope this helps.



Thu, 09 May 2002 03:00:00 GMT
 [ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired]
Bernardo-
  We're having problems with MDAC 2.1 SP2 so I went to the MS web site in
search of ClsIDView utility you mentioned.  There are several references to
it, but the actual KB article from which you can download it no longer
exists!  Apparently MS determined that it was too useful to be giving away!

Bill


Quote:
> I had a problem when I upgraded to MDAC 2.1 SP2 4202.3 and NT SP5 which
made
> my existing code crash with a "Fatal Error" message from OLE DB.

> None of my asp code which made connections to SQL worked. I went back to
> MDAC 2.1 SP1 3711.9 and the error ceased. There are several theories on
> this: the required installation order and a bug on MDAC SP2.

> Why am I pointing to MDAC as a suspect? Because if your code worked fine
> before and SP6 brought about the problem, it could only be due to
something
> related to the SQL drivers or OLEDB drivers.

> Which MDAC service pack are you using? Check the version tab on the
> properties of the msado15.dll under c:/Program Files/Common
> Files/System/ado/msado15.dll.

> To uninstall then MDAC dlls use the ClsIdView utility available somewhere
on
> microsoft.com

> Hope this helps.



Thu, 09 May 2002 03:00:00 GMT
 [ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired]
Thanks for your help, I actually did install: MDAC 2.1 SP2 4202.3  based on
the recomendations written in:
http://support.microsoft.com/support/siteserver/install/ss3sp3/NT40-s...
p

My msado15.dll version says: 2.10.4202.1

I read Bill's response (next thread, about not having any luck finding
ClsIdView), do you (or anyone) have any
tips on what I should do?  Would downgrading my MDAC affect Site Server or
SQL7?

Thanks,

Alberto.


Quote:
> I had a problem when I upgraded to MDAC 2.1 SP2 4202.3 and NT SP5 which
made
> my existing code crash with a "Fatal Error" message from OLE DB.

> None of my asp code which made connections to SQL worked. I went back to
> MDAC 2.1 SP1 3711.9 and the error ceased. There are several theories on
> this: the required installation order and a bug on MDAC SP2.

> Why am I pointing to MDAC as a suspect? Because if your code worked fine
> before and SP6 brought about the problem, it could only be due to
something
> related to the SQL drivers or OLEDB drivers.

> Which MDAC service pack are you using? Check the version tab on the
> properties of the msado15.dll under c:/Program Files/Common
> Files/System/ado/msado15.dll.

> To uninstall then MDAC dlls use the ClsIdView utility available somewhere
on
> microsoft.com

> Hope this helps.



Fri, 10 May 2002 03:00:00 GMT
 [ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired]
I found it:
http://support.microsoft.com/download/support/mslfiles/CLSIDVW.EXE


Quote:
> Bernardo-
>   We're having problems with MDAC 2.1 SP2 so I went to the MS web site in
> search of ClsIDView utility you mentioned.  There are several references
to
> it, but the actual KB article from which you can download it no longer
> exists!  Apparently MS determined that it was too useful to be giving
away!

> Bill



> > I had a problem when I upgraded to MDAC 2.1 SP2 4202.3 and NT SP5 which
> made
> > my existing code crash with a "Fatal Error" message from OLE DB.

> > None of my asp code which made connections to SQL worked. I went back to
> > MDAC 2.1 SP1 3711.9 and the error ceased. There are several theories on
> > this: the required installation order and a bug on MDAC SP2.

> > Why am I pointing to MDAC as a suspect? Because if your code worked fine
> > before and SP6 brought about the problem, it could only be due to
> something
> > related to the SQL drivers or OLEDB drivers.

> > Which MDAC service pack are you using? Check the version tab on the
> > properties of the msado15.dll under c:/Program Files/Common
> > Files/System/ado/msado15.dll.

> > To uninstall then MDAC dlls use the ClsIdView utility available
somewhere
> on
> > microsoft.com

> > Hope this helps.



Fri, 10 May 2002 03:00:00 GMT
 [ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired]
ClsIdView will let you unregister (remove from the registry) and delete the
mdac 2.1 and odbc dlls. However, there are some tricks to using it. I'll
tell you what I did that worked.....there may be other ways but I didn't try
them.

1. With ClsIDView I unregistered and deleted everything I could MDAC, RDS,
ODBC, etc. There were some dll's that were being used by the system, so I
shut down and disabled all my related services (SQL, Certificate Server,
etc.) - I think I did a reboot too and got some messages in the event log.

2. Then I physically deleted all the files from the Program Files/Common
Files/System directory to make sure and did a reboot.

3. Then I installed MDAC 2.0 and got a different error - IIS wouldn't
respond.

4. Then I applied the MDAC 2.1 SP1 3711.9 and everything worked again. I was
back to the state in which I was before the SP2.

5. I tried applying SP2 again, and after half an hour of requesting files to
IIS got the same error I started with....so back to step 1.

6. After moving up to step 3, I skipped to step 5 and there it went
again......so once more to step 1.

7. I moved up to step 4 and left it there. Since then, I've had no problems.

Conclusion: No matter what, I'm not installing MDAC 2.1 SP2...........
--

Bernardo Cheing

Development Manager
Banco del Pacfico
Guayaquil, Ecuador



Sat, 11 May 2002 03:00:00 GMT
 [ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired]
Why is this posted on 11/23/2000 ?!?!?


Quote:
> The best way to uninstall MDAC is to call Microsoft Support and ask for a
> copy of "Component Checker".  Component Checker will uninstall the current
> version of MDAC on your machine and will install a prior version of MDAC
for
> you.

> Note, ClsIDView was build for MDAC 1.5 / 2.0.  It has never been updated
for
> MDAC 2.1., however,  there was an updated ClsIDView  INI file for  MDAC
2.1
> But IMHO, it wasn't a clean uninstall.

> Also, just because you unregister and delete the DLLs under "Program
> Files/Common Files/System directory" doesn't mean that you've un-installed
> MDAC.  Remember, MDAC also includes ODBC which is installed in your
system32
> directory.  Plus there are lots of MDAC keys in the system registry.  I
> would NOT recommend that you try this un-install by-hand trick. If you
don't
> know what you are doing, you will end up with a hosed machine and will
have
> to rebuilding it from scratch...

> Again, it best to call Microsoft Support on this one...

> --

> Thanks,
> Carl Prothman, MVP, CCP
> http://www.able-consulting.com



> > ClsIdView will let you unregister (remove from the registry) and delete
> the
> > mdac 2.1 and odbc dlls. However, there are some tricks to using it. I'll
> > tell you what I did that worked.....there may be other ways but I didn't
> try
> > them.

> > 1. With ClsIDView I unregistered and deleted everything I could MDAC,
RDS,
> > ODBC, etc. There were some dll's that were being used by the system, so
I
> > shut down and disabled all my related services (SQL, Certificate Server,
> > etc.) - I think I did a reboot too and got some messages in the event
log.

> > 2. Then I physically deleted all the files from the Program Files/Common
> > Files/System directory to make sure and did a reboot.

> > 3. Then I installed MDAC 2.0 and got a different error - IIS wouldn't
> > respond.

> > 4. Then I applied the MDAC 2.1 SP1 3711.9 and everything worked again. I
> was
> > back to the state in which I was before the SP2.

> > 5. I tried applying SP2 again, and after half an hour of requesting
files
> to
> > IIS got the same error I started with....so back to step 1.

> > 6. After moving up to step 3, I skipped to step 5 and there it went
> > again......so once more to step 1.

> > 7. I moved up to step 4 and left it there. Since then, I've had no
> problems.

> > Conclusion: No matter what, I'm not installing MDAC 2.1 SP2...........
> > --

> > Bernardo Cheing

> > Development Manager
> > Banco del Pacfico
> > Guayaquil, Ecuador



Tue, 25 Jun 2002 03:00:00 GMT
 [ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired]
Your date is screwed up too.


Quote:
> Why is this posted on 11/23/2000 ?!?!?



> > The best way to uninstall MDAC is to call Microsoft Support and ask for
a
> > copy of "Component Checker".  Component Checker will uninstall the
current
> > version of MDAC on your machine and will install a prior version of MDAC
> for
> > you.

> > Note, ClsIDView was build for MDAC 1.5 / 2.0.  It has never been updated
> for
> > MDAC 2.1., however,  there was an updated ClsIDView  INI file for  MDAC
> 2.1
> > But IMHO, it wasn't a clean uninstall.

> > Also, just because you unregister and delete the DLLs under "Program
> > Files/Common Files/System directory" doesn't mean that you've
un-installed
> > MDAC.  Remember, MDAC also includes ODBC which is installed in your
> system32
> > directory.  Plus there are lots of MDAC keys in the system registry.  I
> > would NOT recommend that you try this un-install by-hand trick. If you
> don't
> > know what you are doing, you will end up with a hosed machine and will
> have
> > to rebuilding it from scratch...

> > Again, it best to call Microsoft Support on this one...

> > --

> > Thanks,
> > Carl Prothman, MVP, CCP
> > http://www.able-consulting.com



> > > ClsIdView will let you unregister (remove from the registry) and
delete
> > the
> > > mdac 2.1 and odbc dlls. However, there are some tricks to using it.
I'll
> > > tell you what I did that worked.....there may be other ways but I
didn't
> > try
> > > them.

> > > 1. With ClsIDView I unregistered and deleted everything I could MDAC,
> RDS,
> > > ODBC, etc. There were some dll's that were being used by the system,
so
> I
> > > shut down and disabled all my related services (SQL, Certificate
Server,
> > > etc.) - I think I did a reboot too and got some messages in the event
> log.

> > > 2. Then I physically deleted all the files from the Program
Files/Common
> > > Files/System directory to make sure and did a reboot.

> > > 3. Then I installed MDAC 2.0 and got a different error - IIS wouldn't
> > > respond.

> > > 4. Then I applied the MDAC 2.1 SP1 3711.9 and everything worked again.
I
> > was
> > > back to the state in which I was before the SP2.

> > > 5. I tried applying SP2 again, and after half an hour of requesting
> files
> > to
> > > IIS got the same error I started with....so back to step 1.

> > > 6. After moving up to step 3, I skipped to step 5 and there it went
> > > again......so once more to step 1.

> > > 7. I moved up to step 4 and left it there. Since then, I've had no
> > problems.

> > > Conclusion: No matter what, I'm not installing MDAC 2.1 SP2...........
> > > --

> > > Bernardo Cheing

> > > Development Manager
> > > Banco del Pacfico
> > > Guayaquil, Ecuador



Sun, 07 Jul 2002 03:00:00 GMT
 [ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired]
Now if everyong changed their date to get on top that would really{*filter*}up
things... Now change your date.


Quote:
> The best way to uninstall MDAC is to call Microsoft Support and ask for a
> copy of "Component Checker".  Component Checker will uninstall the current
> version of MDAC on your machine and will install a prior version of MDAC
for
> you.

> Note, ClsIDView was build for MDAC 1.5 / 2.0.  It has never been updated
for
> MDAC 2.1., however,  there was an updated ClsIDView  INI file for  MDAC
2.1
> But IMHO, it wasn't a clean uninstall.

> Also, just because you unregister and delete the DLLs under "Program
> Files/Common Files/System directory" doesn't mean that you've un-installed
> MDAC.  Remember, MDAC also includes ODBC which is installed in your
system32
> directory.  Plus there are lots of MDAC keys in the system registry.  I
> would NOT recommend that you try this un-install by-hand trick. If you
don't
> know what you are doing, you will end up with a hosed machine and will
have
> to rebuilding it from scratch...

> Again, it best to call Microsoft Support on this one...

> --

> Thanks,
> Carl Prothman, MVP, CCP
> http://www.***.com/



> > ClsIdView will let you unregister (remove from the registry) and delete
> the
> > mdac 2.1 and odbc dlls. However, there are some tricks to using it. I'll
> > tell you what I did that worked.....there may be other ways but I didn't
> try
> > them.

> > 1. With ClsIDView I unregistered and deleted everything I could MDAC,
RDS,
> > ODBC, etc. There were some dll's that were being used by the system, so
I
> > shut down and disabled all my related services (SQL, Certificate Server,
> > etc.) - I think I did a reboot too and got some messages in the event
log.

> > 2. Then I physically deleted all the files from the Program Files/Common
> > Files/System directory to make sure and did a reboot.

> > 3. Then I installed MDAC 2.0 and got a different error - IIS wouldn't
> > respond.

> > 4. Then I applied the MDAC 2.1 SP1 3711.9 and everything worked again. I
> was
> > back to the state in which I was before the SP2.

> > 5. I tried applying SP2 again, and after half an hour of requesting
files
> to
> > IIS got the same error I started with....so back to step 1.

> > 6. After moving up to step 3, I skipped to step 5 and there it went
> > again......so once more to step 1.

> > 7. I moved up to step 4 and left it there. Since then, I've had no
> problems.

> > Conclusion: No matter what, I'm not installing MDAC 2.1 SP2...........
> > --

> > Bernardo Cheing

> > Development Manager
> > Banco del Pacfico
> > Guayaquil, Ecuador



Sun, 07 Jul 2002 03:00:00 GMT
 [ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired]
Sorry for the date on my post in this thread. It was during the time when I
was testing for Y2K issues...

I will have the MS Admin delete it from the server.

--

Thanks,
Carl Prothman, MVP, CCP
http://www.***.com/

ADO FAQ: http://www.***.com/
RDS FAQ: http://www.***.com/


Quote:
> Now if everyong changed their date to get on top that would really{*filter*}
up
> things... Now change your date.



> > The best way to uninstall MDAC is to call Microsoft Support and ask for
a
> > copy of "Component Checker".  Component Checker will uninstall the
current
> > version of MDAC on your machine and will install a prior version of MDAC
> for
> > you.

> > Note, ClsIDView was build for MDAC 1.5 / 2.0.  It has never been updated
> for
> > MDAC 2.1., however,  there was an updated ClsIDView  INI file for  MDAC
> 2.1
> > But IMHO, it wasn't a clean uninstall.

> > Also, just because you unregister and delete the DLLs under "Program
> > Files/Common Files/System directory" doesn't mean that you've
un-installed
> > MDAC.  Remember, MDAC also includes ODBC which is installed in your
> system32
> > directory.  Plus there are lots of MDAC keys in the system registry.  I
> > would NOT recommend that you try this un-install by-hand trick. If you
> don't
> > know what you are doing, you will end up with a hosed machine and will
> have
> > to rebuilding it from scratch...

> > Again, it best to call Microsoft Support on this one...

> > --

> > Thanks,
> > Carl Prothman, MVP, CCP
> > http://www.***.com/



> > > ClsIdView will let you unregister (remove from the registry) and delet
e
> > the
> > > mdac 2.1 and odbc dlls. However, there are some tricks to using it.
I'll
> > > tell you what I did that worked.....there may be other ways but I
didn't
> > try
> > > them.

> > > 1. With ClsIDView I unregistered and deleted everything I could MDAC,
> RDS,
> > > ODBC, etc. There were some dll's that were being used by the system,
so
> I
> > > shut down and disabled all my related services (SQL, Certificate
Server,
> > > etc.) - I think I did a reboot too and got some messages in the event
> log.

> > > 2. Then I physically deleted all the files from the Program
Files/Common
> > > Files/System directory to make sure and did a reboot.

> > > 3. Then I installed MDAC 2.0 and got a different error - IIS wouldn't
> > > respond.

> > > 4. Then I applied the MDAC 2.1 SP1 3711.9 and everything worked again.
I
> > was
> > > back to the state in which I was before the SP2.

> > > 5. I tried applying SP2 again, and after half an hour of requesting
> files
> > to
> > > IIS got the same error I started with....so back to step 1.

> > > 6. After moving up to step 3, I skipped to step 5 and there it went
> > > again......so once more to step 1.

> > > 7. I moved up to step 4 and left it there. Since then, I've had no
> > problems.

> > > Conclusion: No matter what, I'm not installing MDAC 2.1 SP2...........
> > > --

> > > Bernardo Cheing

> > > Development Manager
> > > Banco del Pacfico
> > > Guayaquil, Ecuador



Sun, 07 Jul 2002 03:00:00 GMT
 [ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired]
Please withdraw your reply because it's dated 11-23-2000 so it won't
disappear from my newsreader until the 26th of November this year.


Mon, 23 Sep 2002 03:00:00 GMT
 
 [ 12 post ] 

 Relevant Pages 

1. Help : OLE/DB provider returned message: Timeout expired

2. ERR: OLE/DB provider returned message: Timeout expired

3. Timeout Expired error from MS OLE DB Provider For SQL Server

4. Error -2147217871 from Microsoft OLE DB Provider for SQL Server: Timeout expire

5. Timeout expired error for MS OLE DB Provider for SQL Server

6. Error Type: Microsoft OLE DB Provider for SQL Server (0x80004005) Timeout expired

7. Timeout expired - OLE DB Provider for SQL Server

8. Timeout expired, [Microsoft OLE DB Provider for SQL Server]

9. Timeout expired, [Microsoft OLE DB Provider for SQL Server]

10. link server on sql server using ole db provider for odbc driver

11. odbc sql server driver timeout expired sql server 7.0

12. Oracle /MS-SQL Linked Server - OLE/DB provider returned message: ORA-12154


 
Powered by phpBB® Forum Software