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

MSDE SP4 install problem

I attempted to install MSDE SP4 (file SQL2000.MSDE-KB884525-SP4-x86-ENU) on a WinXP Pro SP2 machine.

Command used:

setup SAPWD="ourpw" SECURITYMODE=SQL /L*v c:\MSDELog.log

Install log shows successful install.

MSDE appears to function properly, service starts automatically after reboot, etc.

I can open and work with DB's with a freebie 3rd party GUI called DbaMGR2K, through which I have added the necessary DB user for our locally running ASP application to use the db.

However, when I try to use the DB with our locally running ASP application - connecting with ADO from a dll we wrote, I get the following:

"[DNETLIB]{ConnectionOpen (Connect()).]SQL Server does not exist or access denied"

Any help appreciated.

day10

Hi,

make sure that you connect to the same database and you are using a valid login for connecting. Perhaps you have chosen another authentication mode within the ADO code ? That could explain either the one or the other error message you are getting.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I think we have solved the issue. We used the SQL Server Network Utility to enable TCP/IP (apparently not enabled by default) and now all appears well.

I wonder if there is a way to enable TCP/IP during the install process. Is there an install flag/option?

|||

>> Is there an install flag/option?

Most likely. The flag for this when installing SP3 was "DISABLENETWORKPROTOCOLS=0". I wouldn't think that they would have removed it for SP4.

sql

MSDE setup question

Hello:

I had partitioned my harddrive to have both XP PRO and Red Hat. Got fed up with all that and so used Partition Magic 8.0 to repartition the drive to be one 16 Gig drive. I still have over 8 Gig left on it even after installing VS .NET on it.

I have successfully installed Visual Studio .NET Pro 2003 on it and I can now write programs in VB and see it on my intranet at c:/wwwroot/.

I am now trying to install MSDE 2000 for Developers Using VS .NET. I have downloaded the file from Microsoft and then when I go to install it on my hard drive it tells me it cannot; I have to free up 92.44 Megs for it to be able to extract it to my c drive.

I am a newbee and any help will be GREATLY appreciated!!Sorry but have solved this problem too.

Turns out I was using the wrong download.

Thanx anyways.|||Ohh Boy, you are really working under a tight Hard drive. With 92.44 Megs, any software would complain about free space. Free up some space and try it. Some harddisk space is needed for paging and stuff, so its very normal your program complaining about the disk space. I hope thats what your problem is.

If you are having trouble installing the MSDE, take a look at my blog entry

Let us know your exact issue

MSDE setup errors

I am trying install MSDE on XPSP2 pro. It fails the following set of erros
in the setup log. These lines are from a non-verbose log I created while
running the setup.
Appreciate any help.
Thanks
Shishir
TempFolder is
C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action SkuIt
Setting SqlEdition property failed
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
-V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (B4!D0) [17:39:55:781]: Product: Microsoft SQL Server Desktop Engine
-- Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
I got some info on the possible causes of failure as below. Unfortunately
neither of them help.
If your machine name has lowercase characters then you may be hitting this
issue - http://support.microsoft.com/default...;en-us;Q285100
If you had a old instance of MSDE on the machine you may be hitting this
issue - http://support.microsoft.com/default...b;en-us;816499
"Shishir" wrote:

> I am trying install MSDE on XPSP2 pro. It fails the following set of erros
> in the setup log. These lines are from a non-verbose log I created while
> running the setup.
> Appreciate any help.
> Thanks
> Shishir
> TempFolder is
> C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action SkuIt
> Setting SqlEdition property failed
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\Admin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action ConfigServer
> Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
> -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
> Setup failed to configure the server. Refer to the server error logs and
> setup error logs for more information.
> MSI (s) (B4!D0) [17:39:55:781]: Product: Microsoft SQL Server Desktop Engine
> -- Setup failed to configure the server. Refer to the server error logs and
> setup error logs for more information.
>
|||hi Shishir,
Shishir wrote:
> I am trying install MSDE on XPSP2 pro. It fails the following set
> of erros in the setup log. These lines are from a non-verbose log I
> created while running the setup.
>..
> Engine -- Setup failed to configure the server. Refer to the server
> error logs and setup error logs for more information.
this exception is sometime related to MDAC stack corruption... as no MDAC XP
sp2 refresh is available to fix it, you can only go as indicated in
http://www.macropool.com/en/download/mdac_xp_sp2.html
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I downloaded the repair tool and reregistered all the components. It still
fails the same way.
"Andrea Montanari" wrote:

> hi Shishir,
> Shishir wrote:
> this exception is sometime related to MDAC stack corruption... as no MDAC XP
> sp2 refresh is available to fix it, you can only go as indicated in
> http://www.macropool.com/en/download/mdac_xp_sp2.html
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
sql

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

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.

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

