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
Showing posts with label sp4. Show all posts
Showing posts with label sp4. Show all posts
Friday, March 30, 2012
MSDE SP4 Upgrade problem
Recently when I try to upgrade my current MSDE2000 (SP3a) to SP4 in Windows
XP – SP2, the system just keep on failing me. He is the scenario:
1. Download the MSDE 2000 SP4 from Microsoft site
2. Extract the MSDE SP4
3. Run the following command via command prompt or batch file:
echo off
echo "Start to Upgrade MSDE SP4 ... "
setup.exe /UPGRADESP SQLRUN INSTANCENAME=JSNG SECURITYMODE=SQL
UPGRADEUSER=sa UPGRADEPWD=Th3B3st /L*v c:\MSDE_Log.log
echo "SP4 Upgrade Process completed!"
4. Once the above batch file was run, the standard configuration
screen (gathering information) will be triggered
5. However, after a while the installation will just stopped (before
the title of the windows has changed to show the instance name)
6. When I checked on the verbose log, I have found out that the failure
of the installation is due to the system has failed to configure the server.
PFB for the last few rows of the verbose log:
=== Logging stopped: 8/22/2006 17:36:49 ===
MSI (c) (90:88) [17:36:49:865]: Note: 1: 1729
MSI (c) (90:88) [17:36:49:865]: Product: Microsoft SQL Server Desktop Engine
-- Configuration failed.
MSI (c) (90:88) [17:36:49:865]: Grabbed execution mutex.
MSI (c) (90:88) [17:36:49:865]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (90:88) [17:36:49:865]: MainEngineThread is returning 1603
=== Verbose logging stopped: 8/22/2006 17:36:49 ===
7. Since this is the configuration error, so I have tried to locate
the cnfgsvr.out and hope to get some hints from there, but unfortunately the
config server file is still not updated yet where it still keep the old info
during the installation of MSDE 2000 SP3a.
8. When I try to locate the error (value = 3), I have found out the
its due to the system has detected blank sa password, but I am sure that the
password that I has provided is correct. PFB for the error recorded in the
verbose log:
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{EFB70B01-B1F3-4960-AB69-4A280084A60C}
Starting custom action UpgDetectBlankSaLogin()
Entering Function MyMsiEvaluateCondition
MsiEvaluateCondition for VersionNT returned TRUE
End Function MyMsiEvaluateCondition
An error was encountered during connection to server: 1
Ending custom action UpgDetectBlankSaLogin().
Action ended 9:37:45:
UpgDetectBlankSaLogin.2D02443E_7002_4C0B_ABC9_EAB2 C064397B. Return value 3.
Action ended 9:37:45: INSTALL. Return value 3.
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlProgramDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlInstanceName = EASYSHIP
Property(S): SqlSecurityMode = SQL
Property(S): SqlSa...
Property(S): SqlDisableNetworkProtocols = 0
Property(S): SqlDoUpgrade = 1
Property(S): ProductName = Microsoft SQL Server Desktop Engine (EASYSHIP)
Property(S): VersionNT = 501
Property(S): ALLUSERS = 1
Property(S): ARPNOMODIFY = 1
Property(S): DefaultUIFont = Tahoma8
9. I have even try to use a different command line and yet it failed.
PFB for the alternative command line that I have used:
setup.exe /UPGRADESP SQLRUN INSTANCENAME=JSNG SECURITYMODE=SQL SAPWD=Th3B3st
/L*v
10. I have tried the same in a Windows 2000 Std Server - SP4, and yet it
failed.
During my testing, I have closed down all SQL related activities, including
the followings:
1. Microsoft OutLook
2. SQL Agent Service
3. Easyship Scheduler
But I still experience the above.
I have tried to re-run the same in one of my fresh Windows XP (in virtual
machine), and everything just works fine. Could it be any unclean registry
entry that fail this? Or could it be any software component that is
incompatible with this? Does it have anything to do with the version of MS
Installer being installed in my machine? FYI, I have installed the latest MS
Installer 3.1 before when I tried to install SQL Express, however after I
have remove it, the problem still persist.
Do you have any idea on the above? PFA for the versbose log.
HI,
I am also facing the same issue in my domain.
Unable to find much details.
Is your issue resolved?If yes kindly help me out.
Thanks in advance,
Harish K
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
|||HI,
I am also facing the same issue in my domain.
Unable to find much details.
Is your issue resolved?If yes kindly help me out.
Thanks in advance,
Harish K
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
sql
XP – SP2, the system just keep on failing me. He is the scenario:
1. Download the MSDE 2000 SP4 from Microsoft site
2. Extract the MSDE SP4
3. Run the following command via command prompt or batch file:
echo off
echo "Start to Upgrade MSDE SP4 ... "
setup.exe /UPGRADESP SQLRUN INSTANCENAME=JSNG SECURITYMODE=SQL
UPGRADEUSER=sa UPGRADEPWD=Th3B3st /L*v c:\MSDE_Log.log
echo "SP4 Upgrade Process completed!"
4. Once the above batch file was run, the standard configuration
screen (gathering information) will be triggered
5. However, after a while the installation will just stopped (before
the title of the windows has changed to show the instance name)
6. When I checked on the verbose log, I have found out that the failure
of the installation is due to the system has failed to configure the server.
PFB for the last few rows of the verbose log:
=== Logging stopped: 8/22/2006 17:36:49 ===
MSI (c) (90:88) [17:36:49:865]: Note: 1: 1729
MSI (c) (90:88) [17:36:49:865]: Product: Microsoft SQL Server Desktop Engine
-- Configuration failed.
MSI (c) (90:88) [17:36:49:865]: Grabbed execution mutex.
MSI (c) (90:88) [17:36:49:865]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (90:88) [17:36:49:865]: MainEngineThread is returning 1603
=== Verbose logging stopped: 8/22/2006 17:36:49 ===
7. Since this is the configuration error, so I have tried to locate
the cnfgsvr.out and hope to get some hints from there, but unfortunately the
config server file is still not updated yet where it still keep the old info
during the installation of MSDE 2000 SP3a.
8. When I try to locate the error (value = 3), I have found out the
its due to the system has detected blank sa password, but I am sure that the
password that I has provided is correct. PFB for the error recorded in the
verbose log:
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{EFB70B01-B1F3-4960-AB69-4A280084A60C}
Starting custom action UpgDetectBlankSaLogin()
Entering Function MyMsiEvaluateCondition
MsiEvaluateCondition for VersionNT returned TRUE
End Function MyMsiEvaluateCondition
An error was encountered during connection to server: 1
Ending custom action UpgDetectBlankSaLogin().
Action ended 9:37:45:
UpgDetectBlankSaLogin.2D02443E_7002_4C0B_ABC9_EAB2 C064397B. Return value 3.
Action ended 9:37:45: INSTALL. Return value 3.
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlProgramDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlInstanceName = EASYSHIP
Property(S): SqlSecurityMode = SQL
Property(S): SqlSa...
Property(S): SqlDisableNetworkProtocols = 0
Property(S): SqlDoUpgrade = 1
Property(S): ProductName = Microsoft SQL Server Desktop Engine (EASYSHIP)
Property(S): VersionNT = 501
Property(S): ALLUSERS = 1
Property(S): ARPNOMODIFY = 1
Property(S): DefaultUIFont = Tahoma8
9. I have even try to use a different command line and yet it failed.
PFB for the alternative command line that I have used:
setup.exe /UPGRADESP SQLRUN INSTANCENAME=JSNG SECURITYMODE=SQL SAPWD=Th3B3st
/L*v
10. I have tried the same in a Windows 2000 Std Server - SP4, and yet it
failed.
During my testing, I have closed down all SQL related activities, including
the followings:
1. Microsoft OutLook
2. SQL Agent Service
3. Easyship Scheduler
But I still experience the above.
I have tried to re-run the same in one of my fresh Windows XP (in virtual
machine), and everything just works fine. Could it be any unclean registry
entry that fail this? Or could it be any software component that is
incompatible with this? Does it have anything to do with the version of MS
Installer being installed in my machine? FYI, I have installed the latest MS
Installer 3.1 before when I tried to install SQL Express, however after I
have remove it, the problem still persist.
Do you have any idea on the above? PFA for the versbose log.
HI,
I am also facing the same issue in my domain.
Unable to find much details.
Is your issue resolved?If yes kindly help me out.
Thanks in advance,
Harish K
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
|||HI,
I am also facing the same issue in my domain.
Unable to find much details.
Is your issue resolved?If yes kindly help me out.
Thanks in advance,
Harish K
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
sql
MSDE SP4 installation problem
Having a real problem installing SP4 on MSDE. I've read the notes that come
along with the install files and I've tried most every combination that
makes sense in the command line. Here's just one example:
setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
UPGRADEPWD=apasswoord
DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
It's the default instance. The setup command simply returns immediately, no
log created etc.
I'm at a loss to know what's wrong here.
Thanks for any input you can offer.
jimI believe I have fixed this, appears to be in the comand line arguments. I
couldn't get them to work as in the supplied examples, but still haven't
solved the original problem, which is my other post -'Dist Query Problem'
"Jim Bailey" <jimREMOVETHIS@.ANDTHISjbaileygroup.com> wrote in message
news:3uSve.169016$IO.100652@.tornado.tampabay.rr.com...
> Having a real problem installing SP4 on MSDE. I've read the notes that
come
> along with the install files and I've tried most every combination that
> makes sense in the command line. Here's just one example:
> setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
> UPGRADEPWD=apasswoord
> DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
> It's the default instance. The setup command simply returns immediately,
no
> log created etc.
> I'm at a loss to know what's wrong here.
> Thanks for any input you can offer.
> jim
>
along with the install files and I've tried most every combination that
makes sense in the command line. Here's just one example:
setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
UPGRADEPWD=apasswoord
DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
It's the default instance. The setup command simply returns immediately, no
log created etc.
I'm at a loss to know what's wrong here.
Thanks for any input you can offer.
jimI believe I have fixed this, appears to be in the comand line arguments. I
couldn't get them to work as in the supplied examples, but still haven't
solved the original problem, which is my other post -'Dist Query Problem'
"Jim Bailey" <jimREMOVETHIS@.ANDTHISjbaileygroup.com> wrote in message
news:3uSve.169016$IO.100652@.tornado.tampabay.rr.com...
> Having a real problem installing SP4 on MSDE. I've read the notes that
come
> along with the install files and I've tried most every combination that
> makes sense in the command line. Here's just one example:
> setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
> UPGRADEPWD=apasswoord
> DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
> It's the default instance. The setup command simply returns immediately,
no
> log created etc.
> I'm at a loss to know what's wrong here.
> Thanks for any input you can offer.
> jim
>
MSDE SP4 installation problem
Having a real problem installing SP4 on MSDE. I've read the notes that come
along with the install files and I've tried most every combination that
makes sense in the command line. Here's just one example:
setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
UPGRADEPWD=apasswoord
DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
It's the default instance. The setup command simply returns immediately, no
log created etc.
I'm at a loss to know what's wrong here.
Thanks for any input you can offer.
jim
I believe I have fixed this, appears to be in the comand line arguments. I
couldn't get them to work as in the supplied examples, but still haven't
solved the original problem, which is my other post -'Dist Query Problem'
"Jim Bailey" <jimREMOVETHIS@.ANDTHISjbaileygroup.com> wrote in message
news:3uSve.169016$IO.100652@.tornado.tampabay.rr.co m...
> Having a real problem installing SP4 on MSDE. I've read the notes that
come
> along with the install files and I've tried most every combination that
> makes sense in the command line. Here's just one example:
> setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
> UPGRADEPWD=apasswoord
> DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
> It's the default instance. The setup command simply returns immediately,
no
> log created etc.
> I'm at a loss to know what's wrong here.
> Thanks for any input you can offer.
> jim
>
along with the install files and I've tried most every combination that
makes sense in the command line. Here's just one example:
setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
UPGRADEPWD=apasswoord
DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
It's the default instance. The setup command simply returns immediately, no
log created etc.
I'm at a loss to know what's wrong here.
Thanks for any input you can offer.
jim
I believe I have fixed this, appears to be in the comand line arguments. I
couldn't get them to work as in the supplied examples, but still haven't
solved the original problem, which is my other post -'Dist Query Problem'
"Jim Bailey" <jimREMOVETHIS@.ANDTHISjbaileygroup.com> wrote in message
news:3uSve.169016$IO.100652@.tornado.tampabay.rr.co m...
> Having a real problem installing SP4 on MSDE. I've read the notes that
come
> along with the install files and I've tried most every combination that
> makes sense in the command line. Here's just one example:
> setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
> UPGRADEPWD=apasswoord
> DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
> It's the default instance. The setup command simply returns immediately,
no
> log created etc.
> I'm at a loss to know what's wrong here.
> Thanks for any input you can offer.
> jim
>
MSDE SP4 installation problem
Having a real problem installing SP4 on MSDE. I've read the notes that come
along with the install files and I've tried most every combination that
makes sense in the command line. Here's just one example:
setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
UPGRADEPWD=apasswoord
DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
It's the default instance. The setup command simply returns immediately, no
log created etc.
I'm at a loss to know what's wrong here.
Thanks for any input you can offer.
jimI believe I have fixed this, appears to be in the comand line arguments. I
couldn't get them to work as in the supplied examples, but still haven't
solved the original problem, which is my other post -'Dist Query Problem'
"Jim Bailey" <jimREMOVETHIS@.ANDTHISjbaileygroup.com> wrote in message
news:3uSve.169016$IO.100652@.tornado.tampabay.rr.com...
> Having a real problem installing SP4 on MSDE. I've read the notes that
come
> along with the install files and I've tried most every combination that
> makes sense in the command line. Here's just one example:
> setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
> UPGRADEPWD=apasswoord
> DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
> It's the default instance. The setup command simply returns immediately,
no
> log created etc.
> I'm at a loss to know what's wrong here.
> Thanks for any input you can offer.
> jim
>
along with the install files and I've tried most every combination that
makes sense in the command line. Here's just one example:
setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
UPGRADEPWD=apasswoord
DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
It's the default instance. The setup command simply returns immediately, no
log created etc.
I'm at a loss to know what's wrong here.
Thanks for any input you can offer.
jimI believe I have fixed this, appears to be in the comand line arguments. I
couldn't get them to work as in the supplied examples, but still haven't
solved the original problem, which is my other post -'Dist Query Problem'
"Jim Bailey" <jimREMOVETHIS@.ANDTHISjbaileygroup.com> wrote in message
news:3uSve.169016$IO.100652@.tornado.tampabay.rr.com...
> Having a real problem installing SP4 on MSDE. I've read the notes that
come
> along with the install files and I've tried most every combination that
> makes sense in the command line. Here's just one example:
> setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
> UPGRADEPWD=apasswoord
> DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
> It's the default instance. The setup command simply returns immediately,
no
> log created etc.
> I'm at a loss to know what's wrong here.
> Thanks for any input you can offer.
> jim
>
MSDE SP4 Install problems - invalid instance name
Hi,
Seen this question posted in several places, but none of the fixes stated
have done the trick. I'm trying to patch several MSDE instances installed by
Sharepoint. Instance names are SHAREPOINT.All three instances are installed
on W2k3 Servers. When I run the install from the cmd prompt, I use:
<install Dir>\setup /upgradesp sqlrun INSTANCENAME=SHAREPOINT /L*v
c:\MSDELog.log
I have also tried
<install Dir>\setup /upgradesp sqlrun INSTANCENAME=SHAREPOINT
DISABLENETWORKPROTOCOLS=0 /L*v c:\MSDELog.log
Same thing happens. I get an errors that states:"The instance name specified
is invalid". I know this to be untrue - I can query the databases in it
using SQL Client tools (Query analyser)
I've checked out the install package that was used in the registry(
HKEY_CLASSES_ROOT\Installer\Products\95C756568A324 7948B0EAB40BE0DE4F4\SourceList)
which suggests SQLRUN16.msi was used for the install. As this is the case,
all the documentation says I can use SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE
for the installation. However, it still fails.
I have also had to install SP4 onto several instances created by the MS CRM
Outlook client. To do this I have used the following cmd in the cmd prompt:
<install Dir>\setup /upgradesp sqlrun INSTANCENAME=CRM /L*v c:\MSDELog.log
This works perfectly.However, I cannot do this on any of my SHAREPOINT
Instances.
Can anyone assist please?
Many Thanks
John
hi John,
John wrote:
> Hi,
> Seen this question posted in several places, but none of the fixes
> stated have done the trick. I'm trying to patch several MSDE
> instances installed by Sharepoint. Instance names are SHAREPOINT.All
> three instances are installed on W2k3 Servers. When I run the install
> from the cmd prompt, I use:
from the sp4 readme file,
"MSDE 2000 SP4 updates instances of SQL Server 2000 MSDE 2000 and MSDE 2000
Release A. "
Share Point installs a different version of MSDE, known as WMSDE where some
intrinsic MSDE limits has been removed (2gb data file per database) in order
to fullfill Share Point needs and requirements...
so, in my understanding, I think you have to get the new WMSDE package to
upgrade your Share Point instances...
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 Andrea
First of all, many thanks for the reply. Could you post a URL to where I can
download the new WMSDE Patch? I've searched, but all I could find was a
Critical Update and a service pack for Sharepoint. Do I need to install the
who service pack? I thought I had already done that, and my SMS 2003 is not
telling me that the Service Pack is required, only the msde instance
requires updating
Many Thanks
Regards,
John
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3h8f6oFfh31iU1@.individual.net...
> hi John,
> John wrote:
> from the sp4 readme file,
> "MSDE 2000 SP4 updates instances of SQL Server 2000 MSDE 2000 and MSDE
> 2000 Release A. "
> Share Point installs a different version of MSDE, known as WMSDE where
> some intrinsic MSDE limits has been removed (2gb data file per database)
> in order to fullfill Share Point needs and requirements...
> so, in my understanding, I think you have to get the new WMSDE package to
> upgrade your Share Point instances...
> --
> 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 John,
John wrote:
> Hi Andrea
> First of all, many thanks for the reply. Could you post a URL to
> where I can download the new WMSDE Patch? I've searched, but all I
> could find was a Critical Update and a service pack for Sharepoint.
> Do I need to install the who service pack? I thought I had already
> done that, and my SMS 2003 is not telling me that the Service Pack is
> required, only the msde instance requires updating
>
unfortunately I'm not a Share Point guy... have you tried asking in its NG
hyerarchy?
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 Andrea. Thanks for all your help, I'll try there.
Regards,
John
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hb3r4Fg7op9U1@.individual.net...
> hi John,
> John wrote:
> unfortunately I'm not a Share Point guy... have you tried asking in its NG
> hyerarchy?
> --
> 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
>
Seen this question posted in several places, but none of the fixes stated
have done the trick. I'm trying to patch several MSDE instances installed by
Sharepoint. Instance names are SHAREPOINT.All three instances are installed
on W2k3 Servers. When I run the install from the cmd prompt, I use:
<install Dir>\setup /upgradesp sqlrun INSTANCENAME=SHAREPOINT /L*v
c:\MSDELog.log
I have also tried
<install Dir>\setup /upgradesp sqlrun INSTANCENAME=SHAREPOINT
DISABLENETWORKPROTOCOLS=0 /L*v c:\MSDELog.log
Same thing happens. I get an errors that states:"The instance name specified
is invalid". I know this to be untrue - I can query the databases in it
using SQL Client tools (Query analyser)
I've checked out the install package that was used in the registry(
HKEY_CLASSES_ROOT\Installer\Products\95C756568A324 7948B0EAB40BE0DE4F4\SourceList)
which suggests SQLRUN16.msi was used for the install. As this is the case,
all the documentation says I can use SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE
for the installation. However, it still fails.
I have also had to install SP4 onto several instances created by the MS CRM
Outlook client. To do this I have used the following cmd in the cmd prompt:
<install Dir>\setup /upgradesp sqlrun INSTANCENAME=CRM /L*v c:\MSDELog.log
This works perfectly.However, I cannot do this on any of my SHAREPOINT
Instances.
Can anyone assist please?
Many Thanks
John
hi John,
John wrote:
> Hi,
> Seen this question posted in several places, but none of the fixes
> stated have done the trick. I'm trying to patch several MSDE
> instances installed by Sharepoint. Instance names are SHAREPOINT.All
> three instances are installed on W2k3 Servers. When I run the install
> from the cmd prompt, I use:
from the sp4 readme file,
"MSDE 2000 SP4 updates instances of SQL Server 2000 MSDE 2000 and MSDE 2000
Release A. "
Share Point installs a different version of MSDE, known as WMSDE where some
intrinsic MSDE limits has been removed (2gb data file per database) in order
to fullfill Share Point needs and requirements...
so, in my understanding, I think you have to get the new WMSDE package to
upgrade your Share Point instances...
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 Andrea
First of all, many thanks for the reply. Could you post a URL to where I can
download the new WMSDE Patch? I've searched, but all I could find was a
Critical Update and a service pack for Sharepoint. Do I need to install the
who service pack? I thought I had already done that, and my SMS 2003 is not
telling me that the Service Pack is required, only the msde instance
requires updating
Many Thanks
Regards,
John
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3h8f6oFfh31iU1@.individual.net...
> hi John,
> John wrote:
> from the sp4 readme file,
> "MSDE 2000 SP4 updates instances of SQL Server 2000 MSDE 2000 and MSDE
> 2000 Release A. "
> Share Point installs a different version of MSDE, known as WMSDE where
> some intrinsic MSDE limits has been removed (2gb data file per database)
> in order to fullfill Share Point needs and requirements...
> so, in my understanding, I think you have to get the new WMSDE package to
> upgrade your Share Point instances...
> --
> 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 John,
John wrote:
> Hi Andrea
> First of all, many thanks for the reply. Could you post a URL to
> where I can download the new WMSDE Patch? I've searched, but all I
> could find was a Critical Update and a service pack for Sharepoint.
> Do I need to install the who service pack? I thought I had already
> done that, and my SMS 2003 is not telling me that the Service Pack is
> required, only the msde instance requires updating
>
unfortunately I'm not a Share Point guy... have you tried asking in its NG
hyerarchy?
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 Andrea. Thanks for all your help, I'll try there.
Regards,
John
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hb3r4Fg7op9U1@.individual.net...
> hi John,
> John wrote:
> unfortunately I'm not a Share Point guy... have you tried asking in its NG
> hyerarchy?
> --
> 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
>
MSDE SP4 install problem
I attempted to install MSDE SP4 (file SQL2000.MSDE-KB884525-SP4-x86-ENU) on a WinXP Pro SP2 machine.
Command used:
setup SAPWD="ourpw" SECURITYMODE=SQL /L*v c:\MSDELog.log
Install log shows successful install.
MSDE appears to function properly, service starts automatically after reboot, etc.
I can open and work with DB's with a freebie 3rd party GUI called DbaMGR2K, through which I have added the necessary DB user for our locally running ASP application to use the db.
However, when I try to use the DB with our locally running ASP application - connecting with ADO from a dll we wrote, I get the following:
"[DNETLIB]{ConnectionOpen (Connect()).]SQL Server does not exist or access denied"
Any help appreciated.
day10
Hi,
make sure that you connect to the same database and you are using a valid login for connecting. Perhaps you have chosen another authentication mode within the ADO code ? That could explain either the one or the other error message you are getting.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
I think we have solved the issue. We used the SQL Server Network Utility to enable TCP/IP (apparently not enabled by default) and now all appears well.
I wonder if there is a way to enable TCP/IP during the install process. Is there an install flag/option?
|||>> Is there an install flag/option?
Most likely. The flag for this when installing SP3 was "DISABLENETWORKPROTOCOLS=0". I wouldn't think that they would have removed it for SP4.
sqlWednesday, March 28, 2012
msde sp4 autostart sqlagent and other fun
Since msde sp4 changes sqlagent to manual start, I found scm to reset
it back to automatic.
C:\Program Files\Microsoft SQL Server\80\Tools\Binn>scm -Action 7
-Service sqlserveragent -SvcStartT
ype 2
To get msde sp4 to update my default instance, I had to set sqlagent
'log on as' to Local System Account. Other wise it kept uninstalling.
Anyone know syntax to use scm to set the sqlagent log to Local System
Account and then back to my original user after install? Other means?
Needs to be script or bat happy solution.
hi Mike,
Mike wrote:
> Since msde sp4 changes sqlagent to manual start, I found scm to reset
> it back to automatic.
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn>scm -Action 7
> -Service sqlserveragent -SvcStartT
> ype 2
> To get msde sp4 to update my default instance, I had to set sqlagent
> 'log on as' to Local System Account. Other wise it kept uninstalling.
> Anyone know syntax to use scm to set the sqlagent log to Local System
> Account and then back to my original user after install? Other means?
> Needs to be script or bat happy solution.
I know that sp4 changed something about the account requirements to run it's
services... the information provided in
http://support.microsoft.com/?id=283811 is no longer valid.. I'm checking
this article weekly for addendum, still with no luck...
still running my MSDE sp4 boxes under Local System too...
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
it back to automatic.
C:\Program Files\Microsoft SQL Server\80\Tools\Binn>scm -Action 7
-Service sqlserveragent -SvcStartT
ype 2
To get msde sp4 to update my default instance, I had to set sqlagent
'log on as' to Local System Account. Other wise it kept uninstalling.
Anyone know syntax to use scm to set the sqlagent log to Local System
Account and then back to my original user after install? Other means?
Needs to be script or bat happy solution.
hi Mike,
Mike wrote:
> Since msde sp4 changes sqlagent to manual start, I found scm to reset
> it back to automatic.
> C:\Program Files\Microsoft SQL Server\80\Tools\Binn>scm -Action 7
> -Service sqlserveragent -SvcStartT
> ype 2
> To get msde sp4 to update my default instance, I had to set sqlagent
> 'log on as' to Local System Account. Other wise it kept uninstalling.
> Anyone know syntax to use scm to set the sqlagent log to Local System
> Account and then back to my original user after install? Other means?
> Needs to be script or bat happy solution.
I know that sp4 changed something about the account requirements to run it's
services... the information provided in
http://support.microsoft.com/?id=283811 is no longer valid.. I'm checking
this article weekly for addendum, still with no luck...
still running my MSDE sp4 boxes under Local System too...
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
msde sp4
Why can't I execute sp_attach/sp_detach in MSDE? It said it didn't have
those 2 store procedures.
.~. Might, Courage, Vision. http://www.linux-sxs.org
/ v \
/( _ )\ Linux 2.4.31
^ ^ 8:33pm up 4:06 0 users 1.06 0.75Hi
Maybe because you are using the wrong names?
Try
execute master.dbo.sp_attach_db
execute master.dbo.sp_detach_db
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"man-wai chang" <toylet.toylet@.gmail.com> wrote in message
news:e0SpEyMoFHA.2580@.TK2MSFTNGP09.phx.gbl...
> Why can't I execute sp_attach/sp_detach in MSDE? It said it didn't have
> those 2 store procedures.
> --
> .~. Might, Courage, Vision. http://www.linux-sxs.org
> / v \
> /( _ )\ Linux 2.4.31
> ^ ^ 8:33pm up 4:06 0 users 1.06 0.75|||man-wai chang wrote:
> Why can't I execute sp_attach/sp_detach in MSDE? It said it didn't have
> those 2 store procedures.
>
sorry... I forgot. It should be sp_attach_db..
.~. Might, Courage, Vision. http://www.linux-sxs.org
/ v \
/( _ )\ Linux 2.4.31
^ ^ 8:43pm up 4:16 0 users 0.63 0.63|||
> Maybe because you are using the wrong names?
> Try
> execute master.dbo.sp_attach_db
> execute master.dbo.sp_detach_db
yes.. sorry. :)
.~. Might, Courage, Vision. http://www.linux-sxs.org
/ v \
/( _ )\ Linux 2.4.31
^ ^ 8:49pm up 4:22 0 users 0.52 0.58
those 2 store procedures.
.~. Might, Courage, Vision. http://www.linux-sxs.org
/ v \
/( _ )\ Linux 2.4.31
^ ^ 8:33pm up 4:06 0 users 1.06 0.75Hi
Maybe because you are using the wrong names?
Try
execute master.dbo.sp_attach_db
execute master.dbo.sp_detach_db
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"man-wai chang" <toylet.toylet@.gmail.com> wrote in message
news:e0SpEyMoFHA.2580@.TK2MSFTNGP09.phx.gbl...
> Why can't I execute sp_attach/sp_detach in MSDE? It said it didn't have
> those 2 store procedures.
> --
> .~. Might, Courage, Vision. http://www.linux-sxs.org
> / v \
> /( _ )\ Linux 2.4.31
> ^ ^ 8:33pm up 4:06 0 users 1.06 0.75|||man-wai chang wrote:
> Why can't I execute sp_attach/sp_detach in MSDE? It said it didn't have
> those 2 store procedures.
>
sorry... I forgot. It should be sp_attach_db..
.~. Might, Courage, Vision. http://www.linux-sxs.org
/ v \
/( _ )\ Linux 2.4.31
^ ^ 8:43pm up 4:16 0 users 0.63 0.63|||
> Maybe because you are using the wrong names?
> Try
> execute master.dbo.sp_attach_db
> execute master.dbo.sp_detach_db
yes.. sorry. :)
.~. Might, Courage, Vision. http://www.linux-sxs.org
/ v \
/( _ )\ Linux 2.4.31
^ ^ 8:49pm up 4:22 0 users 0.52 0.58
MSDE SP4
Can anyone please help me with upgrading to MSDE 2000 SP4
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
Suhail
Hi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhail
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
Suhail
Hi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhail
MSDE SP4
Can anyone please help me with upgrading to MSDE 2000 SP4
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting workin
g.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server
.
> The instance was installed by default while installing BKUPExec. Evry time
I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installe
d
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting work
ing.
> Thank you for your help.
> Suhail
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting workin
g.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server
.
> The instance was installed by default while installing BKUPExec. Evry time
I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installe
d
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting work
ing.
> Thank you for your help.
> Suhail
MSDE SP4
Can anyone please help me with upgrading to MSDE 2000 SP4
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhailsql
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhailsql
MSDE SP3a on a Server with SQL Server 2000 SP4
A few questions here.
1. I have noticed a problem when MSDE SP3a is installed on a server with SQL
Server SP4. The Registry key value SQLPath at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup loses the last character and that makes the path
to osql, invalid when executing a post replication script. It also breaks
accessing Query Analyzer and SQL Profiler from Enterprise manager among other
problems I'm sure. Is this a known problem? I can't seem to find any
reference to it anywhere in the KB, although that doesn't mean too much.
2. With the problem in question 1, is installing MSDE SP3a on a server with
SQL Server SP4 a supported thing to do? If not, is an installation program
supposed to deliver multiple versions of MSDE and decide at install time
which version is needed for the server in question? This poses a problem if
one releases software with the MSDE SP3a redist and a new service pack for
SQL Server/MSDE is release after. From what I can tell Microsoft doesn't
really handle this, i.e. Windows SharePoint Services comes with a version of
MSDE SP3a and I haven't seen an update to include MSDE SP4 yet.
3. Again following the previous questions, is it ok to install MSDE SP4 on
servers that have SQL Server 2000 SP2 or SP3a?
Thanks in advance for your time to answer my questions.
Paul
hi Paul,
Paul Degneau wrote:
> A few questions here.
> 1. I have noticed a problem when MSDE SP3a is installed on a server
> with SQL Server SP4. The Registry key value SQLPath at
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\80\Tools\ClientSetup loses the last character and that makes
> the path to osql, invalid when executing a post replication script.
> It also breaks accessing Query Analyzer and SQL Profiler from
> Enterprise manager among other problems I'm sure. Is this a known
> problem? I can't seem to find any reference to it anywhere in the
> KB, although that doesn't mean too much.
I've reproduced your reported feedback on a Win2003 standard VMWare virtual
machine, updated at Windows update today fixes but Win2003 sp1...
after installing a default instance of SQL Server 2000 Dev Edition and
upgrading it to sp4 I've the reported registry entry..
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup
SQLPath = C:\Program Files\Microsoft SQL Server\80\Tools
installing MSDE sp3 from the
http://www.microsoft.com/sql/downloads/2000/sp3.asp package resulted in the
reported behavior, truncating the SQLPath key to C:\Program Files\Microsoft
SQL Server\80\Tool (without "s") and of course inhibiting the call from
Enterprise Manager to launch QA and Profiler..
running oSql.exe from the command line works as expected... can not
understand the
>and that makes the path to osql,
>invalid when executing a post replication script.
but if the registry key is inspected to run oSql, of course it will fail...
just to test, I fixed the registry entry and installed MSDE from the MSDE
Release A package, http://www.microsoft.com/sql/msde/do.../download.asp,
with the very same result
as additional side note, unistalling the MSDE sp3 instance (that from
http://www.microsoft.com/sql/downloads/2000/sp3.asp package) cleared the
"Startup" folder from the "SQL Server Service Manager" link
I'll pass this "feature" to Microsoft support..
> 2. With the problem in question 1, is installing MSDE SP3a on a
> server with SQL Server SP4 a supported thing to do? If not, is an
> installation program supposed to deliver multiple versions of MSDE
> and decide at install time which version is needed for the server in
> question? This poses a problem if one releases software with the
> MSDE SP3a redist and a new service pack for SQL Server/MSDE is
> release after. From what I can tell Microsoft doesn't really handle
> this, i.e. Windows SharePoint Services comes with a version of MSDE
> SP3a and I haven't seen an update to include MSDE SP4 yet.
AFAIK, an updated version of MSDE Release A updated at service pack 4 has
been promised, but I've no idea about the time frame... about Share Point
WMSDE I do not really know... WMSDE is a specialised version of MSDE and I
expect an updated version will be available... but that's my opinion..
no refresh of SQL Server installation package has been publicised.. you have
to go from the standard path.. install the RTM version and then (manually)
install the desired service pack level (sp3 is the supported SQL Server 2000
version on Win2003 platform)
as regard MSDE, the currently available packages do not (for sure) grant you
a way to decide at run time the service pack level to be installed.. if you
choose sp4 there you are, the same for sp3...
> 3. Again following the previous questions, is it ok to install MSDE
> SP4 on servers that have SQL Server 2000 SP2 or SP3a?
>
actually it should be safe, but consider that installing sp4 updates all
shared bins (those in \Program Files\Microsoft SQL Server\80 folder) to it's
service pack level, but MSDE does not include the full set of tools and bin
but a bunch of them like osql, bcp, svrnecn.exe, SQL-DMO components... a
little mix will be the result
on non Win2003/WinXP systems it will additionaly upgrade MDAC stack to
2.8sp1 (that from WinXP sp2), but this is another story...
but I do think, at the end of all this, that it has been tested
I'll foward the registry stuff ...
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
1. I have noticed a problem when MSDE SP3a is installed on a server with SQL
Server SP4. The Registry key value SQLPath at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup loses the last character and that makes the path
to osql, invalid when executing a post replication script. It also breaks
accessing Query Analyzer and SQL Profiler from Enterprise manager among other
problems I'm sure. Is this a known problem? I can't seem to find any
reference to it anywhere in the KB, although that doesn't mean too much.
2. With the problem in question 1, is installing MSDE SP3a on a server with
SQL Server SP4 a supported thing to do? If not, is an installation program
supposed to deliver multiple versions of MSDE and decide at install time
which version is needed for the server in question? This poses a problem if
one releases software with the MSDE SP3a redist and a new service pack for
SQL Server/MSDE is release after. From what I can tell Microsoft doesn't
really handle this, i.e. Windows SharePoint Services comes with a version of
MSDE SP3a and I haven't seen an update to include MSDE SP4 yet.
3. Again following the previous questions, is it ok to install MSDE SP4 on
servers that have SQL Server 2000 SP2 or SP3a?
Thanks in advance for your time to answer my questions.
Paul
hi Paul,
Paul Degneau wrote:
> A few questions here.
> 1. I have noticed a problem when MSDE SP3a is installed on a server
> with SQL Server SP4. The Registry key value SQLPath at
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\80\Tools\ClientSetup loses the last character and that makes
> the path to osql, invalid when executing a post replication script.
> It also breaks accessing Query Analyzer and SQL Profiler from
> Enterprise manager among other problems I'm sure. Is this a known
> problem? I can't seem to find any reference to it anywhere in the
> KB, although that doesn't mean too much.
I've reproduced your reported feedback on a Win2003 standard VMWare virtual
machine, updated at Windows update today fixes but Win2003 sp1...
after installing a default instance of SQL Server 2000 Dev Edition and
upgrading it to sp4 I've the reported registry entry..
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup
SQLPath = C:\Program Files\Microsoft SQL Server\80\Tools
installing MSDE sp3 from the
http://www.microsoft.com/sql/downloads/2000/sp3.asp package resulted in the
reported behavior, truncating the SQLPath key to C:\Program Files\Microsoft
SQL Server\80\Tool (without "s") and of course inhibiting the call from
Enterprise Manager to launch QA and Profiler..
running oSql.exe from the command line works as expected... can not
understand the
>and that makes the path to osql,
>invalid when executing a post replication script.
but if the registry key is inspected to run oSql, of course it will fail...
just to test, I fixed the registry entry and installed MSDE from the MSDE
Release A package, http://www.microsoft.com/sql/msde/do.../download.asp,
with the very same result
as additional side note, unistalling the MSDE sp3 instance (that from
http://www.microsoft.com/sql/downloads/2000/sp3.asp package) cleared the
"Startup" folder from the "SQL Server Service Manager" link
I'll pass this "feature" to Microsoft support..
> 2. With the problem in question 1, is installing MSDE SP3a on a
> server with SQL Server SP4 a supported thing to do? If not, is an
> installation program supposed to deliver multiple versions of MSDE
> and decide at install time which version is needed for the server in
> question? This poses a problem if one releases software with the
> MSDE SP3a redist and a new service pack for SQL Server/MSDE is
> release after. From what I can tell Microsoft doesn't really handle
> this, i.e. Windows SharePoint Services comes with a version of MSDE
> SP3a and I haven't seen an update to include MSDE SP4 yet.
AFAIK, an updated version of MSDE Release A updated at service pack 4 has
been promised, but I've no idea about the time frame... about Share Point
WMSDE I do not really know... WMSDE is a specialised version of MSDE and I
expect an updated version will be available... but that's my opinion..
no refresh of SQL Server installation package has been publicised.. you have
to go from the standard path.. install the RTM version and then (manually)
install the desired service pack level (sp3 is the supported SQL Server 2000
version on Win2003 platform)
as regard MSDE, the currently available packages do not (for sure) grant you
a way to decide at run time the service pack level to be installed.. if you
choose sp4 there you are, the same for sp3...
> 3. Again following the previous questions, is it ok to install MSDE
> SP4 on servers that have SQL Server 2000 SP2 or SP3a?
>
actually it should be safe, but consider that installing sp4 updates all
shared bins (those in \Program Files\Microsoft SQL Server\80 folder) to it's
service pack level, but MSDE does not include the full set of tools and bin
but a bunch of them like osql, bcp, svrnecn.exe, SQL-DMO components... a
little mix will be the result
on non Win2003/WinXP systems it will additionaly upgrade MDAC stack to
2.8sp1 (that from WinXP sp2), but this is another story...
but I do think, at the end of all this, that it has been tested
I'll foward the registry stuff ...
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
Friday, March 23, 2012
MSDE over TCP/IP
I've got a SQL Server Desktop Engine (version 8.00.2039 - SP4) installation
running our SharePoint site. I now need to connect to this database remotely
via TCP/IP, but can't get it to enable the protocol.
The log file always just says:
2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-12-11 12:13:46.39 server SQL server listening on Shared Memory.
I've tried all the suggestions I've heard on the internet. What I've tried:
Install the latest MSDE Service Pack (SP4)
Use SVRNETCN.exe to enable the TCP/IP Protocol
Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433, Restart
Service.
I've hard reset the machine, I've installed all the latest service packs on
this machine. I've disabled the firewall. I've tried ports other than 1433.
I've tried enabling Named Pipes & NWLink at various times as well. No matter
what I do, the log still shows it listening only on shared memory.
Any assistance would be greatly appreciated as I'm completely stumped.
Andrew Faust
http://www.andrewfaust.com
=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
> I've got a SQL Server Desktop Engine (version 8.00.2039 - SP4)
> installation running our SharePoint site. I now need to connect to
> this database remotely via TCP/IP, but can't get it to enable the
> protocol.
> The log file always just says:
> 2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version
> '8.0.2039'. 2007-12-11 12:13:46.39 server SQL server listening on
> Shared Memory.
> I've tried all the suggestions I've heard on the internet. What I've
> tried:
> Install the latest MSDE Service Pack (SP4)
> Use SVRNETCN.exe to enable the TCP/IP Protocol
> Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433,
> Restart Service.
> I've hard reset the machine, I've installed all the latest service
> packs on this machine. I've disabled the firewall. I've tried ports
> other than 1433. I've tried enabling Named Pipes & NWLink at various
> times as well. No matter what I do, the log still shows it listening
> only on shared memory.
> Any assistance would be greatly appreciated as I'm completely stumped.
If you see no effects at all from using svrnetcn.exe, perhaps you have got
multiple instances installed. Drop down the "Instances on this server"
combo at the top of the General tab of the svrnetcn.exe dialog (similarly
the Server combo at the top of the SQL Server Service Manager dialog).
|||Thanks for the response.
Unfortunately, that's not the problem. There is only 1 instance installed on
this server. I forgot to mention this before and don't know if it makes a
difference, but this is a named instance. It's called DOCMGR\SHAREPOINT. It's
also running on Windows Server 2003 with all the latest service packs
installed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:
> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
>
> If you see no effects at all from using svrnetcn.exe, perhaps you have got
> multiple instances installed. Drop down the "Instances on this server"
> combo at the top of the General tab of the svrnetcn.exe dialog (similarly
> the Server combo at the top of the SQL Server Service Manager dialog).
>
|||=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
> Thanks for the response.
> Unfortunately, that's not the problem. There is only 1 instance
> installed on this server. I forgot to mention this before and don't
> know if it makes a difference, but this is a named instance. It's
> called DOCMGR\SHAREPOINT. It's also running on Windows Server 2003
> with all the latest service packs installed.
>
Well, it was something that was possible, given the symptoms you described.
Sorry, I'm out of further ideas. Good luck!
|||I appreciate the effort. I've finally given up on trying to make it work and
have moved my SharePoint to a full install of SQL Server 2000 and gotten the
functionality I needed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:
> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
>
> Well, it was something that was possible, given the symptoms you described.
> Sorry, I'm out of further ideas. Good luck!
>
running our SharePoint site. I now need to connect to this database remotely
via TCP/IP, but can't get it to enable the protocol.
The log file always just says:
2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-12-11 12:13:46.39 server SQL server listening on Shared Memory.
I've tried all the suggestions I've heard on the internet. What I've tried:
Install the latest MSDE Service Pack (SP4)
Use SVRNETCN.exe to enable the TCP/IP Protocol
Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433, Restart
Service.
I've hard reset the machine, I've installed all the latest service packs on
this machine. I've disabled the firewall. I've tried ports other than 1433.
I've tried enabling Named Pipes & NWLink at various times as well. No matter
what I do, the log still shows it listening only on shared memory.
Any assistance would be greatly appreciated as I'm completely stumped.
Andrew Faust
http://www.andrewfaust.com
=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
> I've got a SQL Server Desktop Engine (version 8.00.2039 - SP4)
> installation running our SharePoint site. I now need to connect to
> this database remotely via TCP/IP, but can't get it to enable the
> protocol.
> The log file always just says:
> 2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version
> '8.0.2039'. 2007-12-11 12:13:46.39 server SQL server listening on
> Shared Memory.
> I've tried all the suggestions I've heard on the internet. What I've
> tried:
> Install the latest MSDE Service Pack (SP4)
> Use SVRNETCN.exe to enable the TCP/IP Protocol
> Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433,
> Restart Service.
> I've hard reset the machine, I've installed all the latest service
> packs on this machine. I've disabled the firewall. I've tried ports
> other than 1433. I've tried enabling Named Pipes & NWLink at various
> times as well. No matter what I do, the log still shows it listening
> only on shared memory.
> Any assistance would be greatly appreciated as I'm completely stumped.
If you see no effects at all from using svrnetcn.exe, perhaps you have got
multiple instances installed. Drop down the "Instances on this server"
combo at the top of the General tab of the svrnetcn.exe dialog (similarly
the Server combo at the top of the SQL Server Service Manager dialog).
|||Thanks for the response.
Unfortunately, that's not the problem. There is only 1 instance installed on
this server. I forgot to mention this before and don't know if it makes a
difference, but this is a named instance. It's called DOCMGR\SHAREPOINT. It's
also running on Windows Server 2003 with all the latest service packs
installed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:
> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
>
> If you see no effects at all from using svrnetcn.exe, perhaps you have got
> multiple instances installed. Drop down the "Instances on this server"
> combo at the top of the General tab of the svrnetcn.exe dialog (similarly
> the Server combo at the top of the SQL Server Service Manager dialog).
>
|||=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
> Thanks for the response.
> Unfortunately, that's not the problem. There is only 1 instance
> installed on this server. I forgot to mention this before and don't
> know if it makes a difference, but this is a named instance. It's
> called DOCMGR\SHAREPOINT. It's also running on Windows Server 2003
> with all the latest service packs installed.
>
Well, it was something that was possible, given the symptoms you described.
Sorry, I'm out of further ideas. Good luck!
|||I appreciate the effort. I've finally given up on trying to make it work and
have moved my SharePoint to a full install of SQL Server 2000 and gotten the
functionality I needed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:
> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
>
> Well, it was something that was possible, given the symptoms you described.
> Sorry, I'm out of further ideas. Good luck!
>
Monday, March 19, 2012
MSDE Named Service Connection Problem
I installed SQL 2000 MSDE 2000RelA on Win2K Adv. Server w/ Win2K SP4 (fully
patched), and operating as the only domain controller. I have also run the
IISLockdown Tool on this server.
I originally ran setup using the following parameters:
setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
with the following parameters:
setup sapwd="xxxxxxx" instancename=WSUS
I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
connect to any service and appears in the task bar with a blank icon. When I
open the Service Manager, all fields (server,services) are blank. Pressing
start button will give me:
"The service control action cannot be completed as no
service has been selected"
I entered the server's name in the server field, but no services can be
resolved.
I see MSSQL$WSUS service has started. Further down I noticed
SQLAgent$TESTING service had not started. I started that up, but no change.
Also tried to startup MSSQLServerADHelper but it gave me an error.
I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
keys and SQL Server folder under Program Files.
I again re-installed using the sapwd and instancename parameters but to no
avail.
Can anyone tell me how I can get this working properly?
Thanks!
You could have tried to enter "ComputerName\WSUS" in the service manager
when showed nothing in the server list, and then clicked "Start" button.
Somethimes, for some reason, service manager could not detect any running
SQL/MSDE on the computer/network.
"stantm1" <stantm1@.discussions.microsoft.com> wrote in message
news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>I installed SQL 2000 MSDE 2000RelA on Win2K Adv. Server w/ Win2K SP4 (fully
> patched), and operating as the only domain controller. I have also run the
> IISLockdown Tool on this server.
> I originally ran setup using the following parameters:
> setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
> I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
> with the following parameters:
> setup sapwd="xxxxxxx" instancename=WSUS
> I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
> connect to any service and appears in the task bar with a blank icon. When
> I
> open the Service Manager, all fields (server,services) are blank. Pressing
> start button will give me:
> "The service control action cannot be completed as no
> service has been selected"
> I entered the server's name in the server field, but no services can be
> resolved.
> I see MSSQL$WSUS service has started. Further down I noticed
> SQLAgent$TESTING service had not started. I started that up, but no
> change.
> Also tried to startup MSSQLServerADHelper but it gave me an error.
> I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
> keys and SQL Server folder under Program Files.
> I again re-installed using the sapwd and instancename parameters but to no
> avail.
> Can anyone tell me how I can get this working properly?
> Thanks!
|||Thanks, Norman. I'll give it a try.
"Norman Yuan" wrote:
> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>
>
|||Actually it found the instance of sql server just fine. My machine was in
the list of sql servers but when i try to connect to it i have problems.
Just to let you know im using Windows Authentication and i am an
administrator on this machine.
Brent
"Norman Yuan" <NotReal@.NotReal.not> wrote in message
news:usGQBJbLGHA.3496@.TK2MSFTNGP14.phx.gbl...
> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>
patched), and operating as the only domain controller. I have also run the
IISLockdown Tool on this server.
I originally ran setup using the following parameters:
setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
with the following parameters:
setup sapwd="xxxxxxx" instancename=WSUS
I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
connect to any service and appears in the task bar with a blank icon. When I
open the Service Manager, all fields (server,services) are blank. Pressing
start button will give me:
"The service control action cannot be completed as no
service has been selected"
I entered the server's name in the server field, but no services can be
resolved.
I see MSSQL$WSUS service has started. Further down I noticed
SQLAgent$TESTING service had not started. I started that up, but no change.
Also tried to startup MSSQLServerADHelper but it gave me an error.
I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
keys and SQL Server folder under Program Files.
I again re-installed using the sapwd and instancename parameters but to no
avail.
Can anyone tell me how I can get this working properly?
Thanks!
You could have tried to enter "ComputerName\WSUS" in the service manager
when showed nothing in the server list, and then clicked "Start" button.
Somethimes, for some reason, service manager could not detect any running
SQL/MSDE on the computer/network.
"stantm1" <stantm1@.discussions.microsoft.com> wrote in message
news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>I installed SQL 2000 MSDE 2000RelA on Win2K Adv. Server w/ Win2K SP4 (fully
> patched), and operating as the only domain controller. I have also run the
> IISLockdown Tool on this server.
> I originally ran setup using the following parameters:
> setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
> I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
> with the following parameters:
> setup sapwd="xxxxxxx" instancename=WSUS
> I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
> connect to any service and appears in the task bar with a blank icon. When
> I
> open the Service Manager, all fields (server,services) are blank. Pressing
> start button will give me:
> "The service control action cannot be completed as no
> service has been selected"
> I entered the server's name in the server field, but no services can be
> resolved.
> I see MSSQL$WSUS service has started. Further down I noticed
> SQLAgent$TESTING service had not started. I started that up, but no
> change.
> Also tried to startup MSSQLServerADHelper but it gave me an error.
> I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
> keys and SQL Server folder under Program Files.
> I again re-installed using the sapwd and instancename parameters but to no
> avail.
> Can anyone tell me how I can get this working properly?
> Thanks!
|||Thanks, Norman. I'll give it a try.
"Norman Yuan" wrote:
> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>
>
|||Actually it found the instance of sql server just fine. My machine was in
the list of sql servers but when i try to connect to it i have problems.
Just to let you know im using Windows Authentication and i am an
administrator on this machine.
Brent
"Norman Yuan" <NotReal@.NotReal.not> wrote in message
news:usGQBJbLGHA.3496@.TK2MSFTNGP14.phx.gbl...
> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>
Friday, March 9, 2012
MSDE installation/connection issues
I installed MSDE (sp3a) in a Windows 2000 server SP4. This is configured to
be a domain controller and (AD turned on). I can use MSDE webadmin to
access the database instance fine. I have a couple of problems.
1. MSSQLServerADHelper service does not startup.
System log message is:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Corresponding Application log error is:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
2.Despite following the instructions in KB article: 840219 I still 'm not
able to login to MSDE using OSQL from a command prompt. Error message is:
Cr>osql -U domain\administrator -P xxxx
Login failed for user 'domain\administrator'. Reason: Not associated with a
trusted SQL Server connection.
Is something wrong with my syntax for the value for the -U parameter? I
restarted the SQL server and the agent services after following the steps in
840219.
Any suggestions appreciated.
hi,
"public.microsoft.com" <lakamsani AT gmail.com> ha scritto nel messaggio
news:%23kZ5Z$cbEHA.3684@.TK2MSFTNGP09.phx.gbl...
> I installed MSDE (sp3a) in a Windows 2000 server SP4. This is configured
to
> be a domain controller and (AD turned on). I can use MSDE webadmin to
> access the database instance fine. I have a couple of problems.
> 1. MSSQLServerADHelper service does not startup.
> System log message is:
> The MSSQLServerADHelper service terminated with service-specific error
> 3221225572.
please have a look at http://tinyurl.com/6qwgg
> 2.Despite following the instructions in KB article: 840219 I still 'm not
> able to login to MSDE using OSQL from a command prompt. Error message is:
> Cr>osql -U domain\administrator -P xxxx
> Login failed for user 'domain\administrator'. Reason: Not associated with
a
> trusted SQL Server connection.
> Is something wrong with my syntax for the value for the -U parameter? I
> restarted the SQL server and the agent services after following the steps
in
> 840219.
for trusted connections, you shoul'd pass the -E parameter (where -E
specifys a trusted connection using you actual WindowsNT login credential)
instead that providing SQL Server authenticated related credentials...
tipically
c:\>osql -E
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
be a domain controller and (AD turned on). I can use MSDE webadmin to
access the database instance fine. I have a couple of problems.
1. MSSQLServerADHelper service does not startup.
System log message is:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Corresponding Application log error is:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
2.Despite following the instructions in KB article: 840219 I still 'm not
able to login to MSDE using OSQL from a command prompt. Error message is:
Cr>osql -U domain\administrator -P xxxx
Login failed for user 'domain\administrator'. Reason: Not associated with a
trusted SQL Server connection.
Is something wrong with my syntax for the value for the -U parameter? I
restarted the SQL server and the agent services after following the steps in
840219.
Any suggestions appreciated.
hi,
"public.microsoft.com" <lakamsani AT gmail.com> ha scritto nel messaggio
news:%23kZ5Z$cbEHA.3684@.TK2MSFTNGP09.phx.gbl...
> I installed MSDE (sp3a) in a Windows 2000 server SP4. This is configured
to
> be a domain controller and (AD turned on). I can use MSDE webadmin to
> access the database instance fine. I have a couple of problems.
> 1. MSSQLServerADHelper service does not startup.
> System log message is:
> The MSSQLServerADHelper service terminated with service-specific error
> 3221225572.
please have a look at http://tinyurl.com/6qwgg
> 2.Despite following the instructions in KB article: 840219 I still 'm not
> able to login to MSDE using OSQL from a command prompt. Error message is:
> Cr>osql -U domain\administrator -P xxxx
> Login failed for user 'domain\administrator'. Reason: Not associated with
a
> trusted SQL Server connection.
> Is something wrong with my syntax for the value for the -U parameter? I
> restarted the SQL server and the agent services after following the steps
in
> 840219.
for trusted connections, you shoul'd pass the -E parameter (where -E
specifys a trusted connection using you actual WindowsNT login credential)
instead that providing SQL Server authenticated related credentials...
tipically
c:\>osql -E
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
Saturday, February 25, 2012
MSDE Install Failure
I am trying to install MSDE2 on Win2k server with SP4, as with many other
posts when I try and install it just rolls back. The error log generated
lists
Starting custom action NoRebootReplace
TempFolder Property is C:\WINNT\TEMP\
Source Dir Property is C:\WINNT\TEMP\SqlSetup\Temp
NoRebootConnectRepl returned: 3
Action ended 16:53:55: InstallFinalize. Return value 3.
Action ended 16:53:55: INSTALL. Return value 3.
Does anyone know why this would be?
Many Thanks
hi Phil,
"Phil Milburn" <phil.milburn@.cmiplc.co.uk> ha scritto nel messaggio
news:OqaSZ%238pEHA.2604@.TK2MSFTNGP10.phx.gbl
> I am trying to install MSDE2 on Win2k server with SP4, as with many
> other posts when I try and install it just rolls back. The error log
> generated lists
> Starting custom action NoRebootReplace
> TempFolder Property is C:\WINNT\TEMP\
> Source Dir Property is C:\WINNT\TEMP\SqlSetup\Temp
> NoRebootConnectRepl returned: 3
> Action ended 16:53:55: InstallFinalize. Return value 3.
> Action ended 16:53:55: INSTALL. Return value 3.
> Does anyone know why this would be?
> Many Thanks
are you installing on Terminal Server using Application Server Mode?
please add about 10/20 rows before and after the retun value 3 line
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
posts when I try and install it just rolls back. The error log generated
lists
Starting custom action NoRebootReplace
TempFolder Property is C:\WINNT\TEMP\
Source Dir Property is C:\WINNT\TEMP\SqlSetup\Temp
NoRebootConnectRepl returned: 3
Action ended 16:53:55: InstallFinalize. Return value 3.
Action ended 16:53:55: INSTALL. Return value 3.
Does anyone know why this would be?
Many Thanks
hi Phil,
"Phil Milburn" <phil.milburn@.cmiplc.co.uk> ha scritto nel messaggio
news:OqaSZ%238pEHA.2604@.TK2MSFTNGP10.phx.gbl
> I am trying to install MSDE2 on Win2k server with SP4, as with many
> other posts when I try and install it just rolls back. The error log
> generated lists
> Starting custom action NoRebootReplace
> TempFolder Property is C:\WINNT\TEMP\
> Source Dir Property is C:\WINNT\TEMP\SqlSetup\Temp
> NoRebootConnectRepl returned: 3
> Action ended 16:53:55: InstallFinalize. Return value 3.
> Action ended 16:53:55: INSTALL. Return value 3.
> Does anyone know why this would be?
> Many Thanks
are you installing on Terminal Server using Application Server Mode?
please add about 10/20 rows before and after the retun value 3 line
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Subscribe to:
Posts (Atom)