We have installed an application that usese MSDE as the database, no error m
essage during install process. When application is opened and attempts to c
onnect with the database we get the following message:
sql code = -1
sql db code = 10004
"SQL Error: unable to connect: SQL server is unavailable or does not
exist. unable to connect: sql server does not exist or network access
denied"
We can get to the database and view contents using ODBC and OSQL. The syste
m is Windows Server 2003 Small Business Server, and we are using MSDE releas
e A. Other software on the system that might create a problem (hints I've s
een on other forums) are Ba
ckupexe and Sharepoint.
We have checked all issues of access rights and security issues we can think
of but apparently have overlooked something. This is a pretty high priorit
y issue for us so if anyone can help we would certainly appreciate it!I know this may not help much, but if you have no problem connecting from
OSQL and other application, you might want to check with teh vendor of the
application and find out how the connection to SQL Server is made from the
application. This might help lead to you why the error is occurring.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql
Showing posts with label process. Show all posts
Showing posts with label process. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
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.
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
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.
Friday, March 23, 2012
MSDE 2000 Install Problems
I have been developing an application that uses MSDE 2000 as it's database.
In the process of testing/debugging my installation, I have run into an
interesting and very frustrating problem. MSDE now completely refuses to
install anymore! I cannot get the installer to install either as part of my
installer package using the MSDEBootstrap release candidate "or" by running
the MSDE setup from the command line.
I tried attaching the verbose log from my last command-line attempt, but
this newsgroup blocks my message due to size constraints. If anyone can
provide me any insight into how to resolve this, it would be much
appreciated. The error generated by the install is the ambiguous error
1603. The portion of the log which seems to contain the location where
things are goofin up follows:
MSI (s) (2C:08): Doing action:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B
Action start 8:35:54:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B.
MSI (s) (2C:08): Creating MSIHANDLE (49) of type 790542 for thread 3592
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
TempFolder is
C:\DOCUME~1\sbrodie\LOCALS~1\Temp\{689404D2-1C94-44B3-9203-BEC5594FDA7A}\
Loading extended custom action library
C:\DOCUME~1\sbrodie\LOCALS~1\Temp\{689404D2-1C94-44B3-9203-BEC5594FDA7A}\sql
cax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
Starting custom action SetPropSQLMSDEInstalled
FindSet for ProductCode <{689404D2-1C94-44B3-9203-BEC5594FDA7A}> returned 2
Setting SQLMSDEInstalled by MsiSetProperty returned 0
Setting SQLMSDESelected by MsiSetProperty returned 0
End SetPropSQLMSDEInstalled
Action ended 8:35:55:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B. Return value
1.
MSI (s) (2C:08): Doing action:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B
Action start 8:35:55:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B.
MSI (s) (2C:08): Creating MSIHANDLE (59) of type 790542 for thread 3592
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
Entering Function MyMsiEvaluateCondition
MsiEvaluateCondition for SQLMSDEInstalled returned TRUE
End Function MyMsiEvaluateCondition
Error reading setup parameters
Action ended 8:35:55:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. Return value 3.
Action ended 8:35:55: INSTALL. Return value 3.
MSI (s) (2C:08): Note: 1: 2262 2: Control 3: -2147287038
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir = C:\DMSF
Property(S): SqlProgramDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlInstanceName = DMSF
Property(S): SqlSa...
Property(S): VersionNT = 501
Property(S): ALLUSERS = 1
Property(S): ARPNOMODIFY = 1
Property(S): DefaultUIFont = Tahoma8
Property(S): INSTALLLEVEL = 3
Property(S): LIMITUI = 1
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductCode = {689404D2-1C94-44B3-9203-BEC5594FDA7A}
Property(S): ProductLanguage = 1033
Property(S): ProductName = Microsoft SQL Server Desktop Engine
Property(S): ProductVersion = 8.00.761
Property(S): MsiHiddenProperties = SqlSa...
Property(S): ProgramFilesFolder.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B =
C:\Program Files\
Property(S): StartupFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B =
C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): SystemFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B =
C:\WINDOWS\System32\
Property(S): SQLVersion.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 8.00.194
Property(S): SQLMSDEInstalled = 1
Property(S): SQLExitCode.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 1603
Regards
Shane Brodie
"Shane Brodie" <sbrodie@.deorkit.com> wrote in message
news:u5BCBXJIEHA.4052@.TK2MSFTNGP12.phx.gbl...
> I have been developing an application that uses MSDE 2000 as it's
database.
> In the process of testing/debugging my installation, I have run into an
> interesting and very frustrating problem. MSDE now completely refuses to
> install anymore! I cannot get the installer to install either as part of
my
> installer package using the MSDEBootstrap release candidate "or" by
running
> the MSDE setup from the command line.
>
You may want to try a manual removal of the SQL Server 2000 Desktop database
(MSDE), reboot then re-install.
http://www.support.microsoft.com/?id=320873
Steve
|||Thanks Steve:
Been there ... done that ... got the t-shirt. Following is a part of my
daily blog at work:
...
Frustration day. Had a bunch of problems with MSDE and the release candidate
installer used to install the database as part of a VS.Net project. For
whatever reason, the installer is refusing to install MSDE on my machine
even after performing an in-place update of Windows XP, uninstalling and
re-installing SQL Server tools and another instance of MSDE I am running and
performing an exhaustive filesystem and registry "search and destroy
mission" to remove any existing references to my database instance. BTW:
It would be really ... nice ... if Microsoft would post expected release
dates of the final release of "release candidate" software(give or take 6
months ; ) ).
Existing newsgroup postings report similar problems and the log files
generated by the Windows Installer and Event Viewer are somewhat less than
informative ...
In the meantime, I have managed to install an instance of MS SQL Server
using the official SQL Server 2000 Personal Edition CD so that I can
continue development while I fight with this issue. I am following up on the
MS newsgroups and elsewhere to see if there are permanent work-arounds/fixes
for this problem.
...
As well installation fails whether I use the generated installation from my
VS.Net solution or if I perform a command-line install of MSDE2000a.
Sorry about the double post ... Outlook Express complained on the size of
the message plus log (and I assumed that it meant it did not send ...) and
then sent it anyways.
Regards
Shane Brodie
In the process of testing/debugging my installation, I have run into an
interesting and very frustrating problem. MSDE now completely refuses to
install anymore! I cannot get the installer to install either as part of my
installer package using the MSDEBootstrap release candidate "or" by running
the MSDE setup from the command line.
I tried attaching the verbose log from my last command-line attempt, but
this newsgroup blocks my message due to size constraints. If anyone can
provide me any insight into how to resolve this, it would be much
appreciated. The error generated by the install is the ambiguous error
1603. The portion of the log which seems to contain the location where
things are goofin up follows:
MSI (s) (2C:08): Doing action:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B
Action start 8:35:54:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B.
MSI (s) (2C:08): Creating MSIHANDLE (49) of type 790542 for thread 3592
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
TempFolder is
C:\DOCUME~1\sbrodie\LOCALS~1\Temp\{689404D2-1C94-44B3-9203-BEC5594FDA7A}\
Loading extended custom action library
C:\DOCUME~1\sbrodie\LOCALS~1\Temp\{689404D2-1C94-44B3-9203-BEC5594FDA7A}\sql
cax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
Starting custom action SetPropSQLMSDEInstalled
FindSet for ProductCode <{689404D2-1C94-44B3-9203-BEC5594FDA7A}> returned 2
Setting SQLMSDEInstalled by MsiSetProperty returned 0
Setting SQLMSDESelected by MsiSetProperty returned 0
End SetPropSQLMSDEInstalled
Action ended 8:35:55:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B. Return value
1.
MSI (s) (2C:08): Doing action:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B
Action start 8:35:55:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B.
MSI (s) (2C:08): Creating MSIHANDLE (59) of type 790542 for thread 3592
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
Entering Function MyMsiEvaluateCondition
MsiEvaluateCondition for SQLMSDEInstalled returned TRUE
End Function MyMsiEvaluateCondition
Error reading setup parameters
Action ended 8:35:55:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. Return value 3.
Action ended 8:35:55: INSTALL. Return value 3.
MSI (s) (2C:08): Note: 1: 2262 2: Control 3: -2147287038
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir = C:\DMSF
Property(S): SqlProgramDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlInstanceName = DMSF
Property(S): SqlSa...
Property(S): VersionNT = 501
Property(S): ALLUSERS = 1
Property(S): ARPNOMODIFY = 1
Property(S): DefaultUIFont = Tahoma8
Property(S): INSTALLLEVEL = 3
Property(S): LIMITUI = 1
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductCode = {689404D2-1C94-44B3-9203-BEC5594FDA7A}
Property(S): ProductLanguage = 1033
Property(S): ProductName = Microsoft SQL Server Desktop Engine
Property(S): ProductVersion = 8.00.761
Property(S): MsiHiddenProperties = SqlSa...
Property(S): ProgramFilesFolder.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B =
C:\Program Files\
Property(S): StartupFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B =
C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): SystemFolder.2D02443E_7002_4C0B_ABC9_EAB2C064397B =
C:\WINDOWS\System32\
Property(S): SQLVersion.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 8.00.194
Property(S): SQLMSDEInstalled = 1
Property(S): SQLExitCode.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 1603
Regards
Shane Brodie
"Shane Brodie" <sbrodie@.deorkit.com> wrote in message
news:u5BCBXJIEHA.4052@.TK2MSFTNGP12.phx.gbl...
> I have been developing an application that uses MSDE 2000 as it's
database.
> In the process of testing/debugging my installation, I have run into an
> interesting and very frustrating problem. MSDE now completely refuses to
> install anymore! I cannot get the installer to install either as part of
my
> installer package using the MSDEBootstrap release candidate "or" by
running
> the MSDE setup from the command line.
>
You may want to try a manual removal of the SQL Server 2000 Desktop database
(MSDE), reboot then re-install.
http://www.support.microsoft.com/?id=320873
Steve
|||Thanks Steve:
Been there ... done that ... got the t-shirt. Following is a part of my
daily blog at work:
...
Frustration day. Had a bunch of problems with MSDE and the release candidate
installer used to install the database as part of a VS.Net project. For
whatever reason, the installer is refusing to install MSDE on my machine
even after performing an in-place update of Windows XP, uninstalling and
re-installing SQL Server tools and another instance of MSDE I am running and
performing an exhaustive filesystem and registry "search and destroy
mission" to remove any existing references to my database instance. BTW:
It would be really ... nice ... if Microsoft would post expected release
dates of the final release of "release candidate" software(give or take 6
months ; ) ).
Existing newsgroup postings report similar problems and the log files
generated by the Windows Installer and Event Viewer are somewhat less than
informative ...
In the meantime, I have managed to install an instance of MS SQL Server
using the official SQL Server 2000 Personal Edition CD so that I can
continue development while I fight with this issue. I am following up on the
MS newsgroups and elsewhere to see if there are permanent work-arounds/fixes
for this problem.
...
As well installation fails whether I use the generated installation from my
VS.Net solution or if I perform a command-line install of MSDE2000a.
Sorry about the double post ... Outlook Express complained on the size of
the message plus log (and I assumed that it meant it did not send ...) and
then sent it anyways.
Regards
Shane Brodie
Friday, March 9, 2012
MSDE - Insuring that process is up & running
I'm developing a C# application that runs against MSDE. How can I
programatically check whether MSDE is running and, if not, start it up
and set it to "auto-start"?
Thanks in advance!
hi,
"FinallyInSeattle" <lori.pearsall7@.gte.net> ha scritto nel messaggio
news:c987b316.0406241719.46bc434b@.posting.google.c om...
> I'm developing a C# application that runs against MSDE. How can I
> programatically check whether MSDE is running and, if not, start it up
> and set it to "auto-start"?
> Thanks in advance!
as regard then service running test, you coul'd use SQL-DMO object model...
when connecting, you can specify the .Start method instead of .Connect
metodh , and trap the resulting error , if any...
err -2147023840 indicates the instance is already running...
or trying connecti via Ado.Net, setting the connection timeout to a low
value, and, on error, sending a NET START command...
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
|||Thanks Andrea!!
"Andrea Montanari" wrote:
> hi,
> "FinallyInSeattle" <lori.pearsall7@.gte.net> ha scritto nel messaggio
> news:c987b316.0406241719.46bc434b@.posting.google.c om...
> as regard then service running test, you coul'd use SQL-DMO object model...
> when connecting, you can specify the .Start method instead of .Connect
> metodh , and trap the resulting error , if any...
> err -2147023840 indicates the instance is already running...
> or trying connecti via Ado.Net, setting the connection timeout to a low
> value, and, on error, sending a NET START command...
> --
> 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
>
programatically check whether MSDE is running and, if not, start it up
and set it to "auto-start"?
Thanks in advance!
hi,
"FinallyInSeattle" <lori.pearsall7@.gte.net> ha scritto nel messaggio
news:c987b316.0406241719.46bc434b@.posting.google.c om...
> I'm developing a C# application that runs against MSDE. How can I
> programatically check whether MSDE is running and, if not, start it up
> and set it to "auto-start"?
> Thanks in advance!
as regard then service running test, you coul'd use SQL-DMO object model...
when connecting, you can specify the .Start method instead of .Connect
metodh , and trap the resulting error , if any...
err -2147023840 indicates the instance is already running...
or trying connecti via Ado.Net, setting the connection timeout to a low
value, and, on error, sending a NET START command...
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
|||Thanks Andrea!!
"Andrea Montanari" wrote:
> hi,
> "FinallyInSeattle" <lori.pearsall7@.gte.net> ha scritto nel messaggio
> news:c987b316.0406241719.46bc434b@.posting.google.c om...
> as regard then service running test, you coul'd use SQL-DMO object model...
> when connecting, you can specify the .Start method instead of .Connect
> metodh , and trap the resulting error , if any...
> err -2147023840 indicates the instance is already running...
> or trying connecti via Ado.Net, setting the connection timeout to a low
> value, and, on error, sending a NET START command...
> --
> 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
>
Wednesday, March 7, 2012
MSDB up to 2GB due to DTA
I noticed my MSDB database is up over 2GB. Most of the data is in
DTA_tuninglog. Is there a process to purge this data? Can I simply delete
all the rows or will that cause an inconsistency with another table?
Thanks
Ron
Hi Ron,
I am not sure what version of the server you have running, however check
this link out as I think it may help you clean up the database:
http://support.microsoft.com/kb/899634
Take care.
~lb
"Ron" wrote:
> I noticed my MSDB database is up over 2GB. Most of the data is in
> DTA_tuninglog. Is there a process to purge this data? Can I simply delete
> all the rows or will that cause an inconsistency with another table?
> Thanks
> Ron
DTA_tuninglog. Is there a process to purge this data? Can I simply delete
all the rows or will that cause an inconsistency with another table?
Thanks
Ron
Hi Ron,
I am not sure what version of the server you have running, however check
this link out as I think it may help you clean up the database:
http://support.microsoft.com/kb/899634
Take care.
~lb
"Ron" wrote:
> I noticed my MSDB database is up over 2GB. Most of the data is in
> DTA_tuninglog. Is there a process to purge this data? Can I simply delete
> all the rows or will that cause an inconsistency with another table?
> Thanks
> Ron
MSDB up to 2GB due to DTA
I noticed my MSDB database is up over 2GB. Most of the data is in
DTA_tuninglog. Is there a process to purge this data? Can I simply delete
all the rows or will that cause an inconsistency with another table?
Thanks
RonHi Ron,
I am not sure what version of the server you have running, however check
this link out as I think it may help you clean up the database:
http://support.microsoft.com/kb/899634
Take care.
--
~lb
"Ron" wrote:
> I noticed my MSDB database is up over 2GB. Most of the data is in
> DTA_tuninglog. Is there a process to purge this data? Can I simply delete
> all the rows or will that cause an inconsistency with another table?
> Thanks
> Ron
DTA_tuninglog. Is there a process to purge this data? Can I simply delete
all the rows or will that cause an inconsistency with another table?
Thanks
RonHi Ron,
I am not sure what version of the server you have running, however check
this link out as I think it may help you clean up the database:
http://support.microsoft.com/kb/899634
Take care.
--
~lb
"Ron" wrote:
> I noticed my MSDB database is up over 2GB. Most of the data is in
> DTA_tuninglog. Is there a process to purge this data? Can I simply delete
> all the rows or will that cause an inconsistency with another table?
> Thanks
> Ron
Subscribe to:
Posts (Atom)