MSDE on WinXP Pro SP2 joined to a domain

Hi,
I have a problem that I cannot find a resolution to.
Recently, I got a laptop and I installed WinXP Pro SP2 on it.
I did this at home so was not near my office domain so I temporarily setup
the laptop as a workgroup computer instead of joining the domain.
Once installed, I then installed MSDE2000RelA.
Everything was working fine.
Then I took the laptop to work, joined the domain, and now MSDE can no
longer connect. All I get in the system tray is a computer tower icon with a
white circle on it. Hovering over that pops up "Cannot connect \\". There
should be a green arrow in the circle when services start.
I have tried uninstalling, re-installing, changing user permissions in group
policy for the guest account? - all sorts of things, but nothing fixes this
issue - and I desperately need MSDE to work on the laptop.
I think it has something to do with the laptop being on the domain, but I
don't know (and that doesn't really make sense to me either).
Can anyone point me to a solution?
Cheers,
Rob
hi Rob
Did u set DISABLENETWORKPROTOCOLS=0 parameter while setup?
by default the setup will take 1 (means disable).
just check out
Dil
|||Ah, no I didn't!
Do I have to reinstall or can I update a previous installation with this
setting?
Cheers,
Rob
|||hi Rob,
RobGT wrote:
> Ah, no I didn't!
> Do I have to reinstall or can I update a previous installation with
> this setting?
please run the Server Network Utility (svrnetcn.exe) to enable the desired
network protocol..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Perfect, thankyou.
It appears to now be working fine.
Shame I found it so difficult to locate this information (I searched online
for ages before coming here to ask the question!)
Thanks a million for resolving this so quickly for me!
Cheers,
Rob

MSDE on Windows 2003

I am trying to connect to a MSDE from XP pro SP2, the MSDE is running on Windows 2003 server and the only way I can connect to the MSDE is if I make the network user an Administrator of the Windows 2003 server.
How can I connect to MSDE without making the user an Admin?
Thanks
Peter
hi Peter,
Peter wrote:
> I am trying to connect to a MSDE from XP pro SP2, the MSDE is running
> on Windows 2003 server and the only way I can connect to the MSDE is
> if I make the network user an Administrator of the Windows 2003
> server.
> How can I connect to MSDE without making the user an Admin?
assuming you've no network problem ( :-D ), what kind of authentication are
you using for that?
I guess you are using Windows authentication (trusted connection)... MSDE
installs by default granting local Windows admins membership to the SQL
Server sysadmins role (BUILTIN\Administrator) so that they are "naturally"
granted login to the MSDE instance... if you want your power/limited users
to be granted to, you have to manually create a SQL Server "Windows"
Login(s) or Windows Group login for all your required users...
please have a look at
http://msdn.microsoft.com/library/de...ga-gz_8dri.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I have added a domain user the the database
EXEC sp_grantlogin 'MyDomain\Peter'
Go
but still user Peter can not connect to the database unless Peter is an
Admin
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3ngpceF1f9poU1@.individual.net...
> hi Peter,
> Peter wrote:
> assuming you've no network problem ( :-D ), what kind of authentication
> are you using for that?
> I guess you are using Windows authentication (trusted connection)... MSDE
> installs by default granting local Windows admins membership to the SQL
> Server sysadmins role (BUILTIN\Administrator) so that they are "naturally"
> granted login to the MSDE instance... if you want your power/limited users
> to be granted to, you have to manually create a SQL Server "Windows"
> Login(s) or Windows Group login for all your required users...
> please have a look at
> http://msdn.microsoft.com/library/de...ga-gz_8dri.asp
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Peter,
Peter wrote:
> I have added a domain user the the database
> EXEC sp_grantlogin 'MyDomain\Peter'
> Go
> but still user Peter can not connect to the database unless Peter is
> an Admin
using and accessing MSDE/SQL Server and it's databases belongs to an
authentication area of the product...
SQL Server uses a sort of 2 phase authentication..
the first one regards login, where someone try to connect to a particular
instance using WinNT (trusted) connections or standard SQL Server
connections (yes, handling both is known as "mixed authentication")
in the second case, standard SQL Server connections, a user id and a
password must be provided, and this information has to be matched against
available SQL Server logins... if a match is found the connecting person has
provided correct information and can log in...
the WinNT (trusted) method does not require this kind of information as the
underlaying OS provides the sid of the against the DC authenticated OS
login, that only need to be matched against a WinNT SQL Server already
granted login or WinNT granted group..
that's to say both kind of authentications need a match in the granted
logins...
Standard SQL Server logins must all be manually added via sp_addlogin system
stored procedure but "sa" "super" login, which is provided by default and
that can not be removed..
as regard WinNT connections, the setup automatically adds a WinNT group
including all WinNT administrators, and this is the reason you can log in
MSDE when logged in Windows as admin...
but all other Windows users/groups have to be manually added via sytem
stored procedure sp_grantlogin
so you have to add you specific WinNT group (say "powerusers") in order to
grant all them permission to log in, or only your specific WinNT account
Domain\Account if you want only him to be granted login...
as regard the second authentication phase, it regards specific access to
each database, and this is done via the sp_grantdbaccess system stored
procedures, that adds an entry in each specific database.dbo.sysusers system
table matching the master.dbo.syslogins system view in the join of the sid
column... this operation generate a database user mapped to a specific
login, allowing him/her to access the desired database with the provided
database role privileges... additional permission can be granted/denied to
each db user, defining the specific security design as required on every db
object and so on, but this is a successive step...
please start reading at
http://msdn.microsoft.com/library/de...ar_da_0n77.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
Thanks for all of your help. I ran both cleanup tools. Still did not solve
problem. I would not give up! After many hours of trial and error I
determine the problem was with a corrupted MDAC component. Reinstall MDAC on
XP sp2? Yes there is a way to do that (very simple). Once I reinstalled
MDAC the client application connected and installed just fine. --RS
"Andrea Montanari" wrote:

