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
Showing posts with label current. Show all posts
Showing posts with label current. Show all posts
Friday, March 30, 2012
Monday, March 19, 2012
MSDE Merge Replication (feasibility and licensing)
I am new to replication and have a couple of questions.
My requirement is to keep several (2 - 10) databases in sync. My current thinking is to use MSDE, along with merge replication. I have determined from the documentation that MSDE has the features and capabilities to fulfil the data storage and retrieval
requirments.
1) Is merge replication possible among a number of MSDE databases across a network (no SQL Server involved)
2) Do any licenses have to be purchased? The documentation is a little inconsistent on this point.
Thanks a lot.
1) yes, but MSDE is optimized for 8 concurrent workloads
2) check out this link for MSDE licensing information
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
"JW" <anonymous@.discussions.microsoft.com> wrote in message
news:F861246B-EBDA-4EEA-8CA0-6077C3F5DBCD@.microsoft.com...
> I am new to replication and have a couple of questions.
> My requirement is to keep several (2 - 10) databases in sync. My current
thinking is to use MSDE, along with merge replication. I have determined
from the documentation that MSDE has the features and capabilities to fulfil
the data storage and retrieval requirments.
> 1) Is merge replication possible among a number of MSDE databases across a
network (no SQL Server involved)
> 2) Do any licenses have to be purchased? The documentation is a little
inconsistent on this point.
> Thanks a lot.
|||I must admit that I've never tested this, but as far as I
recall MSDE is throttled at 5 connections.
Regards,
Paul Ibison
|||Thanks for the replies.
1) I think that it's the number of concurrent batches that chokes MSDE, not the number of connections.
From "The SQL Server 2000 Workload Governor" at http://msdn.microsoft.com/library/?u...asp?frame=true :
"Like all versions of SQL Server 2000, SQL Server 2000 Personal Edition and MSDE 2000 allow 32,767 connections to an instance of the database engine. There is no limit for the number of connections that can be executing operations at the same time. The on
ly effect of the workload governor is that it starts slowing down the database engine when more than eight operations are actively running at the same time."
2) Based on my research, it looks like no extra licensing is required if there is no connection to any of the 'regular' SQL Server editions:
From "HOW TO: Use Replication with SQL Server 2000 Desktop Engine (MSDE 2000)" at http://support.microsoft.com/4
"Licensing Issues
MSDE 2000 does not require any licensing when you use it in a stand-alone mode, but when you use it as part of a replication topology that involves regular SQL Server editions, if the server is in Per Seat mode as opposed to a Per Processor mode, each MSD
E 2000 Subscriber must have a client-access license (CAL).
For more information about SQL Server licensing, visit the following Microsoft Web site:
http://www.microsoft.com/sql/howtobuy/SQL2KLic.doc"
Again, thanks for your time.
Regards,
Joe
|||JW,
interesting. In the MS knowledgebase it mentions throttling after 5
concurrent connections:
MSDE 2000-Specific Limitations and Caveats
a.. MSDE 2000 limits the size of the database to 2 GB...
b.. The number of connections to MSDE 2000 is optimized for five
connections. This may affect the performance of replication if MSDE 2000 is
the Publisher and there are a enough Subscribers to the publication or if it
is a Subscriber to multiple publications.
see: http://support.microsoft.com/default...;en-us;Q324992
I have seen this 'limit' mentioned elsewhere, so the mentioning of 8 is
strange. I'll do some more research and see if we can get a definitive
answer.
Regards,
Paul Ibison
My requirement is to keep several (2 - 10) databases in sync. My current thinking is to use MSDE, along with merge replication. I have determined from the documentation that MSDE has the features and capabilities to fulfil the data storage and retrieval
requirments.
1) Is merge replication possible among a number of MSDE databases across a network (no SQL Server involved)
2) Do any licenses have to be purchased? The documentation is a little inconsistent on this point.
Thanks a lot.
1) yes, but MSDE is optimized for 8 concurrent workloads
2) check out this link for MSDE licensing information
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp
"JW" <anonymous@.discussions.microsoft.com> wrote in message
news:F861246B-EBDA-4EEA-8CA0-6077C3F5DBCD@.microsoft.com...
> I am new to replication and have a couple of questions.
> My requirement is to keep several (2 - 10) databases in sync. My current
thinking is to use MSDE, along with merge replication. I have determined
from the documentation that MSDE has the features and capabilities to fulfil
the data storage and retrieval requirments.
> 1) Is merge replication possible among a number of MSDE databases across a
network (no SQL Server involved)
> 2) Do any licenses have to be purchased? The documentation is a little
inconsistent on this point.
> Thanks a lot.
|||I must admit that I've never tested this, but as far as I
recall MSDE is throttled at 5 connections.
Regards,
Paul Ibison
|||Thanks for the replies.
1) I think that it's the number of concurrent batches that chokes MSDE, not the number of connections.
From "The SQL Server 2000 Workload Governor" at http://msdn.microsoft.com/library/?u...asp?frame=true :
"Like all versions of SQL Server 2000, SQL Server 2000 Personal Edition and MSDE 2000 allow 32,767 connections to an instance of the database engine. There is no limit for the number of connections that can be executing operations at the same time. The on
ly effect of the workload governor is that it starts slowing down the database engine when more than eight operations are actively running at the same time."
2) Based on my research, it looks like no extra licensing is required if there is no connection to any of the 'regular' SQL Server editions:
From "HOW TO: Use Replication with SQL Server 2000 Desktop Engine (MSDE 2000)" at http://support.microsoft.com/4
"Licensing Issues
MSDE 2000 does not require any licensing when you use it in a stand-alone mode, but when you use it as part of a replication topology that involves regular SQL Server editions, if the server is in Per Seat mode as opposed to a Per Processor mode, each MSD
E 2000 Subscriber must have a client-access license (CAL).
For more information about SQL Server licensing, visit the following Microsoft Web site:
http://www.microsoft.com/sql/howtobuy/SQL2KLic.doc"
Again, thanks for your time.
Regards,
Joe
|||JW,
interesting. In the MS knowledgebase it mentions throttling after 5
concurrent connections:
MSDE 2000-Specific Limitations and Caveats
a.. MSDE 2000 limits the size of the database to 2 GB...
b.. The number of connections to MSDE 2000 is optimized for five
connections. This may affect the performance of replication if MSDE 2000 is
the Publisher and there are a enough Subscribers to the publication or if it
is a Subscriber to multiple publications.
see: http://support.microsoft.com/default...;en-us;Q324992
I have seen this 'limit' mentioned elsewhere, so the mentioning of 8 is
strange. I'll do some more research and see if we can get a definitive
answer.
Regards,
Paul Ibison
Monday, March 12, 2012
MSDE Lockdown scripts
We are installing MSDE along with one of our applications.
But with the current security threats, we want to make sure
that the installed MSDE is secure. So is there any lock
down scripts available publicly that can be used for the same.
Thanks in Advance.
hi,
"Arunkumar Viswanathan" <anonymous@.discussions.microsoft.com> ha scritto nel
messaggio news:012101c4904c$0eea0af0$a401280a@.phx.gbl...
> We are installing MSDE along with one of our applications.
> But with the current security threats, we want to make sure
> that the installed MSDE is secure. So is there any lock
> down scripts available publicly that can be used for the same.
not that I'm aware of... anyway, MSDE installs by default disabling network
protocols and with Windows NT authentication only... you only have to set a
strong "sa" password...
this is the *standard*, and should be quite secure... but usually you will
need remote connections (which require TCP/IP or other preferred network
protocol to be enabled) ... if you do not need SQL Server authenticated
connections, you can go with the default "trusted" only...
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
|||Hi Andrea,
Thanks for replying. As you rightly said the we have to
provide a strong password to the sa user. But generally in
a stand alone MSDE installation some stored procedures are
given public previleges and that can cause problems with
advanced users. So if you of know of any lock down scripts
pls post the link here.
Thanks
Arunkumar
>--Original Message--
>not that I'm aware of... anyway, MSDE installs by default
disabling network
>protocols and with Windows NT authentication only... you
only have to set a
>strong "sa" password...
>this is the *standard*, and should be quite secure... but
usually you will
>need remote connections (which require TCP/IP or other
preferred network
>protocol to be enabled) ... if you do not need SQL Server
authenticated
>connections, you can go with the default "trusted" only...
>--
>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
>.
>
|||hi Arunkumar,
<anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:452d01c49052$8853d550$a601280a@.phx.gbl...
> Hi Andrea,
> Thanks for replying. As you rightly said the we have to
> provide a strong password to the sa user. But generally in
> a stand alone MSDE installation some stored procedures are
> given public previleges and that can cause problems with
> advanced users. So if you of know of any lock down scripts
> pls post the link here.
again... unfortunately I do not know one :-(
but, again, it all depends on what you want to secure...
if you mean system stored procedures, usually (at least the problematic,
like xp_cmdshell and so on) they are "protected" requiring sysadmins
privileges
on the other side, if you mena your own procedures, it' up to you to remove
"guest" permission to them =;-D
so I usually remove guest login and deny public involvement... and I do
manage privileges in user's groups...
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
But with the current security threats, we want to make sure
that the installed MSDE is secure. So is there any lock
down scripts available publicly that can be used for the same.
Thanks in Advance.
hi,
"Arunkumar Viswanathan" <anonymous@.discussions.microsoft.com> ha scritto nel
messaggio news:012101c4904c$0eea0af0$a401280a@.phx.gbl...
> We are installing MSDE along with one of our applications.
> But with the current security threats, we want to make sure
> that the installed MSDE is secure. So is there any lock
> down scripts available publicly that can be used for the same.
not that I'm aware of... anyway, MSDE installs by default disabling network
protocols and with Windows NT authentication only... you only have to set a
strong "sa" password...
this is the *standard*, and should be quite secure... but usually you will
need remote connections (which require TCP/IP or other preferred network
protocol to be enabled) ... if you do not need SQL Server authenticated
connections, you can go with the default "trusted" only...
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
|||Hi Andrea,
Thanks for replying. As you rightly said the we have to
provide a strong password to the sa user. But generally in
a stand alone MSDE installation some stored procedures are
given public previleges and that can cause problems with
advanced users. So if you of know of any lock down scripts
pls post the link here.
Thanks
Arunkumar
>--Original Message--
>not that I'm aware of... anyway, MSDE installs by default
disabling network
>protocols and with Windows NT authentication only... you
only have to set a
>strong "sa" password...
>this is the *standard*, and should be quite secure... but
usually you will
>need remote connections (which require TCP/IP or other
preferred network
>protocol to be enabled) ... if you do not need SQL Server
authenticated
>connections, you can go with the default "trusted" only...
>--
>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
>.
>
|||hi Arunkumar,
<anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:452d01c49052$8853d550$a601280a@.phx.gbl...
> Hi Andrea,
> Thanks for replying. As you rightly said the we have to
> provide a strong password to the sa user. But generally in
> a stand alone MSDE installation some stored procedures are
> given public previleges and that can cause problems with
> advanced users. So if you of know of any lock down scripts
> pls post the link here.
again... unfortunately I do not know one :-(
but, again, it all depends on what you want to secure...
if you mean system stored procedures, usually (at least the problematic,
like xp_cmdshell and so on) they are "protected" requiring sysadmins
privileges
on the other side, if you mena your own procedures, it' up to you to remove
"guest" permission to them =;-D
so I usually remove guest login and deny public involvement... and I do
manage privileges in user's groups...
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)