HI
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Showing posts with label upgrade. Show all posts
Showing posts with label upgrade. Show all posts
Friday, March 30, 2012
MSDE to SQL Server
HI
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
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
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
Wednesday, March 28, 2012
MSDE SP4
Can anyone please help me with upgrading to MSDE 2000 SP4
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
Suhail
Hi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhail
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
Suhail
Hi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhail
MSDE SP4
Can anyone please help me with upgrading to MSDE 2000 SP4
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting workin
g.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server
.
> The instance was installed by default while installing BKUPExec. Evry time
I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installe
d
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting work
ing.
> Thank you for your help.
> Suhail
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting workin
g.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server
.
> The instance was installed by default while installing BKUPExec. Evry time
I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installe
d
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting work
ing.
> Thank you for your help.
> Suhail
MSDE SP4
Can anyone please help me with upgrading to MSDE 2000 SP4
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhailsql
I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
The instance was installed by default while installing BKUPExec. Evry time I
run the upgrade from the command line using
setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
the upgrade fails. I am guessing it is failing becasue it was not installed
using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
Thank you for your help.
SuhailHi
This command seems to have been recommended in other posts except there was
no spaces around the "=" see http://tinyurl.com/b4lbw
John
"suhail" wrote:
> Can anyone please help me with upgrading to MSDE 2000 SP4
> I need to upgrade BKUPExec Instance from SP3 to SP4 on Windows 2003 server.
> The instance was installed by default while installing BKUPExec. Evry time I
> run the upgrade from the command line using
> setup /upgradesp sqlrun INSTANCENAME = BKUPEXEC /L*v C:\MSDElog.log
> the upgrade fails. I am guessing it is failing becasue it was not installed
> using the MSDE 2000 setup CD. Is it any way to upgrade it and getting working.
> Thank you for your help.
> Suhailsql
MSDE SP3a Upgrade problem
I just upgraded my desktop engine MSDE 1.0 to MSDE 2000 SP3a. Everything seemed to go well, MSSQLSERVER AND SQLSERVER Agent Services are running, problem is, I can no longer see the particular instance on the network from Enterprise Manager.
The installation instructions specified that if the Instance was to accept connections from applications on other computers not to specify the DISABLENETWORKPROTOCOLS parameter, so I didn't.
I'm a little green with this, can anyone suggest a place to start troubleshooting?Can you pull it up in Query Analyzer. Just type in (local) or whatever your instance name is for the connection server and see if it connects.
The installation instructions specified that if the Instance was to accept connections from applications on other computers not to specify the DISABLENETWORKPROTOCOLS parameter, so I didn't.
I'm a little green with this, can anyone suggest a place to start troubleshooting?Can you pull it up in Query Analyzer. Just type in (local) or whatever your instance name is for the connection server and see if it connects.
Wednesday, March 21, 2012
MSDE not keeping an ALTER modifcation
Hi Everyone,
Today i faced the following issue : An MSDE Database I had been working
on in the morning in order to be able to upgrade our software, with
the statement:
Through Osql :
1)IF ( (SELECT currentSize= (size /128) FROM
PMI_Operations.dbo.sysfiles WHERE groupid = 1) < 200)
2)PRINT 'PMI_Operations under 200Mb'
3)GO
'PMI_Operations under 200Mb'
1)IF ( (SELECT currentSize= (size /128) FROM
PMI_Operations.dbo.sysfiles WHERE groupid = 1) < 200)
2)PRINT 'PMI_Operations under 200Mb...please wait while increasing'
3)ALTER DATABASE [PMI_Operations] MODIFY FILE (NAME =
N'PMI_Operations', SIZE = 200)
'PMI_Operations under 200Mb...please wait while increasing'
1)
It worked fine.
I came back to the box in the afternoon, after rush hour, and did same
test again (
1)IF ( (SELECT currentSize= (size /128) FROM
PMI_Operations.dbo.sysfiles WHERE groupid = 1) < 200)
2)PRINT 'PMI_Operations under 200Mb'
3)GO
expecting it to not display the print message, but it did !! I had to
run the ALTER again.
What could have caused my morning ALTER to be discarded by the
Afternoon ?
Thanks for any help you can bring
Rgards
hi,
Frogbeef wrote:
> expecting it to not display the print message, but it did !! I had to
> run the ALTER again.
> What could have caused my morning ALTER to be discarded by the
> Afternoon ?
do you have a scheduled job to "shrink" databases?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply
Today i faced the following issue : An MSDE Database I had been working
on in the morning in order to be able to upgrade our software, with
the statement:
Through Osql :
1)IF ( (SELECT currentSize= (size /128) FROM
PMI_Operations.dbo.sysfiles WHERE groupid = 1) < 200)
2)PRINT 'PMI_Operations under 200Mb'
3)GO
'PMI_Operations under 200Mb'
1)IF ( (SELECT currentSize= (size /128) FROM
PMI_Operations.dbo.sysfiles WHERE groupid = 1) < 200)
2)PRINT 'PMI_Operations under 200Mb...please wait while increasing'
3)ALTER DATABASE [PMI_Operations] MODIFY FILE (NAME =
N'PMI_Operations', SIZE = 200)
'PMI_Operations under 200Mb...please wait while increasing'
1)
It worked fine.
I came back to the box in the afternoon, after rush hour, and did same
test again (
1)IF ( (SELECT currentSize= (size /128) FROM
PMI_Operations.dbo.sysfiles WHERE groupid = 1) < 200)
2)PRINT 'PMI_Operations under 200Mb'
3)GO
expecting it to not display the print message, but it did !! I had to
run the ALTER again.
What could have caused my morning ALTER to be discarded by the
Afternoon ?
Thanks for any help you can bring
Rgards
hi,
Frogbeef wrote:
> expecting it to not display the print message, but it did !! I had to
> run the ALTER again.
> What could have caused my morning ALTER to be discarded by the
> Afternoon ?
do you have a scheduled job to "shrink" databases?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply
Monday, February 20, 2012
MSDE fail after upgrade from WIN98 to WINXP HOME
Anyone can help?
I installed MSDE in WIN98 and then upgrade to WINXP home, after that, MSDE failure and i can't reinstall MSDE again, already call microsoft support and try something but no help at all.
John
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Not to be rude, but your first mistake was attempting to upgrade Win9x to
XP.
MSDE installed under Win9x is a completely different animal than an
installation on the NT style operating systems. With Win9x there are no
service applications so MSDE runs as a standard application when the system
starts up. When you upgrade your OS to XP there is no magical conversion of
the MSDE installation to it running as a service. Your best bet is to backup
your databases and then manually uninstall MSDE. Microsoft has an article on
how to do this at:
http://support.microsoft.com/default...b;en-us;290991
After uninstalling MSDE re-install it and restore your databases.
Jim
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:OzBSSNkjEHA.1404@.TK2MSFTNGP09.phx.gbl...
> Anyone can help?
> I installed MSDE in WIN98 and then upgrade to WINXP home, after that, MSDE
failure and i can't reinstall MSDE again, already call microsoft support and
try something but no help at all.
> John
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
|||Hi Jim,
Thanks for your advice, i will try it !!
John
>--=AD=EC=A9l=B6l=A5=F3--
>Not to be rude, but your first mistake was attempting to=20
upgrade Win9x to
>XP.
>MSDE installed under Win9x is a completely different=20
animal than an
>installation on the NT style operating systems. With=20
Win9x there are no
>service applications so MSDE runs as a standard=20
application when the system
>starts up. When you upgrade your OS to XP there is no=20
magical conversion of
>the MSDE installation to it running as a service. Your=20
best bet is to backup
>your databases and then manually uninstall MSDE.=20
Microsoft has an article on
>how to do this at:
>http://support.microsoft.com/default.aspx?scid=3Dkb;en-
us;290991
>After uninstalling MSDE re-install it and restore your=20
databases.
>Jim
>"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in=20
message[vbcol=seagreen]
>news:OzBSSNkjEHA.1404@.TK2MSFTNGP09.phx.gbl...
home, after that, MSDE
>failure and i can't reinstall MSDE again, already call=20
microsoft support and[vbcol=seagreen]
>try something but no help at all.
newsgroup engine
>supports Post Alerts, Ratings, and Searching.
>
>.
>
I installed MSDE in WIN98 and then upgrade to WINXP home, after that, MSDE failure and i can't reinstall MSDE again, already call microsoft support and try something but no help at all.
John
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Not to be rude, but your first mistake was attempting to upgrade Win9x to
XP.
MSDE installed under Win9x is a completely different animal than an
installation on the NT style operating systems. With Win9x there are no
service applications so MSDE runs as a standard application when the system
starts up. When you upgrade your OS to XP there is no magical conversion of
the MSDE installation to it running as a service. Your best bet is to backup
your databases and then manually uninstall MSDE. Microsoft has an article on
how to do this at:
http://support.microsoft.com/default...b;en-us;290991
After uninstalling MSDE re-install it and restore your databases.
Jim
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:OzBSSNkjEHA.1404@.TK2MSFTNGP09.phx.gbl...
> Anyone can help?
> I installed MSDE in WIN98 and then upgrade to WINXP home, after that, MSDE
failure and i can't reinstall MSDE again, already call microsoft support and
try something but no help at all.
> John
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
|||Hi Jim,
Thanks for your advice, i will try it !!
John
>--=AD=EC=A9l=B6l=A5=F3--
>Not to be rude, but your first mistake was attempting to=20
upgrade Win9x to
>XP.
>MSDE installed under Win9x is a completely different=20
animal than an
>installation on the NT style operating systems. With=20
Win9x there are no
>service applications so MSDE runs as a standard=20
application when the system
>starts up. When you upgrade your OS to XP there is no=20
magical conversion of
>the MSDE installation to it running as a service. Your=20
best bet is to backup
>your databases and then manually uninstall MSDE.=20
Microsoft has an article on
>how to do this at:
>http://support.microsoft.com/default.aspx?scid=3Dkb;en-
us;290991
>After uninstalling MSDE re-install it and restore your=20
databases.
>Jim
>"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in=20
message[vbcol=seagreen]
>news:OzBSSNkjEHA.1404@.TK2MSFTNGP09.phx.gbl...
home, after that, MSDE
>failure and i can't reinstall MSDE again, already call=20
microsoft support and[vbcol=seagreen]
>try something but no help at all.
newsgroup engine
>supports Post Alerts, Ratings, and Searching.
>
>.
>
Subscribe to:
Posts (Atom)