MSDE 2ksp3a TO SQL Server 2000, why is upgrade option disabled?

Hi,
I have latest version of MSDE on my win xp machine, I had installed a named version msde using the microsoft bootstrapper along with my application. During installation I had specified the datadir to be something like c:\program files\MyApp\Data
So far so good.
Now I am trying to install SQL Server 2000 dev edition on my computer and was hoping to upgrade this named instance of MSDE, but the upgrade option is disabled. All I can click on is "Create a new instance of SQL Server, or install Client Tools" and "Adv
anced options". Why is that. What am I missing. I read many times that upgrading named instance shouldn't be a problem.
I have to figure this out so that in future my client's can upgrade our MSDE named instance to SQL Server named instance if they need to..
Thanks
dev
correction, I had installed msde using the latest sql2ksp3 exe from microsoft.
thanks
dev
|||You can't upgrade MSDE to Developer Edition, you can only upgrade to SQL
Server 2000 Enterprise Edition or SQL Server 2000 Standard Edition.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:F366A797-A10F-4EAE-8AD7-1BC89ED470C4@.microsoft.com...
> Hi,
> I have latest version of MSDE on my win xp machine, I had installed a
named version msde using the microsoft bootstrapper along with my
application. During installation I had specified the datadir to be
something like c:\program files\MyApp\Data
> So far so good.
> Now I am trying to install SQL Server 2000 dev edition on my computer and
was hoping to upgrade this named instance of MSDE, but the upgrade option is
disabled. All I can click on is "Create a new instance of SQL Server, or
install Client Tools" and "Advanced options". Why is that. What am I
missing. I read many times that upgrading named instance shouldn't be a
problem.
> I have to figure this out so that in future my client's can upgrade our
MSDE named instance to SQL Server named instance if they need to..
> Thanks
> dev
>
|||Jasper thanks for the reply. Where can I find the document which states MSDE can be upgraded to which versions.
Does that mean that my client will have to invest in a server (NT 4.0 Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000 Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
thanks
dev
|||got it, thanks
http://support.microsoft.com/default...b;en-us;823462
|||They'll need a server operating system e.g. Windows 2000 Server or Windows
2003 Standard to install SQL2000 Standard
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:3F461785-F5A1-491F-9A4E-8ED5462409AE@.microsoft.com...
> Jasper thanks for the reply. Where can I find the document which states
MSDE can be upgraded to which versions.
> Does that mean that my client will have to invest in a server (NT 4.0
Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000
Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
> thanks
> dev

MSDE 2ksp3a TO SQL Server 2000, why is upgrade option disabled?

Hi
I have latest version of MSDE on my win xp machine, I had installed a named version msde using the microsoft bootstrapper along with my application. During installation I had specified the datadir to be something like c:\program files\MyApp\Dat
So far so good
Now I am trying to install SQL Server 2000 dev edition on my computer and was hoping to upgrade this named instance of MSDE, but the upgrade option is disabled. All I can click on is "Create a new instance of SQL Server, or install Client Tools" and "Advanced options". Why is that. What am I missing. I read many times that upgrading named instance shouldn't be a problem
I have to figure this out so that in future my client's can upgrade our MSDE named instance to SQL Server named instance if they need to.
Thank
deYou can't upgrade MSDE to Developer Edition, you can only upgrade to SQL
Server 2000 Enterprise Edition or SQL Server 2000 Standard Edition.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:F366A797-A10F-4EAE-8AD7-1BC89ED470C4@.microsoft.com...
> Hi,
> I have latest version of MSDE on my win xp machine, I had installed a
named version msde using the microsoft bootstrapper along with my
application. During installation I had specified the datadir to be
something like c:\program files\MyApp\Data
> So far so good.
> Now I am trying to install SQL Server 2000 dev edition on my computer and
was hoping to upgrade this named instance of MSDE, but the upgrade option is
disabled. All I can click on is "Create a new instance of SQL Server, or
install Client Tools" and "Advanced options". Why is that. What am I
missing. I read many times that upgrading named instance shouldn't be a
problem.
> I have to figure this out so that in future my client's can upgrade our
MSDE named instance to SQL Server named instance if they need to..
> Thanks
> dev
>|||Jasper thanks for the reply. Where can I find the document which states MSDE can be upgraded to which versions.
Does that mean that my client will have to invest in a server (NT 4.0 Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000 Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
thank
dev|||got it, thanks
http://support.microsoft.com/default.aspx?scid=kb;en-us;823462|||They'll need a server operating system e.g. Windows 2000 Server or Windows
2003 Standard to install SQL2000 Standard
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:3F461785-F5A1-491F-9A4E-8ED5462409AE@.microsoft.com...
> Jasper thanks for the reply. Where can I find the document which states
MSDE can be upgraded to which versions.
> Does that mean that my client will have to invest in a server (NT 4.0
Server OR NT 4.0 Enterprise Server OR Windows 2000 server OR Windows 2000
Advanced Server..) if they wish to upgrade from MSDE to SQL Server...
> thanks
> dev

msde 2000 sp3 install problem on win 2000

server. I am building an installshield package. During this process I must install to win 2000, xp pro etc, at home on my 2000 server I had hell of a time installing the msde. I have tried the msde 2000 sp3 patch as well. The installation rolls back after it is almost done. the log won't tell me anything meaningful. Is there any secret to msde on 2000 severs? I one time managed to install the server after succesfullu monkeying with the security profiles on the server, now it is uninstalled but despite the profile set correctlty I can't install? I need some help FAST!!!
The xp works like a charm.
I have attached the log...so if someone is an expert maybe can shed the ligh for me...Log file is not attached.|||msde setup has a bug - it needs upper case machine id for the network (I wonder if there is a workaround since changing my machine name is not that trivial - I am a cable broadband user.)|||Where did you find out about the upper case machine name - do you have a link ?|||Originally posted by rnealejr
Where did you find out about the upper case machine name - do you have a link ?
? if(document.domain.indexOf('.microsoft.com') > 0) document.domain = 'support.microsoft.com';

Home Search FAQs Downloads Newsgroups Customer Service

Microsoft Knowledge Base Article - 285100

Comments?
Provide us with feedback on this article

Support Centers
Small Business Server
SQL Server

Other Support Options
Contact Microsoft
Phone Numbers, Support Options and Pricing, Online Help, and more.

Customer Service
For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.

Newsgroups
Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.


Page Options
Send
Print



FIX: Installation Fails When Windows Computer Name Is Mixed or Lowercase
View products that this article applies to.
This article was previously published under Q285100
BUG #: 351711(SQL2000)
SYMPTOMS
Connection attempts over the shared memory network library fail on a server where GetComputerName returns a lower or mixed case server name.

When the shared memory connection attempt fails the SQL Server 2000 network library attempts to connect over an alternate protocol.

When you install any edition of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) on a computer whose name is all lowercase or mixed case, Setup may fail, and you receive one of the following messages:

For MSDE 2000:

Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.
For SQL Server 2000:

Setup failed to configure the server. Refer to the server error logs and sqlstp.log for more information.
CAUSE
GetComputerName is used to obtain the local computer name. The client network library component (DBMSLPCn.dll) converts the name to all upper case. The server network library component (SSMSLPCn.dll) leaves the name as returned.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
File name Platform
-------

SSMSLPCn323 Intel

The following file is available for download from the Microsoft Download Center:

SSMSLPCn323.exe

Release Date: JAN-22-2001

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How To Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

The SSMSLPCn323.exe file contains the following files:

File name Size
EULA.txt 2 KB
Readme.txt 1 KB
SSmsLPCn.dll 29 KB
SSmsLPCn.pdb 73 KB
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

WORKAROUND
To work around this problem, change the computer name to all uppercase characters.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
The failure is prohibitive to a SQL Server 2000 setup. A SQL Server 2000 setup prevents external connections by only allowing the shared network library connections.

If a shared memory connection can not be established, the setup fails when it attempts to configure the SQL Server server.

For SQL Server 2000:

The Sqlstp.log file contains an error message similar to:

2:44:57 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINNT\sqlstp.log" -dbdebug -I MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 262404 -U sa -P
Starting Service ...
SQL_Latin1_General_CP1_CI_AS -m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=MyServer;UID=sa;PWD=;database=maste r [Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
In the same Sqlstp.log file you can verify the naming failure by locating the following at the top of the log file:
12:30:08 Name = MYSERVER, Type = 0x1
12:30:08 ComputerName: MyServer

For MSDE 2000:

Run the following command so the installation does not roll back upon failure:
setup.exe /DISABLEROLLBACK=1 /L*v C:\temp\msdesetup.log

You must run this code so that the Cnfgsvr.out file can be collected. Using the /L*v switch enables verbose logging for MSDE 2000 Setup.

After the MSDE 2000 installation fails, when you review the contents of the Cnfgsvr.out file, you see an error message similar to the following:

Starting Service ...

SQL_Latin1_General_CP1_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=MyServer;UID=sa;PWD=;database=maste r

[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
The naming failure can be located from the server parameter. The Msdesetup.log file has an entry similar to the following:
ComputerName =MyServer

The information in this article applies to:
Microsoft SQL Server 2000 (all editions)
Microsoft SQL Server 2000 Desktop Engine (MSDE)
Last Reviewed: 11/3/2003 (4.0)
Keywords: kbBug kbfix kbQFE KB285100 kbAudDeveloper






Contact Us

? 2003 Microsoft Corporation. All rights reserved. Terms of use Security & Privacy Accessibility
function thisLoad(){ setcookieval("SITE","GN"); gsfxUpLevel(); g_reSupportedHostnames = new RegExp(".msn.com$|.passport.com$|.xbox.com$|.microsoft.com $|.microsoft.cz$|.msbpn.com$|.microsoft.co.*", "i"); ForeignLink_Hookup(true);LogHit('http://c.microsoft.com/trans_pixel.asp?TYPE=SSPV&SOURCE=SUPPORT&URI=/GN/EN-US/kb_en-us_285100&GUID=1F4FC18C-F71E-47fb-8FC9-612F8EE59C61&R='); } function thisUnload(){ ; }|||The fix is included in the article - do you download the fix ?|||Originally posted by rnealejr
The fix is included in the article - do you download the fix ?
Yes.
The problem is that I do not know how to update the CAB file and I can't even find reference to SSmsLPCn.pdb - I found the dll but I have not replace it yet in the CAB.
I found it incomprehansible that there is this bug and MSFT can NOT provide a decent fix only this weird one that you need to manually update dll's and fix THEIR setup. I have yet to find a reference to fix an existing setup distributable.|||If you follow the instructions in the readme.txt, you should be fine.

MSDE 2000 problems with linked server

I have set up several servers with MSDE 2000 sp4, have created tables in
these databases, can access, read, write data to the database through win sql
and asp. I have set up a linked server to an oracle database and created a
linkedsrvlogin. I can select data from my oracle database throught SQL using
the linked server. All of my servers are working fine except one. Onne
particular server is taking an extrememly long time to retrive certain data.
For example, I have one server that can get 31000 rows from my linked server
in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
rows from the same table.
Any ideas? Its driving me crazy!!!
Hi Lloyd
Have you tried adding a host file entry to the oracle server on the machine
which is slower than the others, it's a stab in the dark but your one machine
could be talking longer to resolve the name of the oracle db.
Regards
charl
http://www.sqlserver.co.za
"Lloyd Harrison" wrote:

> I have set up several servers with MSDE 2000 sp4, have created tables in
> these databases, can access, read, write data to the database through win sql
> and asp. I have set up a linked server to an oracle database and created a
> linkedsrvlogin. I can select data from my oracle database throught SQL using
> the linked server. All of my servers are working fine except one. Onne
> particular server is taking an extrememly long time to retrive certain data.
> For example, I have one server that can get 31000 rows from my linked server
> in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
> rows from the same table.
> Any ideas? Its driving me crazy!!!

MSDE 2000 problems with linked server

I have set up several servers with MSDE 2000 sp4, have created tables in
these databases, can access, read, write data to the database through win sql
and asp. I have set up a linked server to an oracle database and created a
linkedsrvlogin. I can select data from my oracle database throught SQL using
the linked server. All of my servers are working fine except one. Onne
particular server is taking an extrememly long time to retrive certain data.
For example, I have one server that can get 31000 rows from my linked server
in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
rows from the same table.
Any ideas? Its driving me crazy!!!Hi Lloyd
Have you tried adding a host file entry to the oracle server on the machine
which is slower than the others, it's a stab in the dark but your one machine
could be talking longer to resolve the name of the oracle db.
Regards
charl
http://www.sqlserver.co.za
"Lloyd Harrison" wrote:
> I have set up several servers with MSDE 2000 sp4, have created tables in
> these databases, can access, read, write data to the database through win sql
> and asp. I have set up a linked server to an oracle database and created a
> linkedsrvlogin. I can select data from my oracle database throught SQL using
> the linked server. All of my servers are working fine except one. Onne
> particular server is taking an extrememly long time to retrive certain data.
> For example, I have one server that can get 31000 rows from my linked server
> in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
> rows from the same table.
> Any ideas? Its driving me crazy!!!

MSDE 2000 problems with linked server

I have set up several servers with MSDE 2000 sp4, have created tables in
these databases, can access, read, write data to the database through win sq
l
and asp. I have set up a linked server to an oracle database and created a
linkedsrvlogin. I can select data from my oracle database throught SQL usin
g
the linked server. All of my servers are working fine except one. Onne
particular server is taking an extrememly long time to retrive certain data.
For example, I have one server that can get 31000 rows from my linked server
in 14 seconds, using anohter server, it takes almost 3 mins to get back 773
rows from the same table.
Any ideas? Its driving me crazy!!!Hi Lloyd
Have you tried adding a host file entry to the oracle server on the machine
which is slower than the others, it's a stab in the dark but your one machin
e
could be talking longer to resolve the name of the oracle db.
Regards
charl
http://www.sqlserver.co.za
"Lloyd Harrison" wrote:

> I have set up several servers with MSDE 2000 sp4, have created tables in
> these databases, can access, read, write data to the database through win
sql
> and asp. I have set up a linked server to an oracle database and created a
> linkedsrvlogin. I can select data from my oracle database throught SQL us
ing
> the linked server. All of my servers are working fine except one. Onne
> particular server is taking an extrememly long time to retrive certain dat
a.
> For example, I have one server that can get 31000 rows from my linked serv
er
> in 14 seconds, using anohter server, it takes almost 3 mins to get back 77
3
> rows from the same table.
> Any ideas? Its driving me crazy!!!

MSDE 2000 Installation Fails

I am trying to install MSDE 2000 on my WIN XP Professional machine. I have
installed it previously and uninstalled it. Now I am trying to reinstall.
Here is the error message I am receiving.
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action SkuIt
MSI (s) (8C:80) [09:58:32:977]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (8C:80) [09:58:32:977]: Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (8C:D8) [09:58:33:007]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI6C.tmp, Entrypoint: ConfigServer
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
-V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
MSI (c) (F0:E8) [09:58:59:656]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (8C!B4) [09:59:09:019]: Product: Microsoft SQL Server Desktop Engine
-- Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
Action ended 9:59:09: InstallFinalize. Re
Mike Bacher
IST Computer Technician
"Mike Bacher" wrote:

> I am trying to install MSDE 2000 on my WIN XP Professional machine. I have
> installed it previously and uninstalled it. Now I am trying to reinstall.
> Here is the error message I am receiving.
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action SkuIt
> MSI (s) (8C:80) [09:58:32:977]: Executing op:
> ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
> MSI (s) (8C:80) [09:58:32:977]: Executing op:
> CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
> MSI (s) (8C:D8) [09:58:33:007]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI6C.tmp, Entrypoint: ConfigServer
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action ConfigServer
> Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe
> -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "SQL_Latin1_General_CP1_CI_AS""
> MSI (c) (F0:E8) [09:58:59:656]: Font created. Charset: Req=0, Ret=0, Font:
> Req=MS Shell Dlg, Ret=MS Shell Dlg
> Setup failed to configure the server. Refer to the server error logs and
> setup error logs for more information.
> MSI (s) (8C!B4) [09:59:09:019]: Product: Microsoft SQL Server Desktop Engine
> -- Setup failed to configure the server. Refer to the server error logs and
> setup error logs for more information.
> Action ended 9:59:09: InstallFinalize. Re
> --
> Mike Bacher
> IST Computer Technician
Also here is what my cnfgsvr tells me:
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=HPIST098;UID=sa;PWD=;database=maste r
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
driver={sql server};server=HPIST098;UID=sa;PWD=;database=maste r
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
driver={sql server};server=HPIST098;UID=sa;PWD=;database=maste r
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
SQL Server configuration failed.

MSDE 2000 install on SQL 2000

Hello,
I have installed MSDE 2000 on Win Server 2003 with instance name brprof,
there SQL Server 2000 already installed as a local instance named SBGBHO.
Now, I registered my new MSDE 2000 on enterprise manager, registration done
successfully, but it display following error
LOGIN FAILED FOR USER SA : REASON NOT ASSOCIATED WITH TRUSTED SQL SERVER
CONNECTION
HARSHA.
hi Harsha,
Harsha Shah wrote:
> Hello,
> I have installed MSDE 2000 on Win Server 2003 with instance name
> brprof, there SQL Server 2000 already installed as a local instance
> named SBGBHO. Now, I registered my new MSDE 2000 on enterprise
> manager, registration done successfully, but it display following
> error
> LOGIN FAILED FOR USER SA : REASON NOT ASSOCIATED WITH TRUSTED SQL
> SERVER CONNECTION
MSDE installs by default only allowing trusted WinNT connections... you can
change this behavior, allowing standard SQL Server connection at install
time providing the
SECURITYMODE=SQL
parameter to the setup.exe boostrap installer, or later accessing the
windows registry, as described in
http://support.microsoft.com/default...b;en-us;285097
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

Hi
Trying to install Microsoft SQL Server 2000 Service Pack 4 on Win XP machine.
MSDE 2000 Sp3 already installed on D: drive, instance name= db1
In enterprise manager the db appears as ABC-111\DB1
ABC-111 is the name of the machine
I am using mixed authentication mode.
After reading the help I came up with this to install sp4:
setup /upgradesp sqlrun instancename="db1" securitymode=sql upgradeuser=sa
upgradepwd=sapw /L*v C:\MSDELog.log
I have also tried having instancename="ABC-111\DB1" but always the same error:
This product is not installed. Check is a appropriate instance of MSDE is
installed.
Now, note that the MSDE is installed here on my machine:
D:\Program Files\MSDE\MSSQL$DB1
Could that possible affect this?
I noticed when I looked in the registry that I did not find what the readme
file described, still, the database has been running smoothly for months...
Any hints somebody?
gst Valgar wrote:
> Hi
> Trying to install Microsoft SQL Server 2000 Service Pack 4 on Win XP
> machine. MSDE 2000 Sp3 already installed on D: drive, instance name=
> db1
> In enterprise manager the db appears as ABC-111\DB1
> ABC-111 is the name of the machine
> I am using mixed authentication mode.
> After reading the help I came up with this to install sp4:
> --
> setup /upgradesp sqlrun instancename="db1" securitymode=sql
> upgradeuser=sa upgradepwd=sapw /L*v C:\MSDELog.log
try setup /upgradesp sqlrun instancename=db1 securitymode=sql upgradeuser=sa
upgradepwd=sapw /L*v C:\MSDELog.log
without quotes...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||The error pervails...
"Andrea Montanari" wrote:

> ágúst Valgare wrote:
> try setup /upgradesp sqlrun instancename=db1 securitymode=sql upgradeuser=sa
> upgradepwd=sapw /L*v C:\MSDELog.log
> without quotes...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||Sorry, my mistake, this seems to work, thank you!
"ágúst Valgare" wrote:
[vbcol=seagreen]
> The error pervails...
> "Andrea Montanari" wrote:

msdb is Suspect

Is am running SQL 2000 SP3 on a Win 2000 box.
My msdb is marked suspet. I ran sp_resetstatus and restarted SQL and
the dB is still suspect.
I found an article that recommends...
One approach would be to drop & recreate the msdb databases (see
instmsdb.sql and instserv.sql in the c:\mssql\install directory of your
sqlserver install). You would lose backup/restore histories, all
operators, scheduled tasks, etc. but would get it back up and running.
Is this the only solution? Is there a way to do this without loosing
my backup history?
TIA,
Larry...
Paul,
You are the man!!! This did the trick.
As always, thanks for your help!!!!
Larry...