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.
Showing posts with label exe. Show all posts
Showing posts with label exe. Show all posts
Friday, March 30, 2012
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 sp4 upgrade syntax
Trying to upgrade from sp3. Syntax is:
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
SECURITYMODE=SQL UPGRADEUSER=SA UPGRADEPWD=ACMEPWD /L*v c:\msde.log
message log always shows:
An error was encountered during connection to server: 1
Ending custom action UpgDetectBlankSaLogin().
Action ended 14:17:12:
UpgDetectBlankSaLogin.2D02443E_7002_4C0B_ABC9_EAB2 C064397B. Return value 3.
Action ended 14:17:12: INSTALL. Return value 3.
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir = c:\Microsoft SQL Server\Mssql\data\
Property(S): SqlProgramDir = c:\Microsoft SQL Server\Mssql\binn\
Property(S): SqlInstanceName = ACME
Property(S): SqlSecurityMode = SQL
Property(S): SqlUpgradeUser = sa
Property(S): SqlUpgrade...
hi,
kwicker wrote:
> Trying to upgrade from sp3. Syntax is:
> C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
> SECURITYMODE=SQL UPGRADEUSER=SA UPGRADEPWD=ACMEPWD /L*v c:\msde.log
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME SAPWD=xxxx
SECURITYMODE=SQL /L*v c:\msde.log
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||So you think I don't need to use the UpgradeUser syntax? I've tried what you
wrote (C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
SAPWD=xxxx SECURITYMODE=SQL /L*v c:\msde.log) and I still receive the same
error. At end of log it is returning a 1603. SP3 was installed with a
strong password. What am I missing here?
"Andrea Montanari" wrote:
> hi,
> kwicker wrote:
> C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME SAPWD=xxxx
> SECURITYMODE=SQL /L*v c:\msde.log
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi,
kwicker wrote:
> So you think I don't need to use the UpgradeUser syntax? I've tried
> what you wrote (C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN
> INSTANCENAME=ACME SAPWD=xxxx SECURITYMODE=SQL /L*v c:\msde.log) and
> I still receive the same error. At end of log it is returning a
> 1603. SP3 was installed with a strong password. What am I missing
> here?
you have to provide the strong password you initially provided at MSDE
installation...
or... you can log in via oSql.exe with a trusted connection (as long as you
are logged in Windows as a local admini) and set the sa password to
wathever you want via
EXEC sp_password @.new = 'whatever' . @.loginane = 'sa'
then do upgrade via
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME SAPWD=whatever
SECURITYMODE=SQL /L*v c:\msde.log
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I still receive the same error of "UpgDetectBlankSaLogin" looking at the
Return Value 3 area of the log file. At end of log it is returning a 1603. I
know I have the correct password because I installed sp3 on this test system
just to test the upgrade to sp4.
This is the syntax I used:
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
SAPWD=mypassword SECURITYMODE=SQL /L*v c:\msde.log
I cannot get anything to work that does NOT produce the errors above! I
tried not entering an SAPWD just to see what error I would get and no matter
what syntax I seem to enter, I still get the same error!
|||hi,
kwicker wrote:
> I still receive the same error of "UpgDetectBlankSaLogin" looking at
> the Return Value 3 area of the log file. At end of log it is
> returning a 1603. I know I have the correct password because I
> installed sp3 on this test system just to test the upgrade to sp4.
> This is the syntax I used:
> C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
> SAPWD=mypassword SECURITYMODE=SQL /L*v c:\msde.log
> I cannot get anything to work that does NOT produce the errors above!
> I tried not entering an SAPWD just to see what error I would get and
> no matter what syntax I seem to enter, I still get the same error!
except fo including /L*v c:\msde.log in quotes, like /L*v "c:\msde.log" , I
really have no further idea...
I always succesfully upgraded MSDE RTM and sp3/sp3a instances...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Slowly bullying my way through this. Here's the latest error I receive:
states osql.exe did not return properly. Unable to run the script files.
Error code=1
This is the syntax that produced the error:
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN blanksapwd=1 INSTANCENAME=ACME
SAPWD=mypassword SECURITYMODE=SQL /L*v c:\msde.log
Can send error log if needed. Please help...this is VERY frustrating.
|||hi,
kwicker wrote:
> Slowly bullying my way through this. Here's the latest error I
> receive:
> states osql.exe did not return properly. Unable to run the script
> files. Error code=1
> This is the syntax that produced the error:
> C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN blanksapwd=1
> INSTANCENAME=ACME SAPWD=mypassword SECURITYMODE=SQL /L*v c:\msde.log
> Can send error log if needed. Please help...this is VERY frustrating.
:-|
just a note... blanksapwd=1 and SAPWD=mypassword shoud be mutual exclusive..
and /L*v c:\msde.log should be /L*v "c:\msde.log" to prevent long name
problems... but should not cause problem in the case...
sorry... out of ideas... never heard this exception on sp4 .. but please
have a look at http://tinyurl.com/bu5r3
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
SECURITYMODE=SQL UPGRADEUSER=SA UPGRADEPWD=ACMEPWD /L*v c:\msde.log
message log always shows:
An error was encountered during connection to server: 1
Ending custom action UpgDetectBlankSaLogin().
Action ended 14:17:12:
UpgDetectBlankSaLogin.2D02443E_7002_4C0B_ABC9_EAB2 C064397B. Return value 3.
Action ended 14:17:12: INSTALL. Return value 3.
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir = c:\Microsoft SQL Server\Mssql\data\
Property(S): SqlProgramDir = c:\Microsoft SQL Server\Mssql\binn\
Property(S): SqlInstanceName = ACME
Property(S): SqlSecurityMode = SQL
Property(S): SqlUpgradeUser = sa
Property(S): SqlUpgrade...
hi,
kwicker wrote:
> Trying to upgrade from sp3. Syntax is:
> C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
> SECURITYMODE=SQL UPGRADEUSER=SA UPGRADEPWD=ACMEPWD /L*v c:\msde.log
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME SAPWD=xxxx
SECURITYMODE=SQL /L*v c:\msde.log
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||So you think I don't need to use the UpgradeUser syntax? I've tried what you
wrote (C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
SAPWD=xxxx SECURITYMODE=SQL /L*v c:\msde.log) and I still receive the same
error. At end of log it is returning a 1603. SP3 was installed with a
strong password. What am I missing here?
"Andrea Montanari" wrote:
> hi,
> kwicker wrote:
> C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME SAPWD=xxxx
> SECURITYMODE=SQL /L*v c:\msde.log
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi,
kwicker wrote:
> So you think I don't need to use the UpgradeUser syntax? I've tried
> what you wrote (C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN
> INSTANCENAME=ACME SAPWD=xxxx SECURITYMODE=SQL /L*v c:\msde.log) and
> I still receive the same error. At end of log it is returning a
> 1603. SP3 was installed with a strong password. What am I missing
> here?
you have to provide the strong password you initially provided at MSDE
installation...
or... you can log in via oSql.exe with a trusted connection (as long as you
are logged in Windows as a local admini) and set the sa password to
wathever you want via
EXEC sp_password @.new = 'whatever' . @.loginane = 'sa'
then do upgrade via
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME SAPWD=whatever
SECURITYMODE=SQL /L*v c:\msde.log
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I still receive the same error of "UpgDetectBlankSaLogin" looking at the
Return Value 3 area of the log file. At end of log it is returning a 1603. I
know I have the correct password because I installed sp3 on this test system
just to test the upgrade to sp4.
This is the syntax I used:
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
SAPWD=mypassword SECURITYMODE=SQL /L*v c:\msde.log
I cannot get anything to work that does NOT produce the errors above! I
tried not entering an SAPWD just to see what error I would get and no matter
what syntax I seem to enter, I still get the same error!
|||hi,
kwicker wrote:
> I still receive the same error of "UpgDetectBlankSaLogin" looking at
> the Return Value 3 area of the log file. At end of log it is
> returning a 1603. I know I have the correct password because I
> installed sp3 on this test system just to test the upgrade to sp4.
> This is the syntax I used:
> C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
> SAPWD=mypassword SECURITYMODE=SQL /L*v c:\msde.log
> I cannot get anything to work that does NOT produce the errors above!
> I tried not entering an SAPWD just to see what error I would get and
> no matter what syntax I seem to enter, I still get the same error!
except fo including /L*v c:\msde.log in quotes, like /L*v "c:\msde.log" , I
really have no further idea...
I always succesfully upgraded MSDE RTM and sp3/sp3a instances...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Slowly bullying my way through this. Here's the latest error I receive:
states osql.exe did not return properly. Unable to run the script files.
Error code=1
This is the syntax that produced the error:
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN blanksapwd=1 INSTANCENAME=ACME
SAPWD=mypassword SECURITYMODE=SQL /L*v c:\msde.log
Can send error log if needed. Please help...this is VERY frustrating.
|||hi,
kwicker wrote:
> Slowly bullying my way through this. Here's the latest error I
> receive:
> states osql.exe did not return properly. Unable to run the script
> files. Error code=1
> This is the syntax that produced the error:
> C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN blanksapwd=1
> INSTANCENAME=ACME SAPWD=mypassword SECURITYMODE=SQL /L*v c:\msde.log
> Can send error log if needed. Please help...this is VERY frustrating.
:-|
just a note... blanksapwd=1 and SAPWD=mypassword shoud be mutual exclusive..
and /L*v c:\msde.log should be /L*v "c:\msde.log" to prevent long name
problems... but should not cause problem in the case...
sorry... out of ideas... never heard this exception on sp4 .. but please
have a look at http://tinyurl.com/bu5r3
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Wednesday, March 28, 2012
MSDE setup failed
was installing MSDE for use with Web matrix
thot had done all correctly ie the setup.exe sapwd=xxxxx securitymode=sql from the command prompt
was told that setup has failed
where is the problemWas there any other information provided with the error message? If the message was "Setup Failed to configure the server" then this might help:
thot had done all correctly ie the setup.exe sapwd=xxxxx securitymode=sql from the command prompt
was told that setup has failed
where is the problemWas there any other information provided with the error message? If the message was "Setup Failed to configure the server" then this might help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816499&Product=sql
Also, there should be a setup log created that might have more information.
MSDE Service permissions
Hi All,
I'm installing MSDE 2000 with a custom application (launched using
setup.exe, not integrating merge modules) and am having a problem with the
service permissions for SQL services. The custom app installer is being
build with Installshield Pro 6.3.
Everything works fine for admin users, but MSDE won't start for non-admin
users. The MSSQL$Instance service won't start unless it's logging on a Local
System.
I need non-admin users to have access to the database.
Is there any way to setup MSDE on install to work for everyone?
What does one need to do to manually configure it after install to work for
everyone?
Thanks,
leon.
hi Leon,
"LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
news:Oe0QyXhhEHA.904@.TK2MSFTNGP09.phx.gbl...
> Hi All,
> I'm installing MSDE 2000 with a custom application (launched using
> setup.exe, not integrating merge modules) and am having a problem with the
> service permissions for SQL services. The custom app installer is being
> build with Installshield Pro 6.3.
> Everything works fine for admin users, but MSDE won't start for non-admin
> users. The MSSQL$Instance service won't start unless it's logging on a
Local
> System.
> I need non-admin users to have access to the database.
> Is there any way to setup MSDE on install to work for everyone?
> What does one need to do to manually configure it after install to work
for
> everyone?
usually MSDE is installed setting the relative services account to
LocalSystem, that provide (far) enought privileges (on the local machine)
for all logged users...
have a look at
http://msdn.microsoft.com/library/de...l/THCMCh18.asp
for more restrictions..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
By default the services use Local System option for log on. This worked fine
for all admin users but did not work for a non-admin user. When a non-admin
user logs in (local or domain user), the services won't start using Local
System. (side note: this is on a WinXP Pro machine). The non-admin user
cannot start or stop any service.
We did get it to work for the non-admin user by using the local
administrator account for log on (I goofed when trying it the first time by
using domain admin password instead of local admin password). This is not
the way we want to go, but it's the only way it does work right now.
I did find one thing via your link, in the Installation Recommendations:
"Create a least privileged local account with which to run the SQL Server
service. Use this account when you are prompted for service settings during
setup. Do not use the local system account or an administrator account. "
There is no prompt when installing MSDE. What exactly is a "least priviledge
local account"?
Any other suggestions are most welcome!
Thanks for your help.
leon.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2okhj5Fbml6lU1@.uni-berlin.de...[vbcol=seagreen]
> hi Leon,
> "LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
> news:Oe0QyXhhEHA.904@.TK2MSFTNGP09.phx.gbl...
the[vbcol=seagreen]
non-admin
> Local
> for
> usually MSDE is installed setting the relative services account to
> LocalSystem, that provide (far) enought privileges (on the local machine)
> for all logged users...
> have a look at
>
http://msdn.microsoft.com/library/de...l/THCMCh18.asp
> for more restrictions..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Leon,
"LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
news:eO0WPBthEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi Andrea,
> By default the services use Local System option for log on. This worked
fine
> for all admin users but did not work for a non-admin user. When a
non-admin
> user logs in (local or domain user), the services won't start using Local
> System. (side note: this is on a WinXP Pro machine). The non-admin user
> cannot start or stop any service.
actually they shoul'd run, as all this is intended to work this way... SQL
Server is run under another privileged account than the current logged
account, which only needs to connect to the specified server and query for
information..
perhaps you have to check your local policies...
> We did get it to work for the non-admin user by using the local
> administrator account for log on (I goofed when trying it the first time
by
> using domain admin password instead of local admin password). This is not
> the way we want to go, but it's the only way it does work right now.
I usually use a local account (not LocalSystem), with enought rights on
relevent share(s) if needed..
> I did find one thing via your link, in the Installation Recommendations:
> "Create a least privileged local account with which to run the SQL Server
> service. Use this account when you are prompted for service settings
during
> setup. Do not use the local system account or an administrator account. "
> There is no prompt when installing MSDE. What exactly is a "least
priviledge
> local account"?
no, there's not... that info is for a full blown SQL Server installation..
you have to set that property after MSDE installed, accessing the services
management applet... perhaps it can be done via WMI, but never tried it..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||more,
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> ha scritto nel messaggio
news:2omoccFcfn07U1@.uni-berlin.de...[vbcol=seagreen]
> hi Leon,
> "LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
> news:eO0WPBthEHA.2908@.TK2MSFTNGP10.phx.gbl...
Local[vbcol=seagreen]
they do not have to... set the service's "start at boostrap" property...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||The instructions on the SQLServer Installation Recommendations say to create
a new user, remove it from the users group and use it for the service login.
We created an "msde" user, removed it from Users group, set it as the Log On
As account (it is listed in the "Log on as a service" policy), gave full
access rights for the data files to Everyone, and it doesn't work.
So you have installed MSDE 2000 A and had its service (MSDE$InstanceName)
starting with a non-admin log in?
If so, you must have some magic touch because we're trying this on 2
separate machines with the same failure on each. We'll be trying it on a
fresh XP install shortly, but I don't really expect different results.
Even when logged into the XP as an administrator, setting the MSDE service
login account to "msde" causes the service to fail on a start attempt. It
gives the following error:
Could not start the MSDE$... service on Local Computer.
Error 5: Access is Denied
How do you access the "start at boostrap" property of a service?
thanks,
leon.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2omogoFcbbrgU1@.uni-berlin.de...[vbcol=seagreen]
> more,
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> ha scritto nel messaggio
> news:2omoccFcfn07U1@.uni-berlin.de...
> Local
user
> they do not have to... set the service's "start at boostrap" property...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Leon,
"LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
news:%233zBrHvhEHA.644@.tk2msftngp13.phx.gbl...
> The instructions on the SQLServer Installation Recommendations say to
create
> a new user, remove it from the users group and use it for the service
login.
> We created an "msde" user, removed it from Users group, set it as the Log
On
> As account (it is listed in the "Log on as a service" policy), gave full
> access rights for the data files to Everyone, and it doesn't work.
> So you have installed MSDE 2000 A and had its service (MSDE$InstanceName)
> starting with a non-admin log in?
> If so, you must have some magic touch because we're trying this on 2
> separate machines with the same failure on each. We'll be trying it on a
> fresh XP install shortly, but I don't really expect different results.
> Even when logged into the XP as an administrator, setting the MSDE service
> login account to "msde" causes the service to fail on a start attempt. It
> gives the following error:
> Could not start the MSDE$... service on Local Computer.
> Error 5: Access is Denied
I do always use a local admin account, and I never use the special
LocalSystem account, created just for this purpose and never use an actual
local or domain administrator account. The account must be in the local
Administrators group if you're installing SQL Server on Windows NT or
Windows 2000. You can create this account before you begin installing SQL
Server, or you can change the account under which SQL Server runs at a later
time.
Setting less privileges is intended in not using a Domain Admin account for
network protection.
> How do you access the "start at boostrap" property of a service?
in the service management, select Startup Mode = automatic
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea
Sorry, referring to the automatic service startup as "start at bootstrap"
property is a little different terminology than I am used to. I do
understand the automatic startup option.
We will just include some instructions for setting up the app for non-admin
users.
Thanks for your help.
leon.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2ong8qFcg0ccU1@.uni-berlin.de...[vbcol=seagreen]
> hi Leon,
> "LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
> news:%233zBrHvhEHA.644@.tk2msftngp13.phx.gbl...
> create
> login.
Log[vbcol=seagreen]
> On
(MSDE$InstanceName)[vbcol=seagreen]
service[vbcol=seagreen]
It
> I do always use a local admin account, and I never use the special
> LocalSystem account, created just for this purpose and never use an actual
> local or domain administrator account. The account must be in the local
> Administrators group if you're installing SQL Server on Windows NT or
> Windows 2000. You can create this account before you begin installing SQL
> Server, or you can change the account under which SQL Server runs at a
later
> time.
> Setting less privileges is intended in not using a Domain Admin account
for
> network protection.
> in the service management, select Startup Mode = automatic
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
I'm installing MSDE 2000 with a custom application (launched using
setup.exe, not integrating merge modules) and am having a problem with the
service permissions for SQL services. The custom app installer is being
build with Installshield Pro 6.3.
Everything works fine for admin users, but MSDE won't start for non-admin
users. The MSSQL$Instance service won't start unless it's logging on a Local
System.
I need non-admin users to have access to the database.
Is there any way to setup MSDE on install to work for everyone?
What does one need to do to manually configure it after install to work for
everyone?
Thanks,
leon.
hi Leon,
"LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
news:Oe0QyXhhEHA.904@.TK2MSFTNGP09.phx.gbl...
> Hi All,
> I'm installing MSDE 2000 with a custom application (launched using
> setup.exe, not integrating merge modules) and am having a problem with the
> service permissions for SQL services. The custom app installer is being
> build with Installshield Pro 6.3.
> Everything works fine for admin users, but MSDE won't start for non-admin
> users. The MSSQL$Instance service won't start unless it's logging on a
Local
> System.
> I need non-admin users to have access to the database.
> Is there any way to setup MSDE on install to work for everyone?
> What does one need to do to manually configure it after install to work
for
> everyone?
usually MSDE is installed setting the relative services account to
LocalSystem, that provide (far) enought privileges (on the local machine)
for all logged users...
have a look at
http://msdn.microsoft.com/library/de...l/THCMCh18.asp
for more restrictions..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
By default the services use Local System option for log on. This worked fine
for all admin users but did not work for a non-admin user. When a non-admin
user logs in (local or domain user), the services won't start using Local
System. (side note: this is on a WinXP Pro machine). The non-admin user
cannot start or stop any service.
We did get it to work for the non-admin user by using the local
administrator account for log on (I goofed when trying it the first time by
using domain admin password instead of local admin password). This is not
the way we want to go, but it's the only way it does work right now.
I did find one thing via your link, in the Installation Recommendations:
"Create a least privileged local account with which to run the SQL Server
service. Use this account when you are prompted for service settings during
setup. Do not use the local system account or an administrator account. "
There is no prompt when installing MSDE. What exactly is a "least priviledge
local account"?
Any other suggestions are most welcome!
Thanks for your help.
leon.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2okhj5Fbml6lU1@.uni-berlin.de...[vbcol=seagreen]
> hi Leon,
> "LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
> news:Oe0QyXhhEHA.904@.TK2MSFTNGP09.phx.gbl...
the[vbcol=seagreen]
non-admin
> Local
> for
> usually MSDE is installed setting the relative services account to
> LocalSystem, that provide (far) enought privileges (on the local machine)
> for all logged users...
> have a look at
>
http://msdn.microsoft.com/library/de...l/THCMCh18.asp
> for more restrictions..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Leon,
"LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
news:eO0WPBthEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi Andrea,
> By default the services use Local System option for log on. This worked
fine
> for all admin users but did not work for a non-admin user. When a
non-admin
> user logs in (local or domain user), the services won't start using Local
> System. (side note: this is on a WinXP Pro machine). The non-admin user
> cannot start or stop any service.
actually they shoul'd run, as all this is intended to work this way... SQL
Server is run under another privileged account than the current logged
account, which only needs to connect to the specified server and query for
information..
perhaps you have to check your local policies...
> We did get it to work for the non-admin user by using the local
> administrator account for log on (I goofed when trying it the first time
by
> using domain admin password instead of local admin password). This is not
> the way we want to go, but it's the only way it does work right now.
I usually use a local account (not LocalSystem), with enought rights on
relevent share(s) if needed..
> I did find one thing via your link, in the Installation Recommendations:
> "Create a least privileged local account with which to run the SQL Server
> service. Use this account when you are prompted for service settings
during
> setup. Do not use the local system account or an administrator account. "
> There is no prompt when installing MSDE. What exactly is a "least
priviledge
> local account"?
no, there's not... that info is for a full blown SQL Server installation..
you have to set that property after MSDE installed, accessing the services
management applet... perhaps it can be done via WMI, but never tried it..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||more,
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> ha scritto nel messaggio
news:2omoccFcfn07U1@.uni-berlin.de...[vbcol=seagreen]
> hi Leon,
> "LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
> news:eO0WPBthEHA.2908@.TK2MSFTNGP10.phx.gbl...
Local[vbcol=seagreen]
they do not have to... set the service's "start at boostrap" property...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||The instructions on the SQLServer Installation Recommendations say to create
a new user, remove it from the users group and use it for the service login.
We created an "msde" user, removed it from Users group, set it as the Log On
As account (it is listed in the "Log on as a service" policy), gave full
access rights for the data files to Everyone, and it doesn't work.
So you have installed MSDE 2000 A and had its service (MSDE$InstanceName)
starting with a non-admin log in?
If so, you must have some magic touch because we're trying this on 2
separate machines with the same failure on each. We'll be trying it on a
fresh XP install shortly, but I don't really expect different results.
Even when logged into the XP as an administrator, setting the MSDE service
login account to "msde" causes the service to fail on a start attempt. It
gives the following error:
Could not start the MSDE$... service on Local Computer.
Error 5: Access is Denied
How do you access the "start at boostrap" property of a service?
thanks,
leon.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2omogoFcbbrgU1@.uni-berlin.de...[vbcol=seagreen]
> more,
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> ha scritto nel messaggio
> news:2omoccFcfn07U1@.uni-berlin.de...
> Local
user
> they do not have to... set the service's "start at boostrap" property...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Leon,
"LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
news:%233zBrHvhEHA.644@.tk2msftngp13.phx.gbl...
> The instructions on the SQLServer Installation Recommendations say to
create
> a new user, remove it from the users group and use it for the service
login.
> We created an "msde" user, removed it from Users group, set it as the Log
On
> As account (it is listed in the "Log on as a service" policy), gave full
> access rights for the data files to Everyone, and it doesn't work.
> So you have installed MSDE 2000 A and had its service (MSDE$InstanceName)
> starting with a non-admin log in?
> If so, you must have some magic touch because we're trying this on 2
> separate machines with the same failure on each. We'll be trying it on a
> fresh XP install shortly, but I don't really expect different results.
> Even when logged into the XP as an administrator, setting the MSDE service
> login account to "msde" causes the service to fail on a start attempt. It
> gives the following error:
> Could not start the MSDE$... service on Local Computer.
> Error 5: Access is Denied
I do always use a local admin account, and I never use the special
LocalSystem account, created just for this purpose and never use an actual
local or domain administrator account. The account must be in the local
Administrators group if you're installing SQL Server on Windows NT or
Windows 2000. You can create this account before you begin installing SQL
Server, or you can change the account under which SQL Server runs at a later
time.
Setting less privileges is intended in not using a Domain Admin account for
network protection.
> How do you access the "start at boostrap" property of a service?
in the service management, select Startup Mode = automatic
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea
Sorry, referring to the automatic service startup as "start at bootstrap"
property is a little different terminology than I am used to. I do
understand the automatic startup option.
We will just include some instructions for setting up the app for non-admin
users.
Thanks for your help.
leon.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2ong8qFcg0ccU1@.uni-berlin.de...[vbcol=seagreen]
> hi Leon,
> "LM" <leonm@.vtn-tech.com> ha scritto nel messaggio
> news:%233zBrHvhEHA.644@.tk2msftngp13.phx.gbl...
> create
> login.
Log[vbcol=seagreen]
> On
(MSDE$InstanceName)[vbcol=seagreen]
service[vbcol=seagreen]
It
> I do always use a local admin account, and I never use the special
> LocalSystem account, created just for this purpose and never use an actual
> local or domain administrator account. The account must be in the local
> Administrators group if you're installing SQL Server on Windows NT or
> Windows 2000. You can create this account before you begin installing SQL
> Server, or you can change the account under which SQL Server runs at a
later
> time.
> Setting less privileges is intended in not using a Domain Admin account
for
> network protection.
> in the service management, select Startup Mode = automatic
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (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 ReleaseA
Can i redistribute only osql.exe with my asp.net application
we are using licensed Install Shield for packaging..
we use this osql.exe for creating and setup database...
regards
sahridhayan
hi,
sahridhayan wrote:
> Can i redistribute only osql.exe with my asp.net application
> we are using licensed Install Shield for packaging..
> we use this osql.exe for creating and setup database...
I do not think you can separate oSql.exe from the full MSDE package from a
legal point of view..
but perhaps you've better ask Microsoft representatives...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I'm not sure about MSDE, but if you have a SQL Server license you can
distribute OSQL. Refer to REDIST.TXT for a listing of all the
redistributable components of SQL Server.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3h5uarFf6jcoU1@.individual.net...
> hi,
> sahridhayan wrote:
> I do not think you can separate oSql.exe from the full MSDE package from a
> legal point of view..
> but perhaps you've better ask Microsoft representatives...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi,
Desperado wrote:
> I'm not sure about MSDE, but if you have a SQL Server license you can
> distribute OSQL. Refer to REDIST.TXT for a listing of all the
> redistributable components of SQL Server.
>
again, I'm not sure you can "cannibalize" osql.exe that way... of course,
having a full SQL Server licence, you can install the Client Tools, that
include quiet all tools... but this way I'm little skeptic... but I'm not a
lawyer
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
we are using licensed Install Shield for packaging..
we use this osql.exe for creating and setup database...
regards
sahridhayan
hi,
sahridhayan wrote:
> Can i redistribute only osql.exe with my asp.net application
> we are using licensed Install Shield for packaging..
> we use this osql.exe for creating and setup database...
I do not think you can separate oSql.exe from the full MSDE package from a
legal point of view..
but perhaps you've better ask Microsoft representatives...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I'm not sure about MSDE, but if you have a SQL Server license you can
distribute OSQL. Refer to REDIST.TXT for a listing of all the
redistributable components of SQL Server.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3h5uarFf6jcoU1@.individual.net...
> hi,
> sahridhayan wrote:
> I do not think you can separate oSql.exe from the full MSDE package from a
> legal point of view..
> but perhaps you've better ask Microsoft representatives...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi,
Desperado wrote:
> I'm not sure about MSDE, but if you have a SQL Server license you can
> distribute OSQL. Refer to REDIST.TXT for a listing of all the
> redistributable components of SQL Server.
>
again, I'm not sure you can "cannibalize" osql.exe that way... of course,
having a full SQL Server licence, you can install the Client Tools, that
include quiet all tools... but this way I'm little skeptic... but I'm not a
lawyer
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Monday, March 19, 2012
MSDE Not Connected
Hi,
I installed MSDE 2000 SP3 to use the ASP.NET QuickStart samples on
my Windows 2000 machine. I ran
setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD<my password>
I then ran the QuickStart installer.
These steps were documented by MS.
But when I rebooted, the SQL Service Manager was 'Not Connected'
and the circle in front of the server icon was blank/white. Also the QuickStart samples that connect to MSDE won't and give errors like 'System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.' or '...Login failed for user '<my server name>\ASPNET'
When I run 'osql -E -S <my server name>\VSDOTNET' command I get '1>'. So there is a connection that's possible. Also the MSSQL$VSDOTNET is Started.
Any suggestions?Try running the SVRNETCN.exe tool to find out what protocols MSDE is using. I had a similar problem (not with .NET) and found that NO protocols were selected. Ergo, no connection possible.
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\SVRNETCN.exe
-- Steve
Originally posted by ericscat
Hi,
I installed MSDE 2000 SP3 to use the ASP.NET QuickStart samples on
my Windows 2000 machine. I ran
setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD<my password>
I then ran the QuickStart installer.
These steps were documented by MS.
But when I rebooted, the SQL Service Manager was 'Not Connected'
and the circle in front of the server icon was blank/white. Also the QuickStart samples that connect to MSDE won't and give errors like 'System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.' or '...Login failed for user '<my server name>\ASPNET'
When I run 'osql -E -S <my server name>\VSDOTNET' command I get '1>'. So there is a connection that's possible. Also the MSSQL$VSDOTNET is Started.
Any suggestions?|||Hi,
Thanks I ran it and restarted the MSSQL$VSDOTNET service, but I
don't see any change. Sorry I don't know much of this. Your right
there were no protocols selected so I enabled TCP/IP. What is the
SQLAgent$VSDOTNET service? It's setup as a Manual startup.
Any more tips? I would assume that when I installed MSDE and
setup the instance that I would see the small green right pointing
arrow in the Service Manager icon. The Manager still says Not Connected.
??|||Sorry,
I rebooted and got an automatic connection/Sql Server Service
started.
Thanks for your help.
I installed MSDE 2000 SP3 to use the ASP.NET QuickStart samples on
my Windows 2000 machine. I ran
setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD<my password>
I then ran the QuickStart installer.
These steps were documented by MS.
But when I rebooted, the SQL Service Manager was 'Not Connected'
and the circle in front of the server icon was blank/white. Also the QuickStart samples that connect to MSDE won't and give errors like 'System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.' or '...Login failed for user '<my server name>\ASPNET'
When I run 'osql -E -S <my server name>\VSDOTNET' command I get '1>'. So there is a connection that's possible. Also the MSSQL$VSDOTNET is Started.
Any suggestions?Try running the SVRNETCN.exe tool to find out what protocols MSDE is using. I had a similar problem (not with .NET) and found that NO protocols were selected. Ergo, no connection possible.
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\SVRNETCN.exe
-- Steve
Originally posted by ericscat
Hi,
I installed MSDE 2000 SP3 to use the ASP.NET QuickStart samples on
my Windows 2000 machine. I ran
setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD<my password>
I then ran the QuickStart installer.
These steps were documented by MS.
But when I rebooted, the SQL Service Manager was 'Not Connected'
and the circle in front of the server icon was blank/white. Also the QuickStart samples that connect to MSDE won't and give errors like 'System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.' or '...Login failed for user '<my server name>\ASPNET'
When I run 'osql -E -S <my server name>\VSDOTNET' command I get '1>'. So there is a connection that's possible. Also the MSSQL$VSDOTNET is Started.
Any suggestions?|||Hi,
Thanks I ran it and restarted the MSSQL$VSDOTNET service, but I
don't see any change. Sorry I don't know much of this. Your right
there were no protocols selected so I enabled TCP/IP. What is the
SQLAgent$VSDOTNET service? It's setup as a Manual startup.
Any more tips? I would assume that when I installed MSDE and
setup the instance that I would see the small green right pointing
arrow in the Service Manager icon. The Manager still says Not Connected.
??|||Sorry,
I rebooted and got an automatic connection/Sql Server Service
started.
Thanks for your help.
MSDE newbie
I Just installed MDSE2000A (ithink it already comes with SP3a), by doing
Setup.exe /qb+ INSTANCENAME=MOC DISABLENETWORKPROTOCOLS=1 SAPWD=moc
I downloaded the northwind database and tried to install it by doing
osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
Databases\northwind.mdf'"
the response was
[Shared Memory]Invalid connection.
[Shared Memory]ConnectionOpen (Invalid Instance()).
what have I done wrong?
You did not specify th instance you want to connect to, this can be done
with the switch -S
osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
Databases\northwind.mdf' -SServername\Instancename
Would be on the the local server ".\MOC"
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Joo Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
news:520F0379-78B1-449C-9864-896E04C5C910@.microsoft.com...
>I Just installed MDSE2000A (ithink it already comes with SP3a), by doing
> Setup.exe /qb+ INSTANCENAME=MOC DISABLENETWORKPROTOCOLS=1 SAPWD=moc
> I downloaded the northwind database and tried to install it by doing
> osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
> Databases\northwind.mdf'"
> the response was
> [Shared Memory]Invalid connection.
> [Shared Memory]ConnectionOpen (Invalid Instance()).
> what have I done wrong?
|||thanks, now I have unather problem, I transcribed the line below:
osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
Databases\northwind.mdf'" -S.\MOC
the answer was:
Msg 5105, Level 16, State 4, Server RAINBOWARRIOR\MOC, Line 1
Device activation error. The physical file name 'c:\SQL Server 2000 Sample
Databases\northwind.mdf' may be incorrect.
"Jens Sü?meyer" wrote:
> You did not specify th instance you want to connect to, this can be done
> with the switch -S
> osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
> Databases\northwind.mdf' -SServername\Instancename
> Would be on the the local server ".\MOC"
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
> "Jo?o Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:520F0379-78B1-449C-9864-896E04C5C910@.microsoft.com...
>
>
|||The problem is that there are spaces in the pathname, if you could get
around this you should use a simple path which doesnt contain any space
perhaps c:\sql. If you cant you have to doublequote the Quotes.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Joo Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
news:6A7F0B79-0B83-46C3-A1D6-C48EB86E0C8B@.microsoft.com...[vbcol=seagreen]
> thanks, now I have unather problem, I transcribed the line below:
> osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
> Databases\northwind.mdf'" -S.\MOC
> the answer was:
> Msg 5105, Level 16, State 4, Server RAINBOWARRIOR\MOC, Line 1
> Device activation error. The physical file name 'c:\SQL Server 2000 Sample
> Databases\northwind.mdf' may be incorrect.
> "Jens Smeyer" wrote:
|||thanks!
"Jens Sü?meyer" wrote:
> The problem is that there are spaces in the pathname, if you could get
> around this you should use a simple path which doesn′t contain any space
> perhaps c:\sql. If you can′t you have to doublequote the Quotes.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
> "Jo?o Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:6A7F0B79-0B83-46C3-A1D6-C48EB86E0C8B@.microsoft.com...
>
>
Setup.exe /qb+ INSTANCENAME=MOC DISABLENETWORKPROTOCOLS=1 SAPWD=moc
I downloaded the northwind database and tried to install it by doing
osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
Databases\northwind.mdf'"
the response was
[Shared Memory]Invalid connection.
[Shared Memory]ConnectionOpen (Invalid Instance()).
what have I done wrong?
You did not specify th instance you want to connect to, this can be done
with the switch -S
osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
Databases\northwind.mdf' -SServername\Instancename
Would be on the the local server ".\MOC"
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Joo Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
news:520F0379-78B1-449C-9864-896E04C5C910@.microsoft.com...
>I Just installed MDSE2000A (ithink it already comes with SP3a), by doing
> Setup.exe /qb+ INSTANCENAME=MOC DISABLENETWORKPROTOCOLS=1 SAPWD=moc
> I downloaded the northwind database and tried to install it by doing
> osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
> Databases\northwind.mdf'"
> the response was
> [Shared Memory]Invalid connection.
> [Shared Memory]ConnectionOpen (Invalid Instance()).
> what have I done wrong?
|||thanks, now I have unather problem, I transcribed the line below:
osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
Databases\northwind.mdf'" -S.\MOC
the answer was:
Msg 5105, Level 16, State 4, Server RAINBOWARRIOR\MOC, Line 1
Device activation error. The physical file name 'c:\SQL Server 2000 Sample
Databases\northwind.mdf' may be incorrect.
"Jens Sü?meyer" wrote:
> You did not specify th instance you want to connect to, this can be done
> with the switch -S
> osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
> Databases\northwind.mdf' -SServername\Instancename
> Would be on the the local server ".\MOC"
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
> "Jo?o Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:520F0379-78B1-449C-9864-896E04C5C910@.microsoft.com...
>
>
|||The problem is that there are spaces in the pathname, if you could get
around this you should use a simple path which doesnt contain any space
perhaps c:\sql. If you cant you have to doublequote the Quotes.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Joo Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
news:6A7F0B79-0B83-46C3-A1D6-C48EB86E0C8B@.microsoft.com...[vbcol=seagreen]
> thanks, now I have unather problem, I transcribed the line below:
> osql -E -Q "EXEC sp_attach_db N'Northwind', N'c:\SQL Server 2000 Sample
> Databases\northwind.mdf'" -S.\MOC
> the answer was:
> Msg 5105, Level 16, State 4, Server RAINBOWARRIOR\MOC, Line 1
> Device activation error. The physical file name 'c:\SQL Server 2000 Sample
> Databases\northwind.mdf' may be incorrect.
> "Jens Smeyer" wrote:
|||thanks!
"Jens Sü?meyer" wrote:
> The problem is that there are spaces in the pathname, if you could get
> around this you should use a simple path which doesn′t contain any space
> perhaps c:\sql. If you can′t you have to doublequote the Quotes.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
> "Jo?o Costa" <JooCosta@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:6A7F0B79-0B83-46C3-A1D6-C48EB86E0C8B@.microsoft.com...
>
>
MSDE needs to be installed for BackupEXec
I have a windows 2003 ent server that we cannot install MSDE on.
If we run this from terminal services and a command line, we get nothing:
Setup.exe INSTANCENAME=BKUPEXEC BLANKSAPWD=1 /L*v C:\MSDE.log
Not even a log file.
Does anyone have any suggestions?
Eric Sabo
NT Administrator
hi,
Sabo, Eric wrote:
> I have a windows 2003 ent server that we cannot install MSDE on.
> If we run this from terminal services and a command line, we get
> nothing: Setup.exe INSTANCENAME=BKUPEXEC BLANKSAPWD=1 /L*v C:\MSDE.log
> Not even a log file.
> Does anyone have any suggestions?
I do not think MSDE setup is a viable solution via terminal session.. have
you tried locally connected to the server?
(FWIW, is BLANKSAPWD=1 mandatory? ... and you'll get an instance without
networkprotocols support..)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea is correct. The setup program for MSDE (and SQL Server for that
matter) needs to be done on the physical console of the machine it is being
installed on.
Jim
"Sabo, Eric" <sabo_e@.cup.edu> wrote in message
news:e$fzrbiBFHA.3976@.tk2msftngp13.phx.gbl...
>I have a windows 2003 ent server that we cannot install MSDE on.
> If we run this from terminal services and a command line, we get nothing:
> Setup.exe INSTANCENAME=BKUPEXEC BLANKSAPWD=1 /L*v C:\MSDE.log
> Not even a log file.
> Does anyone have any suggestions?
> --
> Eric Sabo
> NT Administrator
>
|||I tried it this morning and got the same results from the console of the
machine.
Is there a way to complete remove MSDE?
It will not install.
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:OrjflHvBFHA.3096@.TK2MSFTNGP14.phx.gbl...
> Andrea is correct. The setup program for MSDE (and SQL Server for that
> matter) needs to be done on the physical console of the machine it is
> being installed on.
> Jim
> "Sabo, Eric" <sabo_e@.cup.edu> wrote in message
> news:e$fzrbiBFHA.3976@.tk2msftngp13.phx.gbl...
>
|||hi Eric,
Sabo, Eric wrote:
> I tried it this morning and got the same results from the console of
> the machine.
> Is there a way to complete remove MSDE?
> It will not install.
please have a look at
http://support.microsoft.com/default...;EN-US;Q290991 ...
this will not clear the Windows Installer related entries in the Windows
registry, that requires MSIZap.exe from the Platform SDK as reported in
http://support.microsoft.com/default...b;en-us;320873
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
If we run this from terminal services and a command line, we get nothing:
Setup.exe INSTANCENAME=BKUPEXEC BLANKSAPWD=1 /L*v C:\MSDE.log
Not even a log file.
Does anyone have any suggestions?
Eric Sabo
NT Administrator
hi,
Sabo, Eric wrote:
> I have a windows 2003 ent server that we cannot install MSDE on.
> If we run this from terminal services and a command line, we get
> nothing: Setup.exe INSTANCENAME=BKUPEXEC BLANKSAPWD=1 /L*v C:\MSDE.log
> Not even a log file.
> Does anyone have any suggestions?
I do not think MSDE setup is a viable solution via terminal session.. have
you tried locally connected to the server?
(FWIW, is BLANKSAPWD=1 mandatory? ... and you'll get an instance without
networkprotocols support..)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea is correct. The setup program for MSDE (and SQL Server for that
matter) needs to be done on the physical console of the machine it is being
installed on.
Jim
"Sabo, Eric" <sabo_e@.cup.edu> wrote in message
news:e$fzrbiBFHA.3976@.tk2msftngp13.phx.gbl...
>I have a windows 2003 ent server that we cannot install MSDE on.
> If we run this from terminal services and a command line, we get nothing:
> Setup.exe INSTANCENAME=BKUPEXEC BLANKSAPWD=1 /L*v C:\MSDE.log
> Not even a log file.
> Does anyone have any suggestions?
> --
> Eric Sabo
> NT Administrator
>
|||I tried it this morning and got the same results from the console of the
machine.
Is there a way to complete remove MSDE?
It will not install.
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:OrjflHvBFHA.3096@.TK2MSFTNGP14.phx.gbl...
> Andrea is correct. The setup program for MSDE (and SQL Server for that
> matter) needs to be done on the physical console of the machine it is
> being installed on.
> Jim
> "Sabo, Eric" <sabo_e@.cup.edu> wrote in message
> news:e$fzrbiBFHA.3976@.tk2msftngp13.phx.gbl...
>
|||hi Eric,
Sabo, Eric wrote:
> I tried it this morning and got the same results from the console of
> the machine.
> Is there a way to complete remove MSDE?
> It will not install.
please have a look at
http://support.microsoft.com/default...;EN-US;Q290991 ...
this will not clear the Windows Installer related entries in the Windows
registry, that requires MSIZap.exe from the Platform SDK as reported in
http://support.microsoft.com/default...b;en-us;320873
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Friday, March 9, 2012
MSDE installer problem
Hi
I'm working in visual C++ and through it I start MSDE setup.exe. I have to
wait in my VC++ code before the MSDE installer is finished totally. The
problem i'm having is that as soon as I initiate the process of MSDE
setup.exe, i get its finished status in my VC waiting code, though the
installer is still running. I've tried running the MSDE setup.exe from the
command line and i see that the status also come back to prompt just a
second after the setup.exe is run. I was wondering how can i keep the
control from coming back to the setup.exe instantiating application unless
the whole setup.exe is complete. Hope i've made my point clear.
Regards
Usman Jamil
Hi Usman,
Try this code: here WaitForSingleObject( ) waits till your process gets completed. I used the same for installing MSDE through my setup launcher.
Cheers
Piyush
int ExecCmd(char * pszCmd )
{
BOOL bReturnVal = false ;
STARTUPINFO si ;
DWORD dwExitCode ;
SECURITY_ATTRIBUTES saProcess, saThread ;
PROCESS_INFORMATION process_info ;
ZeroMemory(&si, sizeof(si)) ;
si.cb = sizeof(si) ;
saProcess.nLength = sizeof(saProcess) ;
saProcess.lpSecurityDescriptor = NULL ;
saProcess.bInheritHandle = TRUE ;
saThread.nLength = sizeof(saThread) ;
saThread.lpSecurityDescriptor = NULL ;
saThread.bInheritHandle = FALSE ;
bReturnVal = CreateProcess(NULL, (LPTSTR)pszCmd, &saProcess, &saThread, FALSE,
DETACHED_PROCESS,
NULL,
NULL,
&si,
&process_info) ;
if (bReturnVal)
{
CloseHandle( process_info.hThread ) ;
WaitForSingleObject( process_info.hProcess, INFINITE ) ;
GetExitCodeProcess( process_info.hProcess, &dwExitCode ) ;
CloseHandle( process_info.hProcess ) ;
}
return dwExitCode;
}
"Usman Jamil" <usman@.advcomm.net> wrote in message news:O11ArM2WEHA.2716@.tk2msftngp13.phx.gbl...
> Hi
> I'm working in visual C++ and through it I start MSDE setup.exe. I have to
> wait in my VC++ code before the MSDE installer is finished totally. The
> problem i'm having is that as soon as I initiate the process of MSDE
> setup.exe, i get its finished status in my VC waiting code, though the
> installer is still running. I've tried running the MSDE setup.exe from the
> command line and i see that the status also come back to prompt just a
> second after the setup.exe is run. I was wondering how can i keep the
> control from coming back to the setup.exe instantiating application unless
> the whole setup.exe is complete. Hope i've made my point clear.
> Regards
> Usman Jamil
>
|||Hi viki
I dont know how it worked in your case but its not supposed to work and i've
checked it too. It wont work coz the Waitforsingleobject would also return
as soon as the process created is finished. and when we run the process
setup.exe, this setup.exe script asks the windows installer service to run
the actull installer and it exits itself thus breaking the
waitforsingleobject lock too. So it would not work for MSDE installer from
C++ code. Anyway thanx for your help.
Still waiting for a solution..
Regards
Usman Jamil
"viki" <piyush__jain@.hotmail.com> wrote in message
news:eZ5ZQ3MXEHA.1144@.TK2MSFTNGP10.phx.gbl...
Hi Usman,
Try this code: here WaitForSingleObject( ) waits till your process gets
completed. I used the same for installing MSDE through my setup launcher.
Cheers
Piyush
int ExecCmd(char * pszCmd )
{
BOOL bReturnVal = false ;
STARTUPINFO si ;
DWORD dwExitCode ;
SECURITY_ATTRIBUTES saProcess, saThread ;
PROCESS_INFORMATION process_info ;
ZeroMemory(&si, sizeof(si)) ;
si.cb = sizeof(si) ;
saProcess.nLength = sizeof(saProcess) ;
saProcess.lpSecurityDescriptor = NULL ;
saProcess.bInheritHandle = TRUE ;
saThread.nLength = sizeof(saThread) ;
saThread.lpSecurityDescriptor = NULL ;
saThread.bInheritHandle = FALSE ;
bReturnVal = CreateProcess(NULL, (LPTSTR)pszCmd, &saProcess, &saThread,
FALSE,
DETACHED_PROCESS,
NULL,
NULL,
&si,
&process_info) ;
if (bReturnVal)
{
CloseHandle( process_info.hThread ) ;
WaitForSingleObject( process_info.hProcess, INFINITE ) ;
GetExitCodeProcess( process_info.hProcess, &dwExitCode ) ;
CloseHandle( process_info.hProcess ) ;
}
return dwExitCode;
}
"Usman Jamil" <usman@.advcomm.net> wrote in message
news:O11ArM2WEHA.2716@.tk2msftngp13.phx.gbl...
> Hi
> I'm working in visual C++ and through it I start MSDE setup.exe. I have to
> wait in my VC++ code before the MSDE installer is finished totally. The
> problem i'm having is that as soon as I initiate the process of MSDE
> setup.exe, i get its finished status in my VC waiting code, though the
> installer is still running. I've tried running the MSDE setup.exe from the
> command line and i see that the status also come back to prompt just a
> second after the setup.exe is run. I was wondering how can i keep the
> control from coming back to the setup.exe instantiating application unless
> the whole setup.exe is complete. Hope i've made my point clear.
> Regards
> Usman Jamil
>
|||Hi viki
I dont know how it worked in your case but its not supposed to work and i've
checked it too. It wont work coz the Waitforsingleobject would also return
as soon as the process created is finished. and when we run the process
setup.exe, this setup.exe script asks the windows installer service to run
the actull installer and it exits itself thus breaking the
waitforsingleobject lock too. So it would not work for MSDE installer from
C++ code. Anyway thanx for your help.
Still waiting for a solution..
Regards
Usman Jamil
"viki" <piyush__jain@.hotmail.com> wrote in message
news:eZ5ZQ3MXEHA.1144@.TK2MSFTNGP10.phx.gbl...
Hi Usman,
Try this code: here WaitForSingleObject( ) waits till your process gets
completed. I used the same for installing MSDE through my setup launcher.
Cheers
Piyush
int ExecCmd(char * pszCmd )
{
BOOL bReturnVal = false ;
STARTUPINFO si ;
DWORD dwExitCode ;
SECURITY_ATTRIBUTES saProcess, saThread ;
PROCESS_INFORMATION process_info ;
ZeroMemory(&si, sizeof(si)) ;
si.cb = sizeof(si) ;
saProcess.nLength = sizeof(saProcess) ;
saProcess.lpSecurityDescriptor = NULL ;
saProcess.bInheritHandle = TRUE ;
saThread.nLength = sizeof(saThread) ;
saThread.lpSecurityDescriptor = NULL ;
saThread.bInheritHandle = FALSE ;
bReturnVal = CreateProcess(NULL, (LPTSTR)pszCmd, &saProcess, &saThread,
FALSE,
DETACHED_PROCESS,
NULL,
NULL,
&si,
&process_info) ;
if (bReturnVal)
{
CloseHandle( process_info.hThread ) ;
WaitForSingleObject( process_info.hProcess, INFINITE ) ;
GetExitCodeProcess( process_info.hProcess, &dwExitCode ) ;
CloseHandle( process_info.hProcess ) ;
}
return dwExitCode;
}
"Usman Jamil" <usman@.advcomm.net> wrote in message
news:O11ArM2WEHA.2716@.tk2msftngp13.phx.gbl...
> Hi
> I'm working in visual C++ and through it I start MSDE setup.exe. I have to
> wait in my VC++ code before the MSDE installer is finished totally. The
> problem i'm having is that as soon as I initiate the process of MSDE
> setup.exe, i get its finished status in my VC waiting code, though the
> installer is still running. I've tried running the MSDE setup.exe from the
> command line and i see that the status also come back to prompt just a
> second after the setup.exe is run. I was wondering how can i keep the
> control from coming back to the setup.exe instantiating application unless
> the whole setup.exe is complete. Hope i've made my point clear.
> Regards
> Usman Jamil
>
I'm working in visual C++ and through it I start MSDE setup.exe. I have to
wait in my VC++ code before the MSDE installer is finished totally. The
problem i'm having is that as soon as I initiate the process of MSDE
setup.exe, i get its finished status in my VC waiting code, though the
installer is still running. I've tried running the MSDE setup.exe from the
command line and i see that the status also come back to prompt just a
second after the setup.exe is run. I was wondering how can i keep the
control from coming back to the setup.exe instantiating application unless
the whole setup.exe is complete. Hope i've made my point clear.
Regards
Usman Jamil
Hi Usman,
Try this code: here WaitForSingleObject( ) waits till your process gets completed. I used the same for installing MSDE through my setup launcher.
Cheers
Piyush
int ExecCmd(char * pszCmd )
{
BOOL bReturnVal = false ;
STARTUPINFO si ;
DWORD dwExitCode ;
SECURITY_ATTRIBUTES saProcess, saThread ;
PROCESS_INFORMATION process_info ;
ZeroMemory(&si, sizeof(si)) ;
si.cb = sizeof(si) ;
saProcess.nLength = sizeof(saProcess) ;
saProcess.lpSecurityDescriptor = NULL ;
saProcess.bInheritHandle = TRUE ;
saThread.nLength = sizeof(saThread) ;
saThread.lpSecurityDescriptor = NULL ;
saThread.bInheritHandle = FALSE ;
bReturnVal = CreateProcess(NULL, (LPTSTR)pszCmd, &saProcess, &saThread, FALSE,
DETACHED_PROCESS,
NULL,
NULL,
&si,
&process_info) ;
if (bReturnVal)
{
CloseHandle( process_info.hThread ) ;
WaitForSingleObject( process_info.hProcess, INFINITE ) ;
GetExitCodeProcess( process_info.hProcess, &dwExitCode ) ;
CloseHandle( process_info.hProcess ) ;
}
return dwExitCode;
}
"Usman Jamil" <usman@.advcomm.net> wrote in message news:O11ArM2WEHA.2716@.tk2msftngp13.phx.gbl...
> Hi
> I'm working in visual C++ and through it I start MSDE setup.exe. I have to
> wait in my VC++ code before the MSDE installer is finished totally. The
> problem i'm having is that as soon as I initiate the process of MSDE
> setup.exe, i get its finished status in my VC waiting code, though the
> installer is still running. I've tried running the MSDE setup.exe from the
> command line and i see that the status also come back to prompt just a
> second after the setup.exe is run. I was wondering how can i keep the
> control from coming back to the setup.exe instantiating application unless
> the whole setup.exe is complete. Hope i've made my point clear.
> Regards
> Usman Jamil
>
|||Hi viki
I dont know how it worked in your case but its not supposed to work and i've
checked it too. It wont work coz the Waitforsingleobject would also return
as soon as the process created is finished. and when we run the process
setup.exe, this setup.exe script asks the windows installer service to run
the actull installer and it exits itself thus breaking the
waitforsingleobject lock too. So it would not work for MSDE installer from
C++ code. Anyway thanx for your help.
Still waiting for a solution..
Regards
Usman Jamil
"viki" <piyush__jain@.hotmail.com> wrote in message
news:eZ5ZQ3MXEHA.1144@.TK2MSFTNGP10.phx.gbl...
Hi Usman,
Try this code: here WaitForSingleObject( ) waits till your process gets
completed. I used the same for installing MSDE through my setup launcher.
Cheers
Piyush
int ExecCmd(char * pszCmd )
{
BOOL bReturnVal = false ;
STARTUPINFO si ;
DWORD dwExitCode ;
SECURITY_ATTRIBUTES saProcess, saThread ;
PROCESS_INFORMATION process_info ;
ZeroMemory(&si, sizeof(si)) ;
si.cb = sizeof(si) ;
saProcess.nLength = sizeof(saProcess) ;
saProcess.lpSecurityDescriptor = NULL ;
saProcess.bInheritHandle = TRUE ;
saThread.nLength = sizeof(saThread) ;
saThread.lpSecurityDescriptor = NULL ;
saThread.bInheritHandle = FALSE ;
bReturnVal = CreateProcess(NULL, (LPTSTR)pszCmd, &saProcess, &saThread,
FALSE,
DETACHED_PROCESS,
NULL,
NULL,
&si,
&process_info) ;
if (bReturnVal)
{
CloseHandle( process_info.hThread ) ;
WaitForSingleObject( process_info.hProcess, INFINITE ) ;
GetExitCodeProcess( process_info.hProcess, &dwExitCode ) ;
CloseHandle( process_info.hProcess ) ;
}
return dwExitCode;
}
"Usman Jamil" <usman@.advcomm.net> wrote in message
news:O11ArM2WEHA.2716@.tk2msftngp13.phx.gbl...
> Hi
> I'm working in visual C++ and through it I start MSDE setup.exe. I have to
> wait in my VC++ code before the MSDE installer is finished totally. The
> problem i'm having is that as soon as I initiate the process of MSDE
> setup.exe, i get its finished status in my VC waiting code, though the
> installer is still running. I've tried running the MSDE setup.exe from the
> command line and i see that the status also come back to prompt just a
> second after the setup.exe is run. I was wondering how can i keep the
> control from coming back to the setup.exe instantiating application unless
> the whole setup.exe is complete. Hope i've made my point clear.
> Regards
> Usman Jamil
>
|||Hi viki
I dont know how it worked in your case but its not supposed to work and i've
checked it too. It wont work coz the Waitforsingleobject would also return
as soon as the process created is finished. and when we run the process
setup.exe, this setup.exe script asks the windows installer service to run
the actull installer and it exits itself thus breaking the
waitforsingleobject lock too. So it would not work for MSDE installer from
C++ code. Anyway thanx for your help.
Still waiting for a solution..
Regards
Usman Jamil
"viki" <piyush__jain@.hotmail.com> wrote in message
news:eZ5ZQ3MXEHA.1144@.TK2MSFTNGP10.phx.gbl...
Hi Usman,
Try this code: here WaitForSingleObject( ) waits till your process gets
completed. I used the same for installing MSDE through my setup launcher.
Cheers
Piyush
int ExecCmd(char * pszCmd )
{
BOOL bReturnVal = false ;
STARTUPINFO si ;
DWORD dwExitCode ;
SECURITY_ATTRIBUTES saProcess, saThread ;
PROCESS_INFORMATION process_info ;
ZeroMemory(&si, sizeof(si)) ;
si.cb = sizeof(si) ;
saProcess.nLength = sizeof(saProcess) ;
saProcess.lpSecurityDescriptor = NULL ;
saProcess.bInheritHandle = TRUE ;
saThread.nLength = sizeof(saThread) ;
saThread.lpSecurityDescriptor = NULL ;
saThread.bInheritHandle = FALSE ;
bReturnVal = CreateProcess(NULL, (LPTSTR)pszCmd, &saProcess, &saThread,
FALSE,
DETACHED_PROCESS,
NULL,
NULL,
&si,
&process_info) ;
if (bReturnVal)
{
CloseHandle( process_info.hThread ) ;
WaitForSingleObject( process_info.hProcess, INFINITE ) ;
GetExitCodeProcess( process_info.hProcess, &dwExitCode ) ;
CloseHandle( process_info.hProcess ) ;
}
return dwExitCode;
}
"Usman Jamil" <usman@.advcomm.net> wrote in message
news:O11ArM2WEHA.2716@.tk2msftngp13.phx.gbl...
> Hi
> I'm working in visual C++ and through it I start MSDE setup.exe. I have to
> wait in my VC++ code before the MSDE installer is finished totally. The
> problem i'm having is that as soon as I initiate the process of MSDE
> setup.exe, i get its finished status in my VC waiting code, though the
> installer is still running. I've tried running the MSDE setup.exe from the
> command line and i see that the status also come back to prompt just a
> second after the setup.exe is run. I was wondering how can i keep the
> control from coming back to the setup.exe instantiating application unless
> the whole setup.exe is complete. Hope i've made my point clear.
> Regards
> Usman Jamil
>
MSDE Installation problem
Hi All
I am having a little trouble setting up MSDE.
I downloaded the most recent version of MSDE (sql2ksp3.exe) from the Microsoft site to my desktop.
I double clcked on the files to extract them, it created a sql2ksp3 dir on c drive.
I went to command prompt and entered the following in the c:/sql2ksp3/msde directory:
setup.exe DISABLENETWORKPROTOCOLS=1 SAPWD=**REMOVED** then enter.
The setup wizard started then finished after about 30 seconds.
I can't find MSDE anywhere as program just a folder with the original setup programs.
I know this is a total gummy question, can anyone point me in the right direction.
I didn't have MSDE or SQL Server prevoiusly on the system.
Thanks in advance
PDid you see a new icon in your systray for MSSQLServer?
I am having a little trouble setting up MSDE.
I downloaded the most recent version of MSDE (sql2ksp3.exe) from the Microsoft site to my desktop.
I double clcked on the files to extract them, it created a sql2ksp3 dir on c drive.
I went to command prompt and entered the following in the c:/sql2ksp3/msde directory:
setup.exe DISABLENETWORKPROTOCOLS=1 SAPWD=**REMOVED** then enter.
The setup wizard started then finished after about 30 seconds.
I can't find MSDE anywhere as program just a folder with the original setup programs.
I know this is a total gummy question, can anyone point me in the right direction.
I didn't have MSDE or SQL Server prevoiusly on the system.
Thanks in advance
PDid you see a new icon in your systray for MSSQLServer?
If you shell out to DOS and type in this, are any results returned?
osql -L
Terri|||Server:
---NONE----
That's what i got! Can you help me how to fix my problem|||Do you have the SQL Server icon in your systray? It looks like a gray CPU and will likely have a red square on it (and when you hover over it it will say Stopped). You need to right-click on the icon and and choose MSSQLServer - Start. Once you've done this, try the osql -L command again.
Terri|||yes i have SQL Server icon on my systray. I tried to open it but the server is empty. so i put my server name but still cannot connect. I right click also and hit start but still the same. when i hover over it it says"Not Connected". It puzzled me!!|||Hi
Thanks for the reply
No there is no SqlServer Icon.
When I do the DOS command (osql -L) it says that is not recognised as an internal or external command, operable program or batch file.
Where do I go from here
P|||Installation problems are the most insidious and the most difficult to troubleshoot.
Can you search for sqlsp.log on your machine and see if there's anything useful in it?
Terri|||Hi Terri
I just did the search for sqlsp.log and nothing came up.
I have saved the the sql2ksp3.exe to a cd so I can try it all again.
If I do, which directory should I be installing it in.
I am using XP Pro and I VS.net 2003.
Also what services should Istop to make sure nothing stuffs it up there.
I stopped my firewall and anti-virus last time, should I stop IIS and anything else?
Thanks for your help
Pete|||Also, did the event viewer show anything helpful?
Unfortunately I am not an MSDE installation expert. The best advice I can give is to search these forums for MSDE Install and see what has been advised in the past.
Are you following the instructions atMSDE 2000 for Developers Using Visual Studio .NET or something similar (such asCustomizing Desktop Engine Setup.exe)?
And also you should use verbose logging to a text file so you can review any installation problems, by using an additional command line parameter: /L*v C:\MSDEsetup.log
I would use the default directories for installation.
Terri|||Hi Terri
I tried installing the VS.net version of the MSDE without luck.
I did get a log though, but I wouldn't know where to start to look for the problem.
Is it possible to email you the log file to check out the problem.
There was no errors in the event viewer although the Dreamweaver MX Application
server did startup each time I tried to install the MSDE.
Thx
Pete|||It would better benefit you to either post the log itself here or a link to it. As much as I want to help I am not confident that I will be able to pinpoint your problem and you would benefit from other eyes looking at it as well.
Presumably the problematic area will be at the end of the log file.
Terri|||me again
the command i used was
setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD=RRR#$GS1 /L*V c:\msdesetup2.log
The log file is like 3,900KB so it is a little large here is the last bit
Needless to say it would take a while to find where it went wrong
Property(S): DataInstanceInstall.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = C:\Program Files\Microsoft SQL Server\MSSQL$VSDOTNET\Install\
Property(S): DataInstance.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = C:\Program Files\Microsoft SQL Server\MSSQL$VSDOTNET\
Property(S): Data.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = C:\
Property(S): DataInstanceData.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = C:\Program Files\Microsoft SQL Server\MSSQL$VSDOTNET\Data\
Property(S): DataInstanceJobs.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = C:\Program Files\Microsoft SQL Server\MSSQL$VSDOTNET\JOBS\
Property(S): DataInstanceLog.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = C:\Program Files\Microsoft SQL Server\MSSQL$VSDOTNET\LOG\
Property(S): InstanceName.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = VSDOTNET
Property(S): PackageCode = {D29DCF7A-8199-4373-BA0D-2F3635EC940C}
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): INSTANCENAME = VSDOTNET
Property(S): DISABLENETWORKPROTOCOLS = 1
Property(S): SA...
Property(S): CURRENTDIRECTORY = C:\sql2ksp3\MSDE
Property(S): CLIENTUILEVEL = 2
Property(S): CLIENTPROCESSID = 1208
Property(S): VersionDatabase = 110
Property(S): VersionMsi = 2.00
Property(S): WindowsBuild = 2600
Property(S): ServicePackLevel = 1
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 1
Property(S): WindowsFolder = C:\WINDOWS\
Property(S): WindowsVolume = C:\
Property(S): System16Folder = C:\WINDOWS\System\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\DOCUME~1\pete\LOCALS~1\Temp\
Property(S): ProgramFilesFolder = C:\Program Files\
Property(S): CommonFilesFolder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Documents and Settings\pete\Application Data\
Property(S): FavoritesFolder = C:\Documents and Settings\pete\Favorites\
Property(S): NetHoodFolder = C:\Documents and Settings\pete\NetHood\
Property(S): PersonalFolder = C:\Documents and Settings\pete\My Documents\
Property(S): PrintHoodFolder = C:\Documents and Settings\pete\PrintHood\
Property(S): RecentFolder = C:\Documents and Settings\pete\Recent\
Property(S): SendToFolder = C:\Documents and Settings\pete\SendTo\
Property(S): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(S): CommonAppDataFolder = C:\Documents and Settings\All Users\Application Data\
Property(S): LocalAppDataFolder = C:\Documents and Settings\pete\Local Settings\Application Data\
Property(S): MyPicturesFolder = C:\Documents and Settings\pete\My Documents\My Pictures\
Property(S): AdminToolsFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\Documents and Settings\All Users\Start Menu\Programs\
Property(S): StartMenuFolder = C:\Documents and Settings\All Users\Start Menu\
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(S): FontsFolder = C:\WINDOWS\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): Intel = 6
Property(S): PhysicalMemory = 511
Property(S): VirtualMemory = 1010
Property(S): AdminUser = 1
Property(S): LogonUser = xxxxxx
Property(S): UserSID = S-1-5-21-3088462085-1224436771-4233946611-1005
Property(S): UserLanguageID = 3081
Property(S): ComputerName = xxxxx
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 1280
Property(S): ScreenY = 800
Property(S): CaptionHeight = 26
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): MsiNetAssemblySupport = 1.1.4322.573
Property(S): MsiWin32AssemblySupport = 5.1.2600.1515
Property(S): RedirectedDllSupport = 2
Property(S): Time = 13:10:21
Property(S): Date = 7/08/2004
Property(S): Privileged = 1
Property(S): USERNAME =
Property(S): COMPANYNAME =
Property(S): DATABASE = C:\WINDOWS\Installer\678b2d.msi
Property(S): OriginalDatabase = C:\sql2ksp3\MSDE\Setup\SqlRun01.msi
Property(S): UILevel = 3
Property(S): ACTION = INSTALL
Property(S): AgentServiceName = SQLAgent$VSDOTNET
Property(S): InstanceRegKey = Microsoft SQL Server\VSDOTNET
Property(S): InstanceSubDir = MSSQL$VSDOTNET
Property(S): SqlPerfMonRegKey = SQLCTR$VSDOTNET
Property(S): SQLServiceName = MSSQL$VSDOTNET
Property(S): SqlStates = 0
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): SqlFeature = SqlRun
Property(S): SOURCEDIR = C:\sql2ksp3\MSDE\Setup\
Property(S): SourcedirProduct = {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(S): ProductToBeRegistered = 1
=== Logging stopped: 7/08/2004 13:10:21 ===
MSI (s) (20:60): Note: 1: 1708
MSI (s) (20:60): Product: Microsoft SQL Server Desktop Engine -- Installation operation failed.
MSI (s) (20:60): Cleaning up uninstalled install packages, if any exist
MSI (s) (20:60): MainEngineThread is returning 1603
MSI (c) (B8:F8): Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (B8:F8): MainEngineThread is returning 1603
=== Verbose logging stopped: 7/08/2004 13:10:21 ===
once again thx for your help
I am checking the net for solutions, maybe I shouldn't give it an instance name
Pete|||The 2 things I've been able to locate concerning this are: 1) make sure you have the latest MDAC installed and 2) make sure you have the Server service started (You Cannot Install MSDE 2000 if the Server Service Is Not Running).
And I have also seen the recommendation to look for the string "return value 3" in the log file to further identify where the point of failure is.
Terri|||Me again
I found 2 instances of return value 3:
MSI (s) (20:60): Executing op: ActionStart(Name=InstallAgentSecurity.2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
Action 13:09:53: InstallAgentSecurity.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
MSI (s) (20:60): Executing op: CustomActionSchedule(Action=InstallAgentSecurity.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1025,Source=BinaryData,Target=InstallSQLAgentSecurity,)
MSI (s) (20:60): Creating MSIHANDLE (260) of type 790536 for thread 2144
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (PODJIE-LAP,LocalSystem,87).
Action ended 13:09:54: InstallFinalize. Return value 3. <<=============
MSI (s) (20:60): User policy value 'DisableRollback' is 0
MSI (s) (20:60): Machine policy value 'DisableRollback' is 0
MSI (s) (20:60): Executing op: Header(Signature=1397708873,Version=200,Timestamp=822569229,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
--------------------
and here
MSI (s) (20:60): Creating MSIHANDLE (282) of type 790536 for thread 2144
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\setupex.dll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqdedev.dll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlsut.dll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlunirl.dll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlresld.dll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.rll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlstp.dll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlstp.rll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
Rollback: RollbackDeferProperties.2D02443E_7002_4C0B_ABC9_EAB2C064397B
MSI (s) (20:60): Executing op: ActionStart(Name=RollbackDeferProperties.2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (20:60): Executing op: CustomActionRollback(Action=RollbackDeferProperties.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1281,Source=BinaryData,Target=DeferProperties,)
MSI (s) (20:60): Creating MSIHANDLE (293) of type 790536 for thread 2144
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Start custom action DeferProperties
Defer Properties returns: 0
MSI (s) (20:60): Executing op: End(Checksum=0,ProgressTotal=0)
MSI (s) (20:60): Error in rollback skipped. Return: 5
MSI (s) (20:60): FEATURECACHE: Entering Invalidate
MSI (s) (20:60): Calling SRSetRestorePoint API. dwRestorePtType: 13, dwEventType: 103, llSequenceNumber: 171, szDescription: "".
MSI (s) (20:60): The call to SRSetRestorePoint API succeeded. Returned status: 0.
MSI (s) (20:60): Unlocking Server
MSI (s) (20:60): Note: 1: 33
Action ended 13:10:19: INSTALL. Return value 3.<<<===================
------------
I am checking up on MDAC side of things and i'll get back to you
Pete|||The key is definitely the "InstallSQLAgentSecurity failed". Check the article on the Server service that I provided in a previous post. And if that doesn't help matters, check out this link:InstallSQLAgentSecurity failed.
You're getting closer, I can feel it :-)
Terri
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
>
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
>
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
>
Wednesday, March 7, 2012
MSDE installation
I installed MSDE 2000 with parameters SAPWD='ahoj' SECURITYMODE=SQL
Installation was OK, I enabled all networks protocols in SVRNETCN.exe and
restared server.
osql.exe -L found 1 server: (local);
But if I try to start osql.exe -U sa and write a password, osql says 'Login
failed for user sa'.
Where is the mistake?
The password is OK.
Best regards,
Jakub Cermak
ICQ 159971304
http://cermi.wz.cz
Hope you didnt mess up with the syntax, in your case it would be:
OSQL -Usa -Pahoj
Did you tried it with those space between -P and -U ? Most be used with no
spaces between paramters...
HTH, Jens Suessmeyer
http://www.sqlserver2005.de
"Jakub Cermak (news)" <ja.cermi@.centrum.cz> schrieb im Newsbeitrag
news:uaZulUpQFHA.3384@.TK2MSFTNGP10.phx.gbl...
>I installed MSDE 2000 with parameters SAPWD='ahoj' SECURITYMODE=SQL
> Installation was OK, I enabled all networks protocols in SVRNETCN.exe and
> restared server.
> osql.exe -L found 1 server: (local);
> But if I try to start osql.exe -U sa and write a password, osql says
> 'Login
> failed for user sa'.
> Where is the mistake?
> The password is OK.
> --
> Best regards,
> Jakub Cermak
> ICQ 159971304
> http://cermi.wz.cz
|||The problem was in another thing.
The space isn't important.
Best regards,
Jakub Cermak
ICQ 159971304
http://cermi.wz.cz
Jens Smeyer napsal(a):
> Hope you didnt mess up with the syntax, in your case it would be:
> OSQL -Usa -Pahoj
> Did you tried it with those space between -P and -U ? Most be used with no
> spaces between paramters...
> HTH, Jens Suessmeyer
> --
> http://www.sqlserver2005.de
> --
> "Jakub Cermak (news)" <ja.cermi@.centrum.cz> schrieb im Newsbeitrag
> news:uaZulUpQFHA.3384@.TK2MSFTNGP10.phx.gbl...
>
>
Installation was OK, I enabled all networks protocols in SVRNETCN.exe and
restared server.
osql.exe -L found 1 server: (local);
But if I try to start osql.exe -U sa and write a password, osql says 'Login
failed for user sa'.
Where is the mistake?
The password is OK.
Best regards,
Jakub Cermak
ICQ 159971304
http://cermi.wz.cz
Hope you didnt mess up with the syntax, in your case it would be:
OSQL -Usa -Pahoj
Did you tried it with those space between -P and -U ? Most be used with no
spaces between paramters...
HTH, Jens Suessmeyer
http://www.sqlserver2005.de
"Jakub Cermak (news)" <ja.cermi@.centrum.cz> schrieb im Newsbeitrag
news:uaZulUpQFHA.3384@.TK2MSFTNGP10.phx.gbl...
>I installed MSDE 2000 with parameters SAPWD='ahoj' SECURITYMODE=SQL
> Installation was OK, I enabled all networks protocols in SVRNETCN.exe and
> restared server.
> osql.exe -L found 1 server: (local);
> But if I try to start osql.exe -U sa and write a password, osql says
> 'Login
> failed for user sa'.
> Where is the mistake?
> The password is OK.
> --
> Best regards,
> Jakub Cermak
> ICQ 159971304
> http://cermi.wz.cz
|||The problem was in another thing.
The space isn't important.
Best regards,
Jakub Cermak
ICQ 159971304
http://cermi.wz.cz
Jens Smeyer napsal(a):
> Hope you didnt mess up with the syntax, in your case it would be:
> OSQL -Usa -Pahoj
> Did you tried it with those space between -P and -U ? Most be used with no
> spaces between paramters...
> HTH, Jens Suessmeyer
> --
> http://www.sqlserver2005.de
> --
> "Jakub Cermak (news)" <ja.cermi@.centrum.cz> schrieb im Newsbeitrag
> news:uaZulUpQFHA.3384@.TK2MSFTNGP10.phx.gbl...
>
>
MSDE Install roll-back
Downloading and running "sql2kdesksp3.exe" worked with no problems.
But running the setup program that was created has proved less successful no matter what options I specify. The installation starts but moments from completion the progress bar begins moving backward. No error message is displayed and the installation dialog simply closes.
Looking in the 'Program Files' directly during the installation shows a SQL directly but this directory is deleted before the installation dialog closes.
I've installed 'ASP.NET Web Matrix'.
What is causing the installation to rollback? Is this a licensing issue?
Some of my attempts so far:
setup SAPWD=hello SecurityMode=SQL
setup SAPWD=hello
setup SAPWD=hello INSTANCENAME=sqlstarterkitThe documentaion SUCKS for beginners (like me). I got it to work after giving the ASP.NET Machine user admin privlages, but who knows if that was the issue. I also setup using similar lines that you did.
In my search for an answer, it seems MANY people have this problem, and no one seems willing to give an answer, or a newbie-friendly how-to.
Good luck,
mikeP|||I'm in the same boat
I get the same rollback response after following the installation instructions.
Although the very 1st time I installed it, I did get a little further with the installation. I was
able to restart and was able to see the the little computer icon (with a flashing green light) located on my desktop toolbar at the botton of the screen, that said (SQL Running) when you placed the the mouse pointer over it.
Next I open up the web Matrix and proceeded to create a Database which was almost successful untill I received the following Message:
Unable to connect to the database server.
Login failed for user 'SA' Reason:
Not assoicated with a trusted SQL Server connection.
So next I thought I would uninstall & Reinstall & try again to see if I would have better luck the 2nd time. But Now each time that I have tried to reinstall MSDE "sql2kdesksp3.exe" &
follow the same installation procedure, I'm only able to get as far as Command prompt
setup and installation, then I get the same installation rollback same as what you descibed.
I also wish someone if anybody has any advice it would be greatly appreciated.
MSDE install problem
Hi,
My computer OS is win2000 +sp3, I download the MSDE setup file(sql2kdesksp3.exe), I followed the instruction of the microsoft web site to install the msde, but during the windows configure the SQL server desktop engine, it hangs up there. I checked the setup log file, it has no error, it goes to sqlredis.exe, and stop there.
Can any one help me for this?
I really appreciated!
zgWhat is the command line you are using to install msde?
-Kashif
Saturday, February 25, 2012
MSDE Install Hangs During Install
Please help!
The istall hangs at:
Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlredis.exe
/q:a"
The work-around code in the MS white papers is not an option,
What is up?
This effects us a great deal as well. I have to say the whole install
scenario for MSDE 2000 has been incredibly frustrating with many issues that
MS could fix, simply KB articled instead.
You can't depend on users not running applications that occasionally stop
pumping their message queue. This just stops the installer dead.
"A Met" wrote:
> Please help!
> The istall hangs at:
> Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlredis.exe
> /q:a"
> The work-around code in the MS white papers is not an option,
> What is up?
>
|||We are having and the install hang at the exact same point. Previously in
the thread there was a reference to a knowledge base article. If there is a
workaround could you post a link to that article or white paper please.
Also mentioned is the fact that the other applications can stop the intstall
by their affect on the message queue. Would having the user close all other
programs stop the install from failing in this case?
"jwf" wrote:
[vbcol=seagreen]
> This effects us a great deal as well. I have to say the whole install
> scenario for MSDE 2000 has been incredibly frustrating with many issues that
> MS could fix, simply KB articled instead.
> You can't depend on users not running applications that occasionally stop
> pumping their message queue. This just stops the installer dead.
>
> "A Met" wrote:
The istall hangs at:
Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlredis.exe
/q:a"
The work-around code in the MS white papers is not an option,
What is up?
This effects us a great deal as well. I have to say the whole install
scenario for MSDE 2000 has been incredibly frustrating with many issues that
MS could fix, simply KB articled instead.
You can't depend on users not running applications that occasionally stop
pumping their message queue. This just stops the installer dead.
"A Met" wrote:
> Please help!
> The istall hangs at:
> Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlredis.exe
> /q:a"
> The work-around code in the MS white papers is not an option,
> What is up?
>
|||We are having and the install hang at the exact same point. Previously in
the thread there was a reference to a knowledge base article. If there is a
workaround could you post a link to that article or white paper please.
Also mentioned is the fact that the other applications can stop the intstall
by their affect on the message queue. Would having the user close all other
programs stop the install from failing in this case?
"jwf" wrote:
[vbcol=seagreen]
> This effects us a great deal as well. I have to say the whole install
> scenario for MSDE 2000 has been incredibly frustrating with many issues that
> MS could fix, simply KB articled instead.
> You can't depend on users not running applications that occasionally stop
> pumping their message queue. This just stops the installer dead.
>
> "A Met" wrote:
MSDE Install fails. No service listed.
I installed MSDE with the following command line:
Setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD=luxing11
but when I start the system, no service and no server appears listed. How to correct this?
Gavin
Dear Andrea,
Thank you,I could find services in the control panel.
Isaac
>--Original Message--
>hi Isaac,
>"Isaac" <anonymous@.discussions.microsoft.com> ha scritto
nel messaggio[vbcol=seagreen]
>news:18b6501c44b0f$67d85540$a001280a@.phx.gbl...
click
>but it shoul'd be there =;-)
>else, go to control panel and search for the Services
Management MMC snap-in
>applet
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>.
>
Setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD=luxing11
but when I start the system, no service and no server appears listed. How to correct this?
Gavin
Dear Andrea,
Thank you,I could find services in the control panel.
Isaac
>--Original Message--
>hi Isaac,
>"Isaac" <anonymous@.discussions.microsoft.com> ha scritto
nel messaggio[vbcol=seagreen]
>news:18b6501c44b0f$67d85540$a001280a@.phx.gbl...
click
>but it shoul'd be there =;-)
>else, go to control panel and search for the Services
Management MMC snap-in
>applet
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>.
>
MSDE Inatallation
Hi,
I downloaded the MSDE release A (MSDE2000A.exe) from below mentioned link.
http://www.microsoft.com/downloads/d...displaylang=en
Extracted the MSDE2000A.exe to local directory (C:\MSDERelA).
Through Command Prompt executed the following command:
setup SAPWD="sa" INSTANCENAME="Testdb" TARGETDIR="C:\MSDERelA" /L*v
"C:/MSDELog.log"
The following message is popedup:
"Please go to control panel to install adn configure system components"
if click ok, setup is aborted.
Note: My system have Windows XP operating system with Service pack 1
please help to properly install MSDE with the setup downloaded.
Regards,
Abdul Saleem
hi Abdhul,
Abdhul Saleem wrote:
> Hi,
> I downloaded the MSDE release A (MSDE2000A.exe) from below mentioned
> link.
> http://www.microsoft.com/downloads/d...displaylang=en
> Extracted the MSDE2000A.exe to local directory (C:\MSDERelA).
> Through Command Prompt executed the following command:
> setup SAPWD="sa" INSTANCENAME="Testdb" TARGETDIR="C:\MSDERelA" /L*v
> "C:/MSDELog.log"
> The following message is popedup:
> "Please go to control panel to install adn configure system
> components" if click ok, setup is aborted.
> Note: My system have Windows XP operating system with Service pack 1
> please help to properly install MSDE with the setup downloaded.
> Regards,
> Abdul Saleem
please verify File & Printer Sharing is enabled, the Server service up and
running too..
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 MSDE release A (MSDE2000A.exe) from below mentioned link.
http://www.microsoft.com/downloads/d...displaylang=en
Extracted the MSDE2000A.exe to local directory (C:\MSDERelA).
Through Command Prompt executed the following command:
setup SAPWD="sa" INSTANCENAME="Testdb" TARGETDIR="C:\MSDERelA" /L*v
"C:/MSDELog.log"
The following message is popedup:
"Please go to control panel to install adn configure system components"
if click ok, setup is aborted.
Note: My system have Windows XP operating system with Service pack 1
please help to properly install MSDE with the setup downloaded.
Regards,
Abdul Saleem
hi Abdhul,
Abdhul Saleem wrote:
> Hi,
> I downloaded the MSDE release A (MSDE2000A.exe) from below mentioned
> link.
> http://www.microsoft.com/downloads/d...displaylang=en
> Extracted the MSDE2000A.exe to local directory (C:\MSDERelA).
> Through Command Prompt executed the following command:
> setup SAPWD="sa" INSTANCENAME="Testdb" TARGETDIR="C:\MSDERelA" /L*v
> "C:/MSDELog.log"
> The following message is popedup:
> "Please go to control panel to install adn configure system
> components" if click ok, setup is aborted.
> Note: My system have Windows XP operating system with Service pack 1
> please help to properly install MSDE with the setup downloaded.
> Regards,
> Abdul Saleem
please verify File & Printer Sharing is enabled, the Server service up and
running too..
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
Monday, February 20, 2012
MSDE hangs on Install
First off, let me say it took me nearly all day to get this working. When you download the sql2decksp3.exe you might think it install like any other program. No. This exe simply unpacks the setup files. The actual setup program, setup.exe must be run from a DOS command prompt... so you've got to look up the correct command line parameters in the sp3reademe.htm file. Something like:
setup INSTANCENAME="InstanceName" SECURITYMODE=SQL SAPWD="AStrongSAPwd"
No problem so far, but then when I go to run the setup.exe with the correct parameters the install goes fine until the last 5 seconds. Then hangs. Again and again. The install program keep getting hung up just before the finish. Each time I had to uninstall and reinstall-- 6 times. When if it hangs you've got to break out with the Task Manager, then do an uninstall from the Control Panel... if... an entry there was created. It usually is.
I tried everything I could think of and then did a search here. There were a few messages. The only one who actually got past this problem said he deleted all references for "Microsoft SQL" in the registry. I tried that too. It didn't work for me. That setup hung in the very same place. Then instead of breaking out and starting again, I tried shutting the machine down, while the setup was hung, thinking that maybe after a restart the installation might continue AND and that point the install completed.
Hope these notes help the next person who runs into the same problem. I also tried putting the modem on standby and disabling Norton anti-virus. Alone that did help, but when I tried all this stuff together... finally at 4:34 PM, I was able to establish a connection, from both VB.NET and with a great FREE MS SQL Manager at http://sqlmanager.net/products/mssql/manager/download
Now I can start. For some reason, the way I think... I can't do any coding until the entire database spec is first set up. Then you write all the add, edit, display and sort form, windows. When designing web applications, you design the database first, then each web form preforms some unique operation or reference on the remote database. I think that's the way it works.
Hey! Hope this helps others.
Paul TownsendSometimes verbose logging can help to pinpoint installation problems:
setup INSTANCENAME="InstanceName" SECURITYMODE=SQL SAPWD="AStrongSAPwd" /L*v c:\MSDEInstall.log
Terri
Subscribe to:
Posts (Atom)