> hi Peter,
> Peter wrote:
> using and accessing MSDE/SQL Server and it's databases belongs to an
> authentication area of the product...
> SQL Server uses a sort of 2 phase authentication..
> the first one regards login, where someone try to connect to a particular
> instance using WinNT (trusted) connections or standard SQL Server
> connections (yes, handling both is known as "mixed authentication")
> in the second case, standard SQL Server connections, a user id and a
> password must be provided, and this information has to be matched against
> available SQL Server logins... if a match is found the connecting person has
> provided correct information and can log in...
> the WinNT (trusted) method does not require this kind of information as the
> underlaying OS provides the sid of the against the DC authenticated OS
> login, that only need to be matched against a WinNT SQL Server already
> granted login or WinNT granted group..
> that's to say both kind of authentications need a match in the granted
> logins...
> Standard SQL Server logins must all be manually added via sp_addlogin system
> stored procedure but "sa" "super" login, which is provided by default and
> that can not be removed..
> as regard WinNT connections, the setup automatically adds a WinNT group
> including all WinNT administrators, and this is the reason you can log in
> MSDE when logged in Windows as admin...
> but all other Windows users/groups have to be manually added via sytem
> stored procedure sp_grantlogin
> so you have to add you specific WinNT group (say "powerusers") in order to
> grant all them permission to log in, or only your specific WinNT account
> Domain\Account if you want only him to be granted login...
> as regard the second authentication phase, it regards specific access to
> each database, and this is done via the sp_grantdbaccess system stored
> procedures, that adds an entry in each specific database.dbo.sysusers system
> table matching the master.dbo.syslogins system view in the join of the sid
> column... this operation generate a database user mapped to a specific
> login, allowing him/her to access the desired database with the provided
> database role privileges... additional permission can be granted/denied to
> each db user, defining the specific security design as required on every db
> object and so on, but this is a successive step...
> please start reading at
> http://msdn.microsoft.com/library/de...ar_da_0n77.asp
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||Wrong thread, see above... RS
"Andrea Montanari" wrote:

> hi Peter,
> Peter wrote:
> using and accessing MSDE/SQL Server and it's databases belongs to an
> authentication area of the product...
> SQL Server uses a sort of 2 phase authentication..
> the first one regards login, where someone try to connect to a particular
> instance using WinNT (trusted) connections or standard SQL Server
> connections (yes, handling both is known as "mixed authentication")
> in the second case, standard SQL Server connections, a user id and a
> password must be provided, and this information has to be matched against
> available SQL Server logins... if a match is found the connecting person has
> provided correct information and can log in...
> the WinNT (trusted) method does not require this kind of information as the
> underlaying OS provides the sid of the against the DC authenticated OS
> login, that only need to be matched against a WinNT SQL Server already
> granted login or WinNT granted group..
> that's to say both kind of authentications need a match in the granted
> logins...
> Standard SQL Server logins must all be manually added via sp_addlogin system
> stored procedure but "sa" "super" login, which is provided by default and
> that can not be removed..
> as regard WinNT connections, the setup automatically adds a WinNT group
> including all WinNT administrators, and this is the reason you can log in
> MSDE when logged in Windows as admin...
> but all other Windows users/groups have to be manually added via sytem
> stored procedure sp_grantlogin
> so you have to add you specific WinNT group (say "powerusers") in order to
> grant all them permission to log in, or only your specific WinNT account
> Domain\Account if you want only him to be granted login...
> as regard the second authentication phase, it regards specific access to
> each database, and this is done via the sp_grantdbaccess system stored
> procedures, that adds an entry in each specific database.dbo.sysusers system
> table matching the master.dbo.syslogins system view in the join of the sid
> column... this operation generate a database user mapped to a specific
> login, allowing him/her to access the desired database with the provided
> database role privileges... additional permission can be granted/denied to
> each db user, defining the specific security design as required on every db
> object and so on, but this is a successive step...
> please start reading at
> http://msdn.microsoft.com/library/de...ar_da_0n77.asp
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>

