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

msde 2000 and sql server

Hi group!
I am developing an application using MSDE 2000.
I made a Setup.exe by using Installshield tool.
in Installshield I add the msde2000.msm with named
instance. so msde2000 will be installed to the end client
machine.
my question is if the end client machine has SQL server
(for example version 2000, 7.5, 6.0), after my installtion
the sql server in end client machine is still OK?
I found the msde installtion will install dll file to
C:\Program Files\Microsoft SQL Server\80,if end client
machine has SQL server, the msde installtion will rewrite
C:\Program Files\Microsoft SQL Server\80.
thank?
yan
Hi Yan,
I'd strongly suggest you:
1. Modify the setup.ini file to have the settings you want for MSDE and to
install it with an instance name that is unique to you. (That will avoid any
clash with an existing installation)
2. Get the end-customer to run the ms-supplied setup for the MSDE before
installing your app.
Unfortunately, there are just way too many problems with auto-installing it
at present. These will be rectified with SQL Express in the future.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"ycjj" <yan@.mcr-sol.pic.melco.co.jp> wrote in message
news:061a01c49b8f$74866590$a301280a@.phx.gbl...
> Hi group!
> I am developing an application using MSDE 2000.
> I made a Setup.exe by using Installshield tool.
> in Installshield I add the msde2000.msm with named
> instance. so msde2000 will be installed to the end client
> machine.
> my question is if the end client machine has SQL server
> (for example version 2000, 7.5, 6.0), after my installtion
> the sql server in end client machine is still OK?
> I found the msde installtion will install dll file to
> C:\Program Files\Microsoft SQL Server\80,if end client
> machine has SQL server, the msde installtion will rewrite
> C:\Program Files\Microsoft SQL Server\80.
> thank?
> yan

MSDE 2000 & SQL Server 7 installed together?

Hi group!
I'm developing an application using Access/SQL Server.
The end client (government...) only has SQL server 7
installed and has not plans to upgrade in the development
timeframe.
I'd like to use SQL Server 2000 functions in my app. So
I'm wondering if I can reccomend an installation of MSDE
2000 alongside their SLQ server 7.
Is this technically possible?
If not, I'll have to rethink my design and do it in SQL
Server 7.
TIA
Andrew
hi Andrew,
"Andrew Webster" <andrew@.SPAM_ME_NOTwebster.org> ha scritto nel messaggio
news:042701c499fd$d7915ca0$a601280a@.phx.gbl...
> Hi group!
> I'm developing an application using Access/SQL Server.
> The end client (government...) only has SQL server 7
> installed and has not plans to upgrade in the development
> timeframe.
> I'd like to use SQL Server 2000 functions in my app. So
> I'm wondering if I can reccomend an installation of MSDE
> 2000 alongside their SLQ server 7.
> Is this technically possible?
> If not, I'll have to rethink my design and do it in SQL
> Server 7.
MSDE 2000 and MSDE 1.0, as long as SQL Server 7.0 and SQL Server 2000, and
relative mix, can coexiste on the same server...
the 7.0 code based server will be the default instance while the 2000 code
based server(s) have to be named instances.. up to 16 different isntances of
SQL Server 2000/MSDE 2000 can be (technically) hosted on the same sarver...
MDAC stack will be updated at 2.6 version (minimum requirement for SQL
Server 2000 RTM version), or better at 2.7.1 for service pack 3a level,
which I strongly recommend.
if you install MSDE 2000 over SQL Server 7.0, all the client tools of the
7.0 edition should be unusable as the COM binaries will be replaced with the
higher version, and only 2000 based tools will be available for management..
one caveat.. MSDE does not provide those tools (Enterprise Manager, Query
Analyzer and so on) but only the COM objects they rely on... so I really
have no idea (never tried myself) what the end position will be...
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
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
|||Thanks for that - I've now got access to a machine with SQL 7.0 on it, so I
can have a go at the installation and see how it works.
Andrew
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2qojtiF127domU1@.uni-berlin.de...
> hi Andrew,
> "Andrew Webster" <andrew@.SPAM_ME_NOTwebster.org> ha scritto nel messaggio
> news:042701c499fd$d7915ca0$a601280a@.phx.gbl...
> MSDE 2000 and MSDE 1.0, as long as SQL Server 7.0 and SQL Server 2000, and
> relative mix, can coexiste on the same server...
> the 7.0 code based server will be the default instance while the 2000 code
> based server(s) have to be named instances.. up to 16 different isntances
of
> SQL Server 2000/MSDE 2000 can be (technically) hosted on the same
sarver...
> MDAC stack will be updated at 2.6 version (minimum requirement for SQL
> Server 2000 RTM version), or better at 2.7.1 for service pack 3a level,
> which I strongly recommend.
> if you install MSDE 2000 over SQL Server 7.0, all the client tools of the
> 7.0 edition should be unusable as the COM binaries will be replaced with
the
> higher version, and only 2000 based tools will be available for
management..
> one caveat.. MSDE does not provide those tools (Enterprise Manager, Query
> Analyzer and so on) but only the COM objects they rely on... so I really
> have no idea (never tried myself) what the end position will be...
> --
> 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
> --
> 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
>

