Hello,
My 1st attempt to install .Net framework, MSDE, my application and the databases during setup (using the MSDE deployment toolkit RC) works fine on windows xp. Now when I try to do the same for windows 98 SE machine, I am able to install .Net framweork an
d MSDE, but after that during the installation I get the following error message:
"An exception occured in the OnAfterInstall event handler of DBInstaller.CustomInstaller --> Unable to access service: Operating system does not support controlling a Windows service. A service can only be controlled on Windows NT, Windows 2000, or lat
er."
It's clear that when the setup tries to start the service to create the database etc it fails. Is this a known issue. I researched on web but couldn't find anything. Any ideas.
Thanks
dev
Any ideas..
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Friday, March 30, 2012
MSDE to SQL Server 2000 connection drops on XP Pro
Using MSDE 2000 SP3
Sql Server 2000 SP3
Win XP Pro SP1
Microsoft.Jet.OLEDB.4.0
We have recently upgraded field laptops from Windows 2000 to XP Pro. One of our applications which was developed with Visual C++ 6.0 and using MSDE will just drop it's connection to our consolidated Sql Server 2000. This works on Windows 2000 machines.
I have ran the profiler, monitored Sql Processes for locks, checked Event logs and I am unable to find any type of error. Our sync process just drops off. I am uncertain if it is MSDE, Sql Server or XP.
I even set the application's compatiability settings to Windows 2000 but still same result. I am uncertain as to how to do anymore troubleshooting.
Any ideas would be much appreciated.
Thanks,
Vannie Keever
SQL Server (including the MSDE edition) cannot close a connection by itself
except when shutting down. The client, the OS, or the network has to tell
SQL Server to drop the connection. Try a netmon trace to get more details.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
sql
Sql Server 2000 SP3
Win XP Pro SP1
Microsoft.Jet.OLEDB.4.0
We have recently upgraded field laptops from Windows 2000 to XP Pro. One of our applications which was developed with Visual C++ 6.0 and using MSDE will just drop it's connection to our consolidated Sql Server 2000. This works on Windows 2000 machines.
I have ran the profiler, monitored Sql Processes for locks, checked Event logs and I am unable to find any type of error. Our sync process just drops off. I am uncertain if it is MSDE, Sql Server or XP.
I even set the application's compatiability settings to Windows 2000 but still same result. I am uncertain as to how to do anymore troubleshooting.
Any ideas would be much appreciated.
Thanks,
Vannie Keever
SQL Server (including the MSDE edition) cannot close a connection by itself
except when shutting down. The client, the OS, or the network has to tell
SQL Server to drop the connection. Try a netmon trace to get more details.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
sql
MSDE TCP listen problem
I have recently installed a MSDE 2000 (unfortunately with no service pack yet) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to make the MSDE server listen on TCP/IP port 1433. But it will not listen on that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tells me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there were some security settings on that port. And my application had no problem in listening on port 1433.
After looking in the Event Viewer I found a solution to my problem: Windows 2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is not updated with a Service Pack. MSDE without Service Pack is not very secure to virusses like Slammer.
|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.
/IP port!! There is no information in the ERRORLOG file. This file just tells me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there were some security settings on that port. And my application had no problem in listening on port 1433.
After looking in the Event Viewer I found a solution to my problem: Windows 2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is not updated with a Service Pack. MSDE without Service Pack is not very secure to virusses like Slammer.
|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.
MSDE TCP listen problem
I have recently installed a MSDE 2000 (unfortunately with no service pack ye
t) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to
make the MSDE server listen on TCP/IP port 1433. But it will not listen on
that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tell
s me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there w
ere some security settings on that port. And my application had no problem i
n listening on port 1433.After looking in the Event Viewer I found a solution to my problem: Windows
2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is n
ot updated with a Service Pack. MSDE without Service Pack is not very secure
to virusses like Slammer.|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.
t) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to
make the MSDE server listen on TCP/IP port 1433. But it will not listen on
that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tell
s me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there w
ere some security settings on that port. And my application had no problem i
n listening on port 1433.After looking in the Event Viewer I found a solution to my problem: Windows
2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is n
ot updated with a Service Pack. MSDE without Service Pack is not very secure
to virusses like Slammer.|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.
MSDE Subscriber's database > 2GB
Hi all !
We have a database with publication on
SBS2003 Premium Edition,
and 4 subscribers on workstations in warehouses on:
- Windows XP Professional
- MSDE
The database is 1.6 GB now and growing
further. I should migrate from MSDE
to SQL Server 2000.
Which version of SQL has to be installed
at warehouses (on top of Win XP Prof)?
Do I have to break the replication before ?
Thanks,
Pagus
Paul,
what about Personal Edition + Win XP Pro ?
Win XP Pro is working OK with MSDE, I wouldn't like to
purchase Win Server product :-(
Pagus
On Mon, 6 Sep 2004 00:48:11 -0700, "Paul Ibison"
<Paul.Ibison@.Pygmalion.Com> wrote:
>Pagus,
>you'll need Standard or Enterprise Edition. The OSs=20
>required for these editions of sql server are:
>Windows Server 2003, Standard Edition1=20
>Windows Server 2003, Enterprise Edition1=20
>Windows Server 2003, Datacenter Edition1=20
>Windows=AE 2000 Server=20
>Windows 2000 Advanced Server=20
>Windows 2000 Datacenter Server=20
>Windows NT=AE Server version 4.0 with Service Pack 5 (SP5)=20
>or later=20
>Windows NT Server 4.0, Enterprise Edition, with SP5 or=20
>later=20
>HTH,
>Paul Ibison
>(The ONLY sql server 2000 replication book:
>http://www.nwsu.com/0974973602p.html)
>
|||Pagus,
you're quire right, subject to the following restrictions:
It includes a concurrent workload governor that limits
its scalability; performance degrades when more than five
Transact-SQL batches are executed concurrently.
It cannot act as a transactional replication publisher
(subscriber only).
Regards,
Paul Ibison
We have a database with publication on
SBS2003 Premium Edition,
and 4 subscribers on workstations in warehouses on:
- Windows XP Professional
- MSDE
The database is 1.6 GB now and growing
further. I should migrate from MSDE
to SQL Server 2000.
Which version of SQL has to be installed
at warehouses (on top of Win XP Prof)?
Do I have to break the replication before ?
Thanks,
Pagus
Paul,
what about Personal Edition + Win XP Pro ?
Win XP Pro is working OK with MSDE, I wouldn't like to
purchase Win Server product :-(
Pagus
On Mon, 6 Sep 2004 00:48:11 -0700, "Paul Ibison"
<Paul.Ibison@.Pygmalion.Com> wrote:
>Pagus,
>you'll need Standard or Enterprise Edition. The OSs=20
>required for these editions of sql server are:
>Windows Server 2003, Standard Edition1=20
>Windows Server 2003, Enterprise Edition1=20
>Windows Server 2003, Datacenter Edition1=20
>Windows=AE 2000 Server=20
>Windows 2000 Advanced Server=20
>Windows 2000 Datacenter Server=20
>Windows NT=AE Server version 4.0 with Service Pack 5 (SP5)=20
>or later=20
>Windows NT Server 4.0, Enterprise Edition, with SP5 or=20
>later=20
>HTH,
>Paul Ibison
>(The ONLY sql server 2000 replication book:
>http://www.nwsu.com/0974973602p.html)
>
|||Pagus,
you're quire right, subject to the following restrictions:
It includes a concurrent workload governor that limits
its scalability; performance degrades when more than five
Transact-SQL batches are executed concurrently.
It cannot act as a transactional replication publisher
(subscriber only).
Regards,
Paul Ibison
Wednesday, March 28, 2012
MSDE SP4
Can anyone please help me with upgrading to MSDE 2000 SP4
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
Suhail
Hi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhail
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
Suhail
Hi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhail
MSDE SP4
Can anyone please help me with upgrading to MSDE 2000 SP4
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting workin
g.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server
.
> The instance was installed by default while installing BKUPExec. Evry time
I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installe
d
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting work
ing.
> Thank you for your help.
> Suhail
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting workin
g.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server
.
> The instance was installed by default while installing BKUPExec. Evry time
I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installe
d
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting work
ing.
> Thank you for your help.
> Suhail
MSDE SP4
Can anyone please help me with upgrading to MSDE 2000 SP4
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhailsql
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhailsql
MSDE SP3a and XP SP2 on Localhost
I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
default instance on localhost (i.e. not over the network). I found where an
upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
and it's still not working.
Is there something else I'm missing?
thanks in advance
XP SP2 installs a new local firewall that prevents applications from opening
listening ports. You will need to configure the local firewall to allow
sqlservr.exe open listening ports.
See:
http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
Jim
"tg2" <tg2@.discussions.microsoft.com> wrote in message
news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
> default instance on localhost (i.e. not over the network). I found where
an
> upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
> and it's still not working.
> Is there something else I'm missing?
> thanks in advance
|||Except when running on the localhost (i.e. NOT using the network), the
firewall doesn't come into play. My application is using shared memory to
connect to the MSDE database and as such, never opens a network library --
thus opening the firewall doesn't fix the problem.
But thank you for your reply anyway...
"Jim Young" wrote:
> XP SP2 installs a new local firewall that prevents applications from opening
> listening ports. You will need to configure the local firewall to allow
> sqlservr.exe open listening ports.
> See:
> http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
> Jim
> "tg2" <tg2@.discussions.microsoft.com> wrote in message
> news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> an
>
>
|||I have precisely the same problem. My application relies entirely on local
instance of MSDE.
Process associated with sqlservr does not show any port to be opened when
checked with "netstat" command. Any ideas how to work around it?
"tg2" wrote:
> Except when running on the localhost (i.e. NOT using the network), the
> firewall doesn't come into play. My application is using shared memory to
> connect to the MSDE database and as such, never opens a network library --
> thus opening the firewall doesn't fix the problem.
> But thank you for your reply anyway...
>
sql
default instance on localhost (i.e. not over the network). I found where an
upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
and it's still not working.
Is there something else I'm missing?
thanks in advance
XP SP2 installs a new local firewall that prevents applications from opening
listening ports. You will need to configure the local firewall to allow
sqlservr.exe open listening ports.
See:
http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
Jim
"tg2" <tg2@.discussions.microsoft.com> wrote in message
news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
> default instance on localhost (i.e. not over the network). I found where
an
> upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
> and it's still not working.
> Is there something else I'm missing?
> thanks in advance
|||Except when running on the localhost (i.e. NOT using the network), the
firewall doesn't come into play. My application is using shared memory to
connect to the MSDE database and as such, never opens a network library --
thus opening the firewall doesn't fix the problem.
But thank you for your reply anyway...
"Jim Young" wrote:
> XP SP2 installs a new local firewall that prevents applications from opening
> listening ports. You will need to configure the local firewall to allow
> sqlservr.exe open listening ports.
> See:
> http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
> Jim
> "tg2" <tg2@.discussions.microsoft.com> wrote in message
> news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> an
>
>
|||I have precisely the same problem. My application relies entirely on local
instance of MSDE.
Process associated with sqlservr does not show any port to be opened when
checked with "netstat" command. Any ideas how to work around it?
"tg2" wrote:
> Except when running on the localhost (i.e. NOT using the network), the
> firewall doesn't come into play. My application is using shared memory to
> connect to the MSDE database and as such, never opens a network library --
> thus opening the firewall doesn't fix the problem.
> But thank you for your reply anyway...
>
sql
MSDE Setup Failed
Need Help !!!!
I'm trying to install MSDE on my computer - Dell 2.4 ghz
Operating system is Windows XP Professional.
I have already installed the WEB Matrix but having problems installing MSDE.
I keep getting this error message.
I receive this error message:
(Setup failed to configure the server. Refer to the server error logs and setup error
logs for more information.)
Thanks In AdvanceSigh. Setting up MSDE is one of the most complex things that Microsoft has imposed on us.
What do the logs say? They're usually a pretty good source of information.
Don|||Hi Don,
Thanks for taking the time, Here's the latest log I found. see if this can help?
Thanks again
Jeff
2003-08-02 18:32:43.26 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2003-08-02 18:32:43.26 server Copyright (C) 1988-2002 Microsoft Corporation.
2003-08-02 18:32:43.26 server All rights reserved.
2003-08-02 18:32:43.26 server Server Process ID is 1592.
2003-08-02 18:32:43.26 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
2003-08-02 18:32:43.28 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2003-08-02 18:32:43.29 server SQL Server configured for thread mode processing.
2003-08-02 18:32:43.29 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2003-08-02 18:32:43.32 spid3 Warning ******************
2003-08-02 18:32:43.32 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2003-08-02 18:32:43.32 spid3 Starting up database 'master'.
2003-08-02 18:32:43.78 server Using 'SSNETLIB.DLL' version '8.0.760'.
2003-08-02 18:32:43.79 spid5 Starting up database 'model'.
2003-08-02 18:32:44.01 server SQL server listening on 192.168.0.2: 1433.
2003-08-02 18:32:44.03 server SQL server listening on 127.0.0.1: 1433.
2003-08-02 18:32:44.09 spid3 Server name is 'CDISLAND'.
2003-08-02 18:32:44.09 spid3 Starting up database 'msdb'.
2003-08-02 18:32:44.59 spid5 Clearing tempdb database.
2003-08-02 18:32:45.54 spid5 Starting up database 'tempdb'.
2003-08-02 18:32:45.78 spid3 Recovery complete.
2003-08-02 18:32:45.78 spid3 SQL global counter collection task is created.
2003-08-02 18:32:45.79 spid3 Warning: override, autoexec procedures skipped.
2003-08-02 18:32:46.28 server SQL server listening on TCP, Shared Memory, Named Pipes.
2003-08-02 18:32:46.28 server SQL Server is ready for client connections
2003-08-02 18:32:54.10 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.|||Finally got it to work, here's what I did:
·Went to my Add/Remove Programs located in Control Panel.
·Removed MSDE from the Add/Remove Programs.
·Went to my C Drive and removed/deleted the (sql2ksp3 folder)
·Next I went to my Programs files folder and also removed/deleted the (Microsoft SQL server) folder.
·Then Restart computer, and reinstall (sql2ksp3) again – thus eliminating the roll back error
Reinstalling sql2kDesksp3
·Double clicked on sql2kDesksp3 bringing up the installation wizard
·And just followed the installation instructions.
·Now your asked to specify where the files in the SQL2KdeskSP3.exe should be unpacked. Leave the default value, C:\sql2ksp2.
·Once this step is complete the installation wizard will quit.
·Next go to Start, Run, and type in cmd and this opens the command prompt. And enter your commands here.
·Type in cd\sql2ksp3 and hit enter
·Next type dir and hit enter
·Next type cd MSDE and hit enter
·Next type dir and hit enter
·Next type setup SAPWD=password SECURITYMODE=SQL and hit enter
And Installation will begin – this may take a few minutes.
Note: where “password” is the password you want for the administrative MSDE account. [Make sure that you write down and remember your password. You will
Need to provide this supplied password when working with MSDE.
After installation is complete, Restart your computer. Upon returning to Windows, you
Should see a new icon in your system tray. The icon will look like a computer tower with a green arrow in a white circle. That's your Done.
Hope this helps Somebody
Cheers!!|||Thanks loads it has helped me...|||Cool! Glad you got it worked out!
Don
MSDE Setup and first database
I'm deploying MSDE with a desktop app (windows forms .net).
after installing MSDE, how do I create the database for the application?
I cannot provide a createdb.sql script to the user because there is no
queryanalyzer or similar tools.
How can I run the create query from the setup? or what is the recommended
method for doing this?
Thank You!
Hi,
Give a batch file to create the database. All you have to do is double click
the batch file. batch file should contain:-
OSQL -Usa -Ppassword -S servername -Q'Create database
dbname' -o'c:\createdb.log'
Save the command inside a .BAT file and send to client side to create the
database. Instad of giving the -Q parameter you
can also input a .SQL file which contans sequence of TSQL commands.
Thanks
Hari
SQL Server MVP
"Harley" <harleyobrienAThotmailDOTcom> wrote in message
news:E3273FC0-ADE4-47B1-9F3D-8DEC479E3341@.microsoft.com...
> I'm deploying MSDE with a desktop app (windows forms .net).
> after installing MSDE, how do I create the database for the application?
> I cannot provide a createdb.sql script to the user because there is no
> queryanalyzer or similar tools.
> How can I run the create query from the setup? or what is the recommended
> method for doing this?
> Thank You!
after installing MSDE, how do I create the database for the application?
I cannot provide a createdb.sql script to the user because there is no
queryanalyzer or similar tools.
How can I run the create query from the setup? or what is the recommended
method for doing this?
Thank You!
Hi,
Give a batch file to create the database. All you have to do is double click
the batch file. batch file should contain:-
OSQL -Usa -Ppassword -S servername -Q'Create database
dbname' -o'c:\createdb.log'
Save the command inside a .BAT file and send to client side to create the
database. Instad of giving the -Q parameter you
can also input a .SQL file which contans sequence of TSQL commands.
Thanks
Hari
SQL Server MVP
"Harley" <harleyobrienAThotmailDOTcom> wrote in message
news:E3273FC0-ADE4-47B1-9F3D-8DEC479E3341@.microsoft.com...
> I'm deploying MSDE with a desktop app (windows forms .net).
> after installing MSDE, how do I create the database for the application?
> I cannot provide a createdb.sql script to the user because there is no
> queryanalyzer or similar tools.
> How can I run the create query from the setup? or what is the recommended
> method for doing this?
> Thank You!
MSDE Service Manager on XP Pro SP2
I recently installed MSDE 2K on a Windows XP SP2 system. Everything appears
to be working fine, with the exception of the service manager. For some
reason, it will not find the system on the local network and will not
connect to it if I type the name in the server name area. Is this normal or
am I just missing something? Thanks in advance.
hi David,
"David Young" <cdyoung@.uta.edu> ha scritto nel messaggio
news:eBToEMg3EHA.3840@.tk2msftngp13.phx.gbl
> I recently installed MSDE 2K on a Windows XP SP2 system. Everything
> appears to be working fine, with the exception of the service
> manager. For some reason, it will not find the system on the local
> network and will not connect to it if I type the name in the server
> name area. Is this normal or am I just missing something? Thanks in
> advance.
actually, for local instances connections, WinXP sp2 should not be a
problem, but only for remote connections :D
as regard the Service Manager not showing the instance name, this is a known
issue when network protocols are disabled (default setting) as you can see
in http://support.microsoft.com/default...b;EN-US;814132
as regard directly typing in the instance name... did you provide the name
in the ComputerName\InstanceName format ( or just (local)\InstanceName) ?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
to be working fine, with the exception of the service manager. For some
reason, it will not find the system on the local network and will not
connect to it if I type the name in the server name area. Is this normal or
am I just missing something? Thanks in advance.
hi David,
"David Young" <cdyoung@.uta.edu> ha scritto nel messaggio
news:eBToEMg3EHA.3840@.tk2msftngp13.phx.gbl
> I recently installed MSDE 2K on a Windows XP SP2 system. Everything
> appears to be working fine, with the exception of the service
> manager. For some reason, it will not find the system on the local
> network and will not connect to it if I type the name in the server
> name area. Is this normal or am I just missing something? Thanks in
> advance.
actually, for local instances connections, WinXP sp2 should not be a
problem, but only for remote connections :D
as regard the Service Manager not showing the instance name, this is a known
issue when network protocols are disabled (default setting) as you can see
in http://support.microsoft.com/default...b;EN-US;814132
as regard directly typing in the instance name... did you provide the name
in the ComputerName\InstanceName format ( or just (local)\InstanceName) ?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Monday, March 26, 2012
msde security - windows mode?
Hi,
I want to be able to use SQL authentication on my local MSDE 2000 , I've
added a user using sp_addlogin, and try to connect using it, however it
always gives me 'not associated with a trusted SQL server connection'. Is
there any way I can force it to go to SQL mode without reinstalling it?
Thanks> I want to be able to use SQL authentication on my local MSDE 2000 , I've
> added a user using sp_addlogin, and try to connect using it, however it
> always gives me 'not associated with a trusted SQL server connection'. Is
> there any way I can force it to go to SQL mode without reinstalling it?
Yes - check the article at http://support.microsoft.com/kb/285097/EN-US/.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com|||> I want to be able to use SQL authentication on my local MSDE 2000 , I've
> added a user using sp_addlogin, and try to connect using it, however it
> always gives me 'not associated with a trusted SQL server connection'. Is
> there any way I can force it to go to SQL mode without reinstalling it?
Look at my answer in .security group.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
I want to be able to use SQL authentication on my local MSDE 2000 , I've
added a user using sp_addlogin, and try to connect using it, however it
always gives me 'not associated with a trusted SQL server connection'. Is
there any way I can force it to go to SQL mode without reinstalling it?
Thanks> I want to be able to use SQL authentication on my local MSDE 2000 , I've
> added a user using sp_addlogin, and try to connect using it, however it
> always gives me 'not associated with a trusted SQL server connection'. Is
> there any way I can force it to go to SQL mode without reinstalling it?
Yes - check the article at http://support.microsoft.com/kb/285097/EN-US/.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com|||> I want to be able to use SQL authentication on my local MSDE 2000 , I've
> added a user using sp_addlogin, and try to connect using it, however it
> always gives me 'not associated with a trusted SQL server connection'. Is
> there any way I can force it to go to SQL mode without reinstalling it?
Look at my answer in .security group.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
MSDE Running on Two Computers in Workgroup Mode
I have two PC running Windows XP Pro in Workgroup Mode. They both in mixed
authentication mode with blank sa password.
The usernames on each machine are the same and they have no password.
The problem I have is with merge replication. The replication fails with the
message "Login failed for user 'sa'. Reason: Not associated with a trusted
SQL Server connection."
Both computers use the local system account to start the SQL server agent.
If we connect manually to the database via ADO using the sa with blank
password we have no difficulties.
Can someone please advise where I am going wrong.
Thank you in advance.
Colin
Hi ,
There are a number of reasons why this error may occur:
Try using these steps:
1) Most probably you may not be able to logon on to the sql server using
windows authentication.
2) Try using windows authentication over named pipes instead fo tcp/ip to
connect to the sql server.
Make sure that you make use of an alias to do the task
This should fix the problem.
Girish Sundaram
This posting is provided "AS IS" with no warranties, and confers no rights.
authentication mode with blank sa password.
The usernames on each machine are the same and they have no password.
The problem I have is with merge replication. The replication fails with the
message "Login failed for user 'sa'. Reason: Not associated with a trusted
SQL Server connection."
Both computers use the local system account to start the SQL server agent.
If we connect manually to the database via ADO using the sa with blank
password we have no difficulties.
Can someone please advise where I am going wrong.
Thank you in advance.
Colin
Hi ,
There are a number of reasons why this error may occur:
Try using these steps:
1) Most probably you may not be able to logon on to the sql server using
windows authentication.
2) Try using windows authentication over named pipes instead fo tcp/ip to
connect to the sql server.
Make sure that you make use of an alias to do the task
This should fix the problem.
Girish Sundaram
This posting is provided "AS IS" with no warranties, and confers no rights.
MSDE Replication in Workgroup Enviromnet
We currently have two machines in a workgroup environment and both are
running WIndows XP Pro SP1 and MSDE Sp3.
The problem we have is with the Merge Replication. The publisher writes
snapshot data to the snapshot folder, but the subscriber is unable to open
this file across the network. We get error 5 access denied.
From the subscriber PC through explorer/notepad we can open the file. The
file name is MSmerge_genhistory.bcp
If we were to put the pc into a domain we have no problem. Replication wor
Replication is probably accessing this file through a admin share
something like \\servername\d$\xxxxx\repldata\ which needs admin access to
the distributor machine.
Try configuring a named share like \\servername\repldata and allow access to
relevant user and set that to be the working directory. You can set the
working directory when configuring publisher
or through sp_adddistpublisher or sp_changedistpublisher.
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
"Colin M" <ColinM@.discussions.microsoft.com> wrote in message
news:027D0BE9-2D57-4DF4-888C-173A7FCD3404@.microsoft.com...
> We currently have two machines in a workgroup environment and both are
> running WIndows XP Pro SP1 and MSDE Sp3.
> The problem we have is with the Merge Replication. The publisher writes
> snapshot data to the snapshot folder, but the subscriber is unable to open
> this file across the network. We get error 5 access denied.
> From the subscriber PC through explorer/notepad we can open the file. The
> file name is MSmerge_genhistory.bcp
>
> If we were to put the pc into a domain we have no problem. Replication wor
running WIndows XP Pro SP1 and MSDE Sp3.
The problem we have is with the Merge Replication. The publisher writes
snapshot data to the snapshot folder, but the subscriber is unable to open
this file across the network. We get error 5 access denied.
From the subscriber PC through explorer/notepad we can open the file. The
file name is MSmerge_genhistory.bcp
If we were to put the pc into a domain we have no problem. Replication wor
Replication is probably accessing this file through a admin share
something like \\servername\d$\xxxxx\repldata\ which needs admin access to
the distributor machine.
Try configuring a named share like \\servername\repldata and allow access to
relevant user and set that to be the working directory. You can set the
working directory when configuring publisher
or through sp_adddistpublisher or sp_changedistpublisher.
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
"Colin M" <ColinM@.discussions.microsoft.com> wrote in message
news:027D0BE9-2D57-4DF4-888C-173A7FCD3404@.microsoft.com...
> We currently have two machines in a workgroup environment and both are
> running WIndows XP Pro SP1 and MSDE Sp3.
> The problem we have is with the Merge Replication. The publisher writes
> snapshot data to the snapshot folder, but the subscriber is unable to open
> this file across the network. We get error 5 access denied.
> From the subscriber PC through explorer/notepad we can open the file. The
> file name is MSmerge_genhistory.bcp
>
> If we were to put the pc into a domain we have no problem. Replication wor
MSDE remote connection on Windows Home - Windows Authentication
I installed an MSDE on a PC running Windows Home Edition. I would like
to connect to this MSDE installation from an oher PC using Windows
Authentication.
What do I have to do (add account on Home Edition)
hi,
xavierdaull@.gmail.com wrote:
> I installed an MSDE on a PC running Windows Home Edition. I would like
> to connect to this MSDE installation from an oher PC using Windows
> Authentication.
> What do I have to do (add account on Home Edition)
without a Domain Controller, thought in a Workgroup environment, usually you
should rely on standard SQL Server authenticated connections for remote
ones, as all the authentication features are resolved and managed by the
Domain Controller it self..
you can however setup a local account to map the remote account of the other
machine... that's to say, on your local PC you have to add another account
with the very same "credentials" of other account(s) present on the remote
PCs...
all this (still) works becouse of the underlying OS gets somehow confused
and a sort of "embezzlement" where 2 differents accounts, YourPC\YourAccount
and OtherPC\YourAccount "share" a kind of uniqueness becouse of netbios
intrusion... a preventive netbios connection, even on a share or using NET
USE can help...
but this is not granted to work in future releases or even OS service
packs...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
to connect to this MSDE installation from an oher PC using Windows
Authentication.
What do I have to do (add account on Home Edition)
hi,
xavierdaull@.gmail.com wrote:
> I installed an MSDE on a PC running Windows Home Edition. I would like
> to connect to this MSDE installation from an oher PC using Windows
> Authentication.
> What do I have to do (add account on Home Edition)
without a Domain Controller, thought in a Workgroup environment, usually you
should rely on standard SQL Server authenticated connections for remote
ones, as all the authentication features are resolved and managed by the
Domain Controller it self..
you can however setup a local account to map the remote account of the other
machine... that's to say, on your local PC you have to add another account
with the very same "credentials" of other account(s) present on the remote
PCs...
all this (still) works becouse of the underlying OS gets somehow confused
and a sort of "embezzlement" where 2 differents accounts, YourPC\YourAccount
and OtherPC\YourAccount "share" a kind of uniqueness becouse of netbios
intrusion... a preventive netbios connection, even on a share or using NET
USE can help...
but this is not granted to work in future releases or even OS service
packs...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
MSDE remote connection failure
Hi all,
I installed a MSDE on a Windows XP SP2 and configured it for accepting remote connections. But It shows the "SQL Server doesnot exist or connection denied" message whenever I try to connect to this server. For more information I am adding more facts
* It is an MSDE and not a WMSDE
* Firewall is turned off
* Server process is listening on 0.0.0.0:1433
* TCP/IP and Named Pipes are enabled using server network utility
* LoginMode=2 is set for mixed mode authentication in the registry
* Tried restaring the Process and even windows after the changes.
Please help me !!
Thanks in advanceHi friends,
I got the issue fixed. :angel:
I dont know how it works but it worked.
On the client side; using the client network utility, I added an alias to my server.
My server's instance name was SLIMSHADY\SSIT and it was listening on 8001(I changed it thru the registry) in mixed mode authentication.
It wasted my 4-5 hours of playing with the registry and googling. The final attempt succeeded in which I created an alias to the server Indicating its exact port number and Instance name.
Then I tried connecting using this alias .... IT WORKED !!
I DONT KNOW HOW IT WORKS BUT IT WORKED IN MY CASE
HAPPY COMPUTING
MSDE remote connection failure
Hi all,
I installed a MSDE on a Windows XP SP2 and configured it for accepting remote connections. But It shows the "SQL Server doesnot exist or connection denied" message whenever I try to connect to this server. For more information I am adding more facts
* It is an MSDE and not a WMSDE
* Firewall is turned off
* Server process is listening on 0.0.0.0:1433
* TCP/IP and Named Pipes are enabled using server network utility
* LoginMode=2 is set for mixed mode authentication in the registry
* Tried restaring the Process and even windows after the changes.
Please help me !!
Thanks in advanceHi friends,
I got the issue fixed. :angel:
I dont know how it works but it worked.
On the client side; using the client network utility, I added an alias to my server.
My server's instance name was SLIMSHADY\SSIT and it was listening on 8001(I changed it thru the registry) in mixed mode authentication.
It wasted my 4-5 hours of playing with the registry and googling. The final attempt succeeded in which I created an alias to the server Indicating its exact port number and Instance name.
Then I tried connecting using this alias .... IT WORKED !!
I DONT KNOW HOW IT WORKS BUT IT WORKED IN MY CASE
HAPPY COMPUTING
I installed a MSDE on a Windows XP SP2 and configured it for accepting remote connections. But It shows the "SQL Server doesnot exist or connection denied" message whenever I try to connect to this server. For more information I am adding more facts
* It is an MSDE and not a WMSDE
* Firewall is turned off
* Server process is listening on 0.0.0.0:1433
* TCP/IP and Named Pipes are enabled using server network utility
* LoginMode=2 is set for mixed mode authentication in the registry
* Tried restaring the Process and even windows after the changes.
Please help me !!
Thanks in advanceHi friends,
I got the issue fixed. :angel:
I dont know how it works but it worked.
On the client side; using the client network utility, I added an alias to my server.
My server's instance name was SLIMSHADY\SSIT and it was listening on 8001(I changed it thru the registry) in mixed mode authentication.
It wasted my 4-5 hours of playing with the registry and googling. The final attempt succeeded in which I created an alias to the server Indicating its exact port number and Instance name.
Then I tried connecting using this alias .... IT WORKED !!
I DONT KNOW HOW IT WORKS BUT IT WORKED IN MY CASE
HAPPY COMPUTING
MSDE Remote Connect strange problem
I'm trying to connect to the SharePoint MSDE database from Windows XP
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not
exist or access denied.
I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?
Did you ever get an answer to this problem? I'm having a similar error on Windows XP SP2 machines that have MDAC 2.8SP1. I have an MS Access front end that links to SQL Server database using ODBC connections. The report will run, but keeps asking for SQL Server login info, then finally I get the same Connection failed error you listed with the exception on the line: SQL Server Error: 10048. However, the report actually finishes with all the data requested.
I have this same Access front end running on other XP machines with SP1 and Windows 2000 machines with MDAC 2.7 SP1. When the report runs on those machines it only asks for SQL Server login info when the program is first connecting to the db.
Any ideas?
|||Thank you thank you for letting me know about the svrnetcn.exe tool. I have been trying for hours to get a Sharepoint portal going and whilst for the error I had MS KB said enable tcp/ip, it didn't say how to do it for msde. Where did you find out about svrnetcn.exe and are there other useful tools I should know about? I'm ok with osql.
I have seen the error you are getting. It will happen if I'm not using Windows integrated authentication. If I try to connect with osql -U sa -S servername\instancename it doesn't work and gives a server does not exist or access denied. I have to use osql -E -S servername\instancename and it goes in fine.
Hope this helps - even if its a bit late!
Nath
|||
Nathan,
here is the linke which might be useful to you guys
http://www.codeproject.com/database/ConfigureMSDE.asp
Best regards,
Web
MSDE Remote Connect strange problem
I'm trying to connect to the SharePoint MSDE database from Windows XP
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not
exist or access denied.
I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not
exist or access denied.
I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?
Did you ever get an answer to this problem? I'm having a similar error on Windows XP SP2 machines that have MDAC 2.8SP1. I have an MS Access front end that links to SQL Server database using ODBC connections. The report will run, but keeps asking for SQL Server login info, then finally I get the same Connection failed error you listed with the exception on the line: SQL Server Error: 10048. However, the report actually finishes with all the data requested.
I have this same Access front end running on other XP machines with SP1 and Windows 2000 machines with MDAC 2.7 SP1. When the report runs on those machines it only asks for SQL Server login info when the program is first connecting to the db.
Any ideas?
|||Thank you thank you for letting me know about the svrnetcn.exe tool. I have been trying for hours to get a Sharepoint portal going and whilst for the error I had MS KB said enable tcp/ip, it didn't say how to do it for msde. Where did you find out about svrnetcn.exe and are there other useful tools I should know about? I'm ok with osql.
I have seen the error you are getting. It will happen if I'm not using Windows integrated authentication. If I try to connect with osql -U sa -S servername\instancename it doesn't work and gives a server does not exist or access denied. I have to use osql -E -S servername\instancename and it goes in fine.
Hope this helps - even if its a bit late!
Nath
|||
Nathan,
here is the linke which might be useful to you guys
http://www.codeproject.com/database/ConfigureMSDE.asp
Best regards,
Web
Subscribe to:
Posts (Atom)