MSDE Not installing

I am running Windows XP Pro. When trying to install MSDE, sql2ksp3, i go to the command line and enter:
setup SAPWD=somegreatpassword SECURITYMODE=SQL and off it goes, gathering information and starting to install.

After a short period of time where the status bar shows about 9 seconds left the status bar runs backwards down to zero and installation stops.

No error message, no crashes, just packs up its tent and goes away.

I have tried running setup from a batch file with the same results.

I have turned off my antivirus program as well as all other programs.

Need Input! - Thanks - T.C.nothing in the System error log?|||Still have the probl if you modify msde setup.ini to install?
e.g.
----------------------------
TARGETDIR="C:\Program Files\Microsoft SQL Server\Mssql$MyInstance\Binn"
DATADIR="C:\Program Files\Microsoft SQL Server\Mssql$MyInstance\Data"
INSTANCENAME="MyInstance"
SECURITYMODE="SQL"
SAPWD="mysapassword"
----------------------------|||Thanks for the tries but...

Adjusting the ini gave me the same negative results.

System Event viewer just tracked that Installer was used.
Application Event viewer returned error message:
"Product: Microsoft SQL Server Desktop Engine -- Installation operation failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."

and when i follow link to web site i am told Sorry but no help here.|||Hi, I am having the same problem. I have done a bit of research on the net and the MS knowledge base and come up with the following kb article...

http://support.microsoft.com/default.aspx?scid=kb;[LN];816499|||And seeHOW TO: Manually Remove a Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Instance|||thank you one and all for try but alas to no avail. I have not a previous version of SQL so i am a bit stuck.|||You can try to open RPC services, and Server Services.
They are in control pad.|||I have found what it was, I also was having the problem. You have to start the service Server started, even if it is Manual, you will still need to start it.

In the instalation docs for MSDE SP3 under Install Log Verbose at the bottom to look for "Value 3", and withing 10 lines of that you find the item that failed. I found "InstallSQLAgentSecurity failed..." I then proceeded to do a search for that on Technet and low and behold there it was. in the very first sentance of "829386 - You Cannot Install MSDE 2000 if the Server Service Is Not Running" it says you need the Server service running.|||I had the same problem, with my Windows XP home. I worked on it for 4 hours, the problem was that you have to have a network set-up on your computer. so I entered into setting up a home network wizard, windows installed all the components and then I installed the MSDE. Worked like a charm. So the way to solve this is to start the network Wizard! and then install MSDE.

Thanks guys.sql

msde manager

I have installed msde on W2K pro and I am looking for an msde manager, something similar to sql enterprise manager. Does anyone have any suggestions?There are several tools you can use to administer MSDE:

ASP.NET Enterprise Manager, an open source SQL Server and MSDE management tool.

ASP.NET WebMatrix (which includes a database management tool) from this web site (click on the Web Matrix tab at the top of this page).

Microsoft's Web Data Administrator is a free web-based MSDE management program written using C# and ASP.NET, and includes source code.

You can also access MSDE using Access.

Don|||Thanks for the info donkiely! Just what I needed|||The Microsoft's Web Data Administrator MSDE Manager has moved it's URL. you get a redirect at the link provided by donkiely. however, in case that link redirect gets taken away the new URL is: http://msdn.microsoft.com/library/default.asp?url=/downloads/list/aspnet.asp

Farewell,
Quilnux|||Got it! Thank You!

msde installation pro

pls help!!!
I've tried to insatll the msde fr the webmatrix program,and have followed the instructions as said in the website.I aslo get all the screen shots showed on the site,but after 2,3 seconds there is a pop up error message saying,"The instance name specified is invalid".
this is a software that I got through the book Sams teach yorself asp.net in 24hours(the accopmpaning cd has the webmatrix msde n some other software),they have said if we have questions about installing to ask this website.
Need advice as soon as possible!!
shelomi-colombo,sri lanaka.

Try these links and download the MSDE or the full version Evaluation edition. Hope this helps.

http://www.microsoft.com/downloads/details.aspx?FamilyId=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en

http://www.microsoft.com/sql/evaluation/trial/default.mspx

|||Hi Shelomi,
Please ask your cousin in Toronto for more help
Agent742

MSDE Installation on a XP Professional WS.

