[Venting]

So I have this box with SQL Server 2000, Evaluation edition of SQL 2005
which has top be installed as a named instance because of the way that 2K &
2K5 co-exist on the same box, and then there are a couple silly apps I have
that install MSDE as other named instances.
and the STUPI .NET DATA CONNECTION DIALOG doesn't have a field geared toward
named instances.
@.#$%^&
I will now crawl back under my rock.
Peace & happy computing,
Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSenseiCan you edit the connection string in web.config or the source code?
"Mike Labosh" <mlabosh_at_vbsensei_dot_com> wrote in message
news:uwZSfc5PGHA.4900@.TK2MSFTNGP09.phx.gbl...
> So I have this box with SQL Server 2000, Evaluation edition of SQL 2005
> which has top be installed as a named instance because of the way that 2K
> &
> 2K5 co-exist on the same box, and then there are a couple silly apps I
> have
> that install MSDE as other named instances.
> and the STUPI .NET DATA CONNECTION DIALOG doesn't have a field geared
> toward
> named instances.
> @.#$%^&
> I will now crawl back under my rock.
>
> --
> Peace & happy computing,
> Mike Labosh, MCSD MCT
> Owner, vbSensei.Com
> "Escriba coda ergo sum." -- vbSensei
>|||> Can you edit the connection string in web.config or the source code?
2K
Of course I can. It just angers me that the silly little foolish dialog
doesn't let me say so.
Peace & happy computing,
Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei

[ODBC SQL Server Driver]Timeout expired

We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely appreciated?
Any help would be greatly appreciated.
Thank you.
- A l p e r
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that much of traffic hitting our web pages other than the developers themselves (for now-and-then testing). This error seems to pop up sometimes early in the morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I think it might not be due to load on the system.
And changing the time out value to something more or making it unlimited would really be a temporary solution at best for us. I am trying to figure out the real problem, so that the freeze up never happens...Oddly enough, when I run the 'EXEC sp_recompile
' with a table name, the problem disappears...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that much of traffic hitting our web pages other than the developers themselves (for now-and-then testing). This error seems to pop up sometimes early in the morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I think it might not be due to load on the system.
And changing the time out value to something more or making it unlimited would really be a temporary solution at best for us. I am trying to figure out the real problem, so that the freeze up never happens...Oddly enough, when I run the 'EXEC sp_recompile
' with a table name, the problem seems to disappear...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov

[ODBC SQL Server Driver]Timeout expired

We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely apprec
iated?
Any help would be greatly appreciated.
Thank you.
- A l p e r"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that m
uch of traffic hitting our web pages other than the developers themselves (f
or now-and-then testing). This error seems to pop up sometimes early in the
morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I t
hink it might not be due to load on the system.
And changing the time out value to something more or making it unlimited wou
ld really be a temporary solution at best for us. I am trying to figure out
the real problem, so that the freeze up never happens...Oddly enough, when I
run the 'EXEC sp_recompile
' with a table name, the problem disappears...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that m
uch of traffic hitting our web pages other than the developers themselves (f
or now-and-then testing). This error seems to pop up sometimes early in the
morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I t
hink it might not be due to load on the system.
And changing the time out value to something more or making it unlimited wou
ld really be a temporary solution at best for us. I am trying to figure out
the real problem, so that the freeze up never happens...Oddly enough, when I
run the 'EXEC sp_recompile
' with a table name, the problem seems to disappear...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov

[ODBC SQL Server Driver]Timeout expired

We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied)
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expire
If anyone has any ideas as to possible reasons, it would be immensely appreciated
Any help would be greatly appreciated
Thank you
- A l p e"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

trying to install sql server2005 on a windows 2003 server box.

getting msg below at the sql server . i looked at other posts on trying to uninstall SQL Native Access Client and norton antivirus. i could never find the snac on the add - remove programs and this server does not have a virus protection program yet.

here's the history of the installs on the server:

wanted to test a 2005 upgrade so:

1) installed sql server 2000 then sp4 then restored some databases to it - all OK

2) tried to upgrade to sql 2005 but ran into problems and left it at that.

had a disk drive crash on the d drive so lost the installs but not the operating system

when the drive was replaced, left alone for a while

then wanted to test a straight 2005 install

1) removed the broken 2005 attempt

2) removed the 2000

3) installed 2005 and got the error on the subject line:

TITLE: Microsoft SQL Server 2005 Setup

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

i've gone through as many of the forums that i can and have tried several things - like uninstalling 2005 and installing pieces and parts but but nothing seems to work.

Thanks!

Dan <><

It sounds like the SNAC version you have might be corrupt or incompatible.

Go to Add or Remove Programs and find the listing for "Microsoft SQL Native Client". Remove this component.

Then try the install again.

Michelle

|||

Thank you so much for replying. last attempt was to install just the sql server commonent - no others like analysis services or integration services.

i looked at the add / remove programs both before, during and after the sql server database services failed attempt and the add/remove has never shown a program called MS sql native access client (SNAC).

when i start the install, the installing prerequisites window shows the two components that will be installed: snac and the sql server 2005 setup support files. the snac goes to a green arrow almost immediately while the 2005 setup files takes a few seconds. i dont know if that helps or not.

the add remove programs just has:

microsoft .net framwork 2.0|||

It definatel looks like the problems is the "Microsoft SQL Server Native Client" layer. At this point your machine thinks that it is already installed but the install is broken.

Follow the directions in the following article to clean up the machine and then try again.

http://support.microsoft.com/kb/909967

Michelle

|||

uninstall manually - did the following (shows issues with some of the directions)

it said to delete the local security groups. but i never could figure out how to do. the article it mensions didnt (at least to me) show how to delete. so i just went on|||

i went out to the website and downloaded the .msi file for snac. it was slightly different from the .msi that came on the DVD (3511k vs 3516k).

the dvd version when i clicked on the msi file just returned me back to windows explorer.

the snac from microsoft's website executed and finally installed the snac.

the install worked perfectly after that.

thanks for your help

|||

Actually that was a good work around as downloading a newer version would have forced the install to run again where as in the previous case it was failing quickly becuase it thought it was laready installed.

Glad you got you machine back.

Michelle

|||

Hi,

I've been handling SQL Server upgrades for many years. The most dangerous path for an upgrade is to directly upgrade 2000 to 2005 (or 7.0 to 2000). That's because you create the risk of destroying the databases on the existing server and causing data loss.

The best approach embraces the fact that we typically upgrade a windows server when the mfg warranty on the hardware has expired. So, you have a new box and windows server. If you don't, the store the backups on another resource (disk, tape, flash drive, etc...) and copy from or restore from that resource. Rebuild the Windows server or uninstall SQL Server 2000. (I would have fresh windows to insure the best chance of success.)

Install SQL 2005 & configure on the new W03 SP1 server. migrate the users. (this worked easily with 2K but MS has hosed that functionality in 2005 from what I can see; you must use a script they provided that is flaky. You will need to manually create the users it fails to migrate.) Backup the dbs on 2K, shut down 2K on the old machine and restore the dbs to 2005. associate the users with the logins.

Now you have a fullly upgraded database server and your databases are unhosed. This may not be elegant but it guarantees the MS upgrade process won't destroy your databases or bring down your business for days.

If you have a completely hosed system, then rebuild the system (and the drives) and follow the steps above to a successful conclusion.

z.

@@SERVERNAME sql 2k

Hi,
Diff server name for same sql box.
Select @.@.SERVERNAME
and select * from sysservers
WHy?
@.@.SERVERNAME returns incorrect name. How do I correct it?
THnksHi
At some point you probably renamed the server at some point, run
sp_dropserver and sp_addserver as shown in:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_afterinstall_5r8f.asp
John
"mecn" wrote:
> Hi,
> Diff server name for same sql box.
> Select @.@.SERVERNAME
> and select * from sysservers
> WHy?
> @.@.SERVERNAME returns incorrect name. How do I correct it?
> THnks
>
>

@@SERVERNAME sql 2k

Hi,
Diff server name for same sql box.
Select @.@.SERVERNAME
and select * from sysservers
WHy?
@.@.SERVERNAME returns incorrect name. How do I correct it?
THnksHi
At some point you probably renamed the server at some point, run
sp_dropserver and sp_addserver as shown in:
http://msdn.microsoft.com/library/d...nstall_5r8f.asp
John
"mecn" wrote:

> Hi,
> Diff server name for same sql box.
> Select @.@.SERVERNAME
> and select * from sysservers
> WHy?
> @.@.SERVERNAME returns incorrect name. How do I correct it?
> THnks
>
>