MSDE & SQL2000

I am developing a Crystal Reports App in VS2005 (VB). I was originally working on an XP machine with MSDE and stored procedures where it worked fine.

I then transferred the development to a Win2003 machine with SQL2000 and am now getting the following error;

Failed to open a rowset. Description: 'Get_Calls_By_MLO_Date' expects parameter '@.DT1' which was not supplied. Plus some other error detail.

Here is the SP.

CREATE PROCEDURE Get_Calls_By_MLO_By_Date
@.DT1 datetime,
@.DT2 datetime
AS
SELECT MLO, CallNo, DT, Type FROM Actions
WHERE dt >= @.DT1 AND dt <= @.DT2 AND ActionID=1ORDER BY MLO, DT
GO

If I transfer everything back to the XP machine it works fine.

Any ideas?

Thanks

Terry.

How did you call the stored procedure that causes the error?|||

Hi,

It's called from the Crystal Report object. The function below accepts 2 parameters; 1. The report viewer and 2. (optional) a hashtable with the key/value pairs being the parameter info e.g. Key=@.DT1, Value = 13/01/2006 12:00:01 AM

As I mentioned in the original post, this works fine on the XP box but not the Win2003. The are a number of reports; some accept parameters (all of which appear to fail with the same error) and others that don't, all of which work as expected. Other than the OS, and SQL as opposed to MSDE the only other differerence I can think of is the copy of VS2005.

Thanks.

Private Function LoadReport(ByVal ReportNameAs String, _ByVal ViewerAs CrystalDecisions.Windows.Forms.CrystalReportViewer, _Optional ByVal ParametersAs Hashtable =Nothing)As Boolean Dim rptAs New ReportDocumentDim pvCollAs New CrystalDecisions.Shared.ParameterValues' Objects used to set the proper database connection informationDim tbCurrentAs CrystalDecisions.CrystalReports.Engine.TableDim tliCurrentAs CrystalDecisions.Shared.TableLogOnInfoDim pdValAs New CrystalDecisions.Shared.ParameterDiscreteValueTry Dim appPathAs String = Application.ExecutablePath appPath = appPath.Substring(0, appPath.LastIndexOf("\") + 1)Dim fileExistsAs Boolean = false fileExists = My.Computer.FileSystem.FileExists(appPath &"Reports\" & ReportName)If fileExistsThen rpt.Load(appPath &"Reports\" & ReportName)Else MsgBox("Cannot locate report file", MsgBoxStyle.Critical,"Load Error")     pvColl =Nothing    pdVal =NothingExit Function End If For Each tbCurrentIn rpt.Database.Tables tliCurrent = tbCurrent.LogOnInfoWith tliCurrent.ConnectionInfo .ServerName = ServerName .UserID ="" .Password ="" .DatabaseName = My.Settings.DBName.ToStringEnd With tbCurrent.ApplyLogOnInfo(tliCurrent)Next tbCurrentIf Not IsNothing(Parameters)Then Dim myEnumAs IDictionaryEnumerator = Parameters.GetEnumeratorWhile myEnum.MoveNext pvColl.Clear() pdVal.Value = myEnum.Value pvColl.Add(pdVal) rpt.DataDefinition.ParameterFields(myEnum.Key).ApplyCurrentValues(pvColl)End While End If Viewer.ReportSource = rptCatch ExpAs LoadSaveReportException MsgBox("Report " & ReportName &" not found.", _ MsgBoxStyle.Critical,"Load Report Error")Catch ExpAs Exception MsgBox(Exp.Message, MsgBoxStyle.Critical,"General Error")Finally pvColl =Nothing pdVal =Nothing End Try End Function

|||

Thanks for the help. The problem is a crystal reports one and is detailed here

http://support.businessobjects.com/library/kbase/articles/c2017367.asp

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
>