Hello,
I'm experiencing 2 problems after MSDE installation on a XP Pro workstation
on a network.
1. The SQL Service Manager don't show the default instance. If I put
manually is OK, but on every reboot it lose the instance name and show me
nothing.
2. it's impossible to login from an external computer or create any kind of
connection (ODBC or .udl file).
For information the setup was make:
with an .ini file containing
[Options]
INSTANCENAME=fgsoftware
SAPWD=xyzxyz
SECURITYMODE=SQL
The computer is SP2 full patched.
After the first problems I deactivated the windows firewall.
Help me!!!
TIA
Francesco Garganese
FG software
Can't help you with 1 unfortunately - it has happened to me but I've never
quite worked out why...
To log in from an external computer you need to have set the
DISABLENETWORKPROTOLS flag to false when installing. See the readme that
comes with the installer for more details on command line switches.
Also, MSDE from Service Pack 3a onwards, installs in Windows Authentication
mode only by default. see the following kb article for more info:
http://support.microsoft.com/default...;EN-US;Q325022
If you're trying to access it from another machine that is not logged in as
a *domain* user on the same domain (i.e. you must be running a Windows 2003
Server Domain Controller somewhere) then you can only connect using Mixed
Mode Authentication, which as the above article will tell you is disabled by
default.
"Francesco Garganese" <FrancescoGarganese@.discussions.microsoft.com> wrote
in message news:CD18E7C6-6E32-4D27-974D-C744C580C820@.microsoft.com...
> Hello,
> I'm experiencing 2 problems after MSDE installation on a XP Pro
> workstation
> on a network.
> 1. The SQL Service Manager don't show the default instance. If I put
> manually is OK, but on every reboot it lose the instance name and show me
> nothing.
> 2. it's impossible to login from an external computer or create any kind
> of
> connection (ODBC or .udl file).
> For information the setup was make:
> with an .ini file containing
> [Options]
> INSTANCENAME=fgsoftware
> SAPWD=xyzxyz
> SECURITYMODE=SQL
> The computer is SP2 full patched.
> After the first problems I deactivated the windows firewall.
> Help me!!!
> TIA
> --
> Francesco Garganese
> FG software
|||Thank you very much Ben, adding DISABLENETWORKPROTOLS=0 in the paramenters
and reinstalling both problems are resolved!
Sincerely
Francesco Garganese
FG software

MSDE Installation Help

Hi
I am trying to instal MSDE 2000 on a Windows XP Pro SP2 machine. I type in
....
"Setup.exe /qb+ INSTANCENAME=NetSDK DISABLENETWORKPROTOCOLS=1 SAPWD=<YOUR SA
PASSWORD>" at the command prompt and the MSDE setup begins to take place. At
the nearly the end of the install, I get a pop-up dialog stating the the
instalation failed.
I checked setupapi.log file under C:\winnt and the follwoing error was in
their...
"
[2005/01/03 21:29:08 2672.1]
#-199 Executing "C:\Documents and Settings\Owner\Local
Settings\Temp\IXP000.TMP\dasetup.exe" with command line: /Q /N
#E077 Could not locate a non-empty section [DefaultInstall] when calculating
disk space in "C:\Documents and Settings\Owner\Local
Settings\Temp\IXP000.TMP\noop.inf". Error 0xe0000102: The required line was
not found in the INF."
Anyone have any ideas as to what the above means. Also, I checked the
dasetup.log file that was created when attempting to install MSDE and I
noticed the following...
: ****************************************
: * Beginning of Install *
: ****************************************
Starting Install: Current Date/Time (U.S. Local Time): 01/03/2005 : 21:29:07
Path: C:\WINNT;C:\WINNT\system32;
Localization: Machine Locale set to: English_United States.1252
Command Line Parameters:
Suppress Reboot: 0
Quiet/Silent Mode: 1
Logging Level: 3
INI File: dasetup.ini
Windows Directory: C:\WINNT
Progress: Loading Resource Library.
Progress: Parsing INI File.
*************************:
** Begin INI File Dump **:
*************************:
Ini Section: General
: ProductName = Microsoft Data Access Components 2.7
: ProductBuild = 2.71.9040.2
: ProductUrl = http://www.microsoft.com/data
: ProductVersionKey = SOFTWARE\Microsoft\DataAccess
: ProductVersionValue = FullInstallVer
: InstanceName = MDAC
: CheckInUseFiles = 1
: EULAFile = MDACEULA.RTF
: EULAType = rtf
: SupportsTS = 1
: SupportsMUI = 0
: CheckForDiskSpace = 1
: ValidOs = 4294967295
I find it starnge that the install is trying to use MDAC 2.7 when I
currently have MDAC 2.8 SP1 installed on my machine (I verified this through
the MDAC compcheck app).
Anyone have any ideas as to what is going on?
PS Sorry for the long message
Thanks
I also found this error in the dahotfix.log
"
[05:03:12]: An error occurred while setup was trying to verify the version
of Microsoft Data Access Components current installed on the machine.
Either the version currently installed does not match the version of this
hotfix package, or setup was unable to determine the version currently
installed.
["
"John Rydenbark" wrote:

> Hi
> I am trying to instal MSDE 2000 on a Windows XP Pro SP2 machine. I type in
> ...
> "Setup.exe /qb+ INSTANCENAME=NetSDK DISABLENETWORKPROTOCOLS=1 SAPWD=<YOUR SA
> PASSWORD>" at the command prompt and the MSDE setup begins to take place. At
> the nearly the end of the install, I get a pop-up dialog stating the the
> instalation failed.
> I checked setupapi.log file under C:\winnt and the follwoing error was in
> their...
> "
> [2005/01/03 21:29:08 2672.1]
> #-199 Executing "C:\Documents and Settings\Owner\Local
> Settings\Temp\IXP000.TMP\dasetup.exe" with command line: /Q /N
> #E077 Could not locate a non-empty section [DefaultInstall] when calculating
> disk space in "C:\Documents and Settings\Owner\Local
> Settings\Temp\IXP000.TMP\noop.inf". Error 0xe0000102: The required line was
> not found in the INF."
> Anyone have any ideas as to what the above means. Also, I checked the
> dasetup.log file that was created when attempting to install MSDE and I
> noticed the following...
> : ****************************************
> : * Beginning of Install *
> : ****************************************
> Starting Install: Current Date/Time (U.S. Local Time): 01/03/2005 : 21:29:07
> Path: C:\WINNT;C:\WINNT\system32;
> Localization: Machine Locale set to: English_United States.1252
> Command Line Parameters:
> Suppress Reboot: 0
> Quiet/Silent Mode: 1
> Logging Level: 3
> INI File: dasetup.ini
> Windows Directory: C:\WINNT
> Progress: Loading Resource Library.
> Progress: Parsing INI File.
> *************************:
> ** Begin INI File Dump **:
> *************************:
> Ini Section: General
> : ProductName = Microsoft Data Access Components 2.7
> : ProductBuild = 2.71.9040.2
> : ProductUrl = http://www.microsoft.com/data
> : ProductVersionKey = SOFTWARE\Microsoft\DataAccess
> : ProductVersionValue = FullInstallVer
> : InstanceName = MDAC
> : CheckInUseFiles = 1
> : EULAFile = MDACEULA.RTF
> : EULAType = rtf
> : SupportsTS = 1
> : SupportsMUI = 0
> : CheckForDiskSpace = 1
> : ValidOs = 4294967295
> I find it starnge that the install is trying to use MDAC 2.7 when I
> currently have MDAC 2.8 SP1 installed on my machine (I verified this through
> the MDAC compcheck app).
> Anyone have any ideas as to what is going on?
> PS Sorry for the long message
> Thanks
>

MSDE Installation Help

Hi
I am trying to instal MSDE 2000 on a Windows XP Pro SP2 machine. I type in
...
"Setup.exe /qb+ INSTANCENAME=NetSDK DISABLENETWORKPROTOCOLS=1 SAPWD=<YOUR SA
PASSWORD>" at the command prompt and the MSDE setup begins to take place. At
the nearly the end of the install, I get a pop-up dialog stating the the
instalation failed.
I checked setupapi.log file under C:\winnt and the follwoing error was in
their...
"
[2005/01/03 21:29:08 2672.1]
#-199 Executing "C:\Documents and Settings\Owner\Local
Settings\Temp\IXP000.TMP\dasetup.exe" with command line: /Q /N
#E077 Could not locate a non-empty section [DefaultInstall] when calcula
ting
disk space in "C:\Documents and Settings\Owner\Local
Settings\Temp\IXP000.TMP\noop.inf". Error 0xe0000102: The required line was
not found in the INF."
Anyone have any ideas as to what the above means. Also, I checked the
dasetup.log file that was created when attempting to install MSDE and I
noticed the following...
: ****************************************
: * Beginning of Install *
: ****************************************
Starting Install: Current Date/Time (U.S. Local Time): 01/03/2005 : 21:29:07
Path: C:\WINNT;C:\WINNT\system32;
Localization: Machine Locale set to: English_United States.1252
Command Line Parameters:
Suppress Reboot: 0
Quiet/Silent Mode: 1
Logging Level: 3
INI File: dasetup.ini
Windows Directory: C:\WINNT
Progress: Loading Resource Library.
Progress: Parsing INI File.
*************************:
** Begin INI File Dump **:
*************************:
Ini Section: General
: ProductName = Microsoft Data Access Components 2.7
: ProductBuild = 2.71.9040.2
: ProductUrl = http://www.microsoft.com/data
: ProductVersionKey = SOFTWARE\Microsoft\DataAccess
: ProductVersionValue = FullInstallVer
: InstanceName = MDAC
: CheckInUseFiles = 1
: EULAFile = MDACEULA.RTF
: EULAType = rtf
: SupportsTS = 1
: SupportsMUI = 0
: CheckForDiskSpace = 1
: ValidOs = 4294967295
I find it starnge that the install is trying to use MDAC 2.7 when I
currently have MDAC 2.8 SP1 installed on my machine (I verified this through
the MDAC compcheck app).
Anyone have any ideas as to what is going on?
PS Sorry for the long message
ThanksI also found this error in the dahotfix.log
"
[05:03:12]: An error occurred while setup was trying to verify the versi
on
of Microsoft Data Access Components current installed on the machine.
Either the version currently installed does not match the version of this
hotfix package, or setup was unable to determine the version currently
installed.
["
"John Rydenbark" wrote:

> Hi
> I am trying to instal MSDE 2000 on a Windows XP Pro SP2 machine. I type in
> ...
> "Setup.exe /qb+ INSTANCENAME=NetSDK DISABLENETWORKPROTOCOLS=1 SAPWD=<YOUR
SA
> PASSWORD>" at the command prompt and the MSDE setup begins to take place.
At
> the nearly the end of the install, I get a pop-up dialog stating the the
> instalation failed.
> I checked setupapi.log file under C:\winnt and the follwoing error was in
> their...
> "
> [2005/01/03 21:29:08 2672.1]
> #-199 Executing "C:\Documents and Settings\Owner\Local
> Settings\Temp\IXP000.TMP\dasetup.exe" with command line: /Q /N
> #E077 Could not locate a non-empty section [DefaultInstall] when calcu
lating
> disk space in "C:\Documents and Settings\Owner\Local
> Settings\Temp\IXP000.TMP\noop.inf". Error 0xe0000102: The required line wa
s
> not found in the INF."
> Anyone have any ideas as to what the above means. Also, I checked the
> dasetup.log file that was created when attempting to install MSDE and I
> noticed the following...
> : ****************************************
> : * Beginning of Install *
> : ****************************************
> Starting Install: Current Date/Time (U.S. Local Time): 01/03/2005 : 21:29:
07
> Path: C:\WINNT;C:\WINNT\system32;
> Localization: Machine Locale set to: English_United States.1252
> Command Line Parameters:
> Suppress Reboot: 0
> Quiet/Silent Mode: 1
> Logging Level: 3
> INI File: dasetup.ini
> Windows Directory: C:\WINNT
> Progress: Loading Resource Library.
> Progress: Parsing INI File.
> *************************:
> ** Begin INI File Dump **:
> *************************:
> Ini Section: General
> : ProductName = Microsoft Data Access Components 2.7
> : ProductBuild = 2.71.9040.2
> : ProductUrl = http://www.microsoft.com/data
> : ProductVersionKey = SOFTWARE\Microsoft\DataAccess
> : ProductVersionValue = FullInstallVer
> : InstanceName = MDAC
> : CheckInUseFiles = 1
> : EULAFile = MDACEULA.RTF
> : EULAType = rtf
> : SupportsTS = 1
> : SupportsMUI = 0
> : CheckForDiskSpace = 1
> : ValidOs = 4294967295
> I find it starnge that the install is trying to use MDAC 2.7 when I
> currently have MDAC 2.8 SP1 installed on my machine (I verified this throu
gh
> the MDAC compcheck app).
> Anyone have any ideas as to what is going on?
> PS Sorry for the long message
> Thanks
>

MSDE installation freezes

I am installtion MSDE on a Windows XP Pro. The install gets through to 5 seconds and freezes. THis sits for about an hour and nothing happens. The Microsoft SQL Server folder is created, but the services are not created. We tried to reinstall many times and removed the registry key before each reinstall (after uninstalling and rebooting). Any ideas about what could be wrong?I've got that pb yesterday...
and solved it

what is your command line to install MSDE ?|||I am using an executable. Not using a command line. THis is suppose to be a "fresh" install.|||when you install MSDE you uncompress some files
then to run the setup you should go into DOS
to pass some parameters to the setup

(administrator password and instance name)

consult this clear'n'neat web site

http://www.csi-seattle.com/~csiftp001/DDM/Install_Media/Docs/Installation%20Procedure%20for%20MSDE%202000.pdf|||Actually this is a setup file that uncompress the files and installs using an install shield dialog|||does it ask for an instancename or a mode connection check ?|||The install creates a named instance automatically.|||do you see it created (instance name) ?|||No, normally I would see it in the services, but I do have any servcies related to SQL or the instance. I also am missing the folder under the Microsoft SQL Server folder.|||why don't you try installing it without your shield ?

MSDE Installation failure

Hi,
I've downloaded MSDE 2000 R1 from Internet. Tried to install on my PC with
running on Windows XP Pro with SP2.
When everytime i runned the Setup.exe, it will prompt for "A Strong SA
password is required for security reasons. Please use SAPWD switch to supply
the same. Refer to readme for more details. Setup will now exit".
Everyone know about this ? anyway to proceed the installation ?
Thank you
You need to either supply commandline arguments, or edit the empty
setup.ini file and supply them as options there. Go to
msdn.microsoft.com and search for articles like: installing MSDE.
-nick
On Tue, 3 May 2005 01:08:05 -0700, "CK" <CK@.discussions.microsoft.com>
wrote:

>Hi,
>I've downloaded MSDE 2000 R1 from Internet. Tried to install on my PC with
>running on Windows XP Pro with SP2.
>When everytime i runned the Setup.exe, it will prompt for "A Strong SA
>password is required for security reasons. Please use SAPWD switch to supply
>the same. Refer to readme for more details. Setup will now exit".
>Everyone know about this ? anyway to proceed the installation ?
>Thank you
|||hi,
CK wrote:
> Hi,
> I've downloaded MSDE 2000 R1 from Internet. Tried to install on my PC
> with running on Windows XP Pro with SP2.
> When everytime i runned the Setup.exe, it will prompt for "A Strong SA
> password is required for security reasons. Please use SAPWD switch to
> supply the same. Refer to readme for more details. Setup will now
> exit".
> Everyone know about this ? anyway to proceed the installation ?
> Thank you
please have a look at
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for all setup parameter...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE installation failure

I am trying to install MSDE 2000 rel A onto a machine running Win XP Pro SP2,
Keep getting error failed to configure the server and my error logs show this
message "Specified driver could not be loaded due to system error 126 (SQL
Server)." Everything that I have found refers to MDAC issues but SP2
installs the latest MDAC 2.81. I ran component checked and everything matched
when run for 2.8 on XP SP2. The only thing Not Found were odbdbcp.dll
sqlsvr32.dll and sqlsvr32.rll and according to documentation Not Found
just means they were not used in the version selected. Any ideas?
Hi,
I'm not sure, but I heard somewhere that MSDE 2000 relA (or sp3a), cann't be
installed on top of Windows XP SP2.
You must uninstall SP2, install MSDE sp3a and reinstall SP2.
I didn't test it.
HTH
AF
"FirePro2005" <FirePro2005@.discussions.microsoft.com> wrote in message
news:3EC1D631-6F00-4B85-A964-FFE79313533A@.microsoft.com...
> I am trying to install MSDE 2000 rel A onto a machine running Win XP Pro
SP2,
> Keep getting error failed to configure the server and my error logs show
this
> message "Specified driver could not be loaded due to system error 126
(SQL
> Server)." Everything that I have found refers to MDAC issues but SP2
> installs the latest MDAC 2.81. I ran component checked and everything
matched
> when run for 2.8 on XP SP2. The only thing Not Found were odbdbcp.dll
> sqlsvr32.dll and sqlsvr32.rll and according to documentation Not
Found
> just means they were not used in the version selected. Any ideas?
|||I have installed MSDE 2000 Rel A on a quite a few machines with XP and
SP2 without such issues. My issue had always been the same - inability
to connect from a remote system. I have finally figure out that by
default MSDE does not install with Network mode turned on. On top of
that, SP 2 blocks all ports, including 1433 used by MSDE, in the
firewall.
So, I have learned to install with the "Mized Mode Authentication"
turned on and also to open up Port 1433.
- manzoor

MSDE Installation

Hi!

I have a big problem installing msde on an XP Pro. When I try to install (run setup), the process starts and when its nearly finished the progess bar goes quickly down.
There is no error msg or something like that. The event no is 11708 (msi information).

I tried setup with many differnt parameters SAPWD=... Always the same: When quite finished installing, it ends.

I looked now for many hours in the forum and did not find any help.
Does anyone have a good solution ?

thxTry fully removing the current installation, if it's in Add/Remove programs - then, try following this tutorial:
http://aspnet101.com/aspnet101/tutorials.aspx?id=44

If this doesn't work, I'd say, offhand, that you might have some computer problems/issues. If you have Norton's - try running their utilities on your computer to see if anything turns up.

MSDE in WinXP Pro SP2

I have installed MSDE in WinXP Professional SP2, and already enabled the
TCP/IP protocol in SQL Server Network Utility. However, I find that it is
failure to connect the database by calling the IP Address even I test it
locally (use sa/window authorization) , but it is ok by calling the computer
name or (local) (also use sa/window authorization) . I have disabled the
firewall and the situation is no change.
Anyone have same experience on this case?

> Anyone have same experience on this case?
Yes, I have. But I have no answer how to fix it. There must be a bug
somwhere.
Regards,
Lars-Inge Tonnessen