I need a better installation procedure for my software, so I wanted to merge
the MSDE install into the main one. At the moment the Setup has been built
by a third part developer, who use Installshiled.
Problem is, he doesn't know which version of Installshield he needs. Someone
can give me a hint?
On Thu, 1 Jul 2004 16:18:40 +0200, Drizzt <drizzt.du@.libero.it> wrote:
> I need a better installation procedure for my software, so I wanted to
> merge
> the MSDE install into the main one. At the moment the Setup has been
> built
> by a third part developer, who use Installshiled.
> Problem is, he doesn't know which version of Installshield he needs.
> Someone can give me a hint?
From what I read, InstallShield 7 should be alright; maybe even 6.
Not related to MSDE, I am struggling with it, though: I am unable to
create simple Upgrade packages that replace a couple of files in an
installation. something that InnoSetup and InstallShield 5 do perfectly
well.
Stefan
|||When I last spoke to them, the installshield guys didn't have the bootstrapper out for MSDE. They still had the merge modules but be warned microsoft does not want you to continue that route. I even spoke with WISE Solutions and they also mentioned that
they were working on replacing the merge module for MSDE.. so something to keep in mind.
Thanks
dev
"Stefan M. Huber" wrote:
> On Thu, 1 Jul 2004 16:18:40 +0200, Drizzt <drizzt.du@.libero.it> wrote:
>
> From what I read, InstallShield 7 should be alright; maybe even 6.
> Not related to MSDE, I am struggling with it, though: I am unable to
> create simple Upgrade packages that replace a couple of files in an
> installation. something that InnoSetup and InstallShield 5 do perfectly
> well.
> Stefan
>
|||"dev_kh" <devkh@.discussions.microsoft.com> ha scritto nel messaggio
news:3014BFB6-1C09-49FB-BA4E-C21475CDD808@.microsoft.com...
> When I last spoke to them, the installshield guys didn't
> have the bootstrapper out for MSDE. They still had the merge
> modules but be warned microsoft does not want you to continue
> that route. I even spoke with WISE Solutions and they also mentioned
> that they were working on replacing the merge module for MSDE.. so
something to keep in mind.
Sorry, I got lost.
Our product must be a self-easy-installing one. I have no experience about
Installations packages, and the (external)guy who must build it needs
directions from me, as he have never installed MSDE before.
We need a tight integration between the two -installshield and MSDE- 'cause
in case of errors we need the installation to halt and report the error,
while now it simply goes on...
So, is there a simply solution? What are the methods commonly used for this?
Sorry to bother, but I really have no clues...
|||| So, is there a simply solution? What are the methods commonly used for this?
I plan on using InnoSetup. I have been using it for over a year - love it. I
have not used it for MSDE, but I plan to.
<quote>
Yes, we now know how to. But it has taken a *LOT* of effort to
integrate it into InnoSetup in such a way that it:
* Checks the existence of an earlier MSDE installation
* If found check if it was done from our software
* If not, install a new instance using Microsoft setup
* Make sure to use the correct MSI file during install
* Make sure to set all install parameters correct
* Start the MSDE after install
* Connect to MSDE and install database
* Make sure it works on all NT platforms (big problems on NT4)
* etc etc etc
We have probably spent one man-moth on this task alone... Bo
</quote>
http://fox.wikis.com/wc.dll?Wiki~Inn...ScriptMSDE~VFP
Carl K
|||So, do you have a workable solution for installing an app and MSDE or not?
TIA,
Paul
"Carl Karsten" <carl@.personnelware.com> wrote in message
news:%23dnKozoYEHA.3988@.tk2msftngp13.phx.gbl...
> | So, is there a simply solution? What are the methods commonly used for
this?
> I plan on using InnoSetup. I have been using it for over a year - love
it. I
> have not used it for MSDE, but I plan to.
> <quote>
> Yes, we now know how to. But it has taken a *LOT* of effort to
> integrate it into InnoSetup in such a way that it:
> * Checks the existence of an earlier MSDE installation
> * If found check if it was done from our software
> * If not, install a new instance using Microsoft setup
> * Make sure to use the correct MSI file during install
> * Make sure to set all install parameters correct
> * Start the MSDE after install
> * Connect to MSDE and install database
> * Make sure it works on all NT platforms (big problems on NT4)
> * etc etc etc
> We have probably spent one man-moth on this task alone... Bo
> </quote>
> http://fox.wikis.com/wc.dll?Wiki~Inn...ScriptMSDE~VFP
> Carl K
>
|||Personally, no.
If the Inno guys say it will fly, I have no reason to doubt them. They aren't
trying to sell me something - the beauty of open source software.
Carl K
"Paul McTeigue" <paul_mcteigue@.msn.com> wrote in message
news:%23vGPGesYEHA.2816@.TK2MSFTNGP11.phx.gbl...
| So, do you have a workable solution for installing an app and MSDE or not?
|
| TIA,
| Paul
|
| "Carl Karsten" <carl@.personnelware.com> wrote in message
| news:%23dnKozoYEHA.3988@.tk2msftngp13.phx.gbl...
| >
| > | So, is there a simply solution? What are the methods commonly used for
| this?
| >
| > I plan on using InnoSetup. I have been using it for over a year - love
| it. I
| > have not used it for MSDE, but I plan to.
| >
| > <quote>
| > Yes, we now know how to. But it has taken a *LOT* of effort to
| > integrate it into InnoSetup in such a way that it:
| > * Checks the existence of an earlier MSDE installation
| > * If found check if it was done from our software
| > * If not, install a new instance using Microsoft setup
| > * Make sure to use the correct MSI file during install
| > * Make sure to set all install parameters correct
| > * Start the MSDE after install
| > * Connect to MSDE and install database
| > * Make sure it works on all NT platforms (big problems on NT4)
| > * etc etc etc
| >
| > We have probably spent one man-moth on this task alone... Bo
| > </quote>
| >
| > http://fox.wikis.com/wc.dll?Wiki~Inn...ScriptMSDE~VFP
| >
| > Carl K
| >
|
|
sql
Showing posts with label install. Show all posts
Showing posts with label install. Show all posts
Friday, March 30, 2012
MSDE and Enterprise Manager
I have just installed (new clean install) of MSDE 3a. On another machine I have enterprise manager, and I thought I would be able to access it, but when I try to register it in EM it gives me the following error: SERVERNAME - SQL Server does not exist or access denied, Connection Open(Connect(). I have done this in the past with no problem. Did I forget a parameter on the install of 3a to allow other machines to access or do I have some other security issue?Depends on the configuration of MSDE. If you have enabled (using sapwd flag on setup.exe) SQL authentication, you can authenticate with these credentials. However, I did not try to connect to an MSDE instance running on another box with Enterprise Manager yet. But AFAIK, SQL auth should work fine in this case.|||I did configure it for SQL authentication.sql
MSDE and DDL error
I have recently set up MSDE through a SharePoint services
install. I added a database, but when I go to add a table
through Visual Studio or osql I get the error "ADO error:
DDL statement is not allowed." I have tried to modify the
DDL settings in my database through >> exec sp_dboption
mydatabase, "ddl in tran", true <<, but "ddl in tran" is
not a recognized option any longer. Anyone know a
workaround on this? THANKS>Check your MDAC version
Try to update it.
Regards
---
All information provided above AS IS.
"Stephen Haiman" <shaiman@.ctt-inc.com> wrote in message
news:115501c3a2ea$88b9a2a0$a301280a@.phx.gbl...
> I have recently set up MSDE through a SharePoint services
> install. I added a database, but when I go to add a table
> through Visual Studio or osql I get the error "ADO error:
> DDL statement is not allowed." I have tried to modify the
> DDL settings in my database through >> exec sp_dboption
> mydatabase, "ddl in tran", true <<, but "ddl in tran" is
> not a recognized option any longer. Anyone know a
> workaround on this? THANKS>
install. I added a database, but when I go to add a table
through Visual Studio or osql I get the error "ADO error:
DDL statement is not allowed." I have tried to modify the
DDL settings in my database through >> exec sp_dboption
mydatabase, "ddl in tran", true <<, but "ddl in tran" is
not a recognized option any longer. Anyone know a
workaround on this? THANKS>Check your MDAC version
Try to update it.
Regards
---
All information provided above AS IS.
"Stephen Haiman" <shaiman@.ctt-inc.com> wrote in message
news:115501c3a2ea$88b9a2a0$a301280a@.phx.gbl...
> I have recently set up MSDE through a SharePoint services
> install. I added a database, but when I go to add a table
> through Visual Studio or osql I get the error "ADO error:
> DDL statement is not allowed." I have tried to modify the
> DDL settings in my database through >> exec sp_dboption
> mydatabase, "ddl in tran", true <<, but "ddl in tran" is
> not a recognized option any longer. Anyone know a
> workaround on this? THANKS>
msde AlaptopND sql server on save
I have SQL Server Developer edition on my laptop. Want to install MSDE on
same laptop (so VB .NET 2003 will work.
Any issues here with two versions/inmstances of "SQL Server" on same box?
On Sat, 16 Apr 2005 13:11:28 -0700, rOBBY wrote:
>I have SQL Server Developer edition on my laptop. Want to install MSDE on
>same laptop (so VB .NET 2003 will work.
>Any issues here with two versions/inmstances of "SQL Server" on same box?
Hi Robby,
I have never tried it myself, but I *think* that it should work. Though
I can imagine your poor laptop having a hard time, attempting to serve
two memory-intensive applications. :-)
For a more authorative answer, I suggest you repeat your question in
microsoft.public.sqlserver.msde, or microsoft.public.sqlserver.setup.
This group (microsoft.public.sqlserver.mseq) is actually about English
Query, so most MSDE and setup experts don't hang around here.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
same laptop (so VB .NET 2003 will work.
Any issues here with two versions/inmstances of "SQL Server" on same box?
On Sat, 16 Apr 2005 13:11:28 -0700, rOBBY wrote:
>I have SQL Server Developer edition on my laptop. Want to install MSDE on
>same laptop (so VB .NET 2003 will work.
>Any issues here with two versions/inmstances of "SQL Server" on same box?
Hi Robby,
I have never tried it myself, but I *think* that it should work. Though
I can imagine your poor laptop having a hard time, attempting to serve
two memory-intensive applications. :-)
For a more authorative answer, I suggest you repeat your question in
microsoft.public.sqlserver.msde, or microsoft.public.sqlserver.setup.
This group (microsoft.public.sqlserver.mseq) is actually about English
Query, so most MSDE and setup experts don't hang around here.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
MSDE 7.0 and SQL2000
Can you install SQL2000 on a server with an application
that is using MSDE 7.0 which was installed with the
software ?
If you can, what is the best way to do so without it
affecting the previous installation of MSDE 7.0 ?Yes you can. BE aware, though, that MDAC on the machine will be upgraded to 2.6 (if not or higher
already), so make sure you test the app for that MDAC version.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Valencia" <vahorda@.hotmail.com> wrote in message news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
> Can you install SQL2000 on a server with an application
> that is using MSDE 7.0 which was installed with the
> software ?
> If you can, what is the best way to do so without it
> affecting the previous installation of MSDE 7.0 ?
>|||Thank you Tibor. I checked the version of MDAC and it is
2.5.
>--Original Message--
>Yes you can. BE aware, though, that MDAC on the machine
will be upgraded to 2.6 (if not or higher
>already), so make sure you test the app for that MDAC
version.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Valencia" <vahorda@.hotmail.com> wrote in message
news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
>> Can you install SQL2000 on a server with an application
>> that is using MSDE 7.0 which was installed with the
>> software ?
>> If you can, what is the best way to do so without it
>> affecting the previous installation of MSDE 7.0 ?
>
>.
>sql
that is using MSDE 7.0 which was installed with the
software ?
If you can, what is the best way to do so without it
affecting the previous installation of MSDE 7.0 ?Yes you can. BE aware, though, that MDAC on the machine will be upgraded to 2.6 (if not or higher
already), so make sure you test the app for that MDAC version.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Valencia" <vahorda@.hotmail.com> wrote in message news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
> Can you install SQL2000 on a server with an application
> that is using MSDE 7.0 which was installed with the
> software ?
> If you can, what is the best way to do so without it
> affecting the previous installation of MSDE 7.0 ?
>|||Thank you Tibor. I checked the version of MDAC and it is
2.5.
>--Original Message--
>Yes you can. BE aware, though, that MDAC on the machine
will be upgraded to 2.6 (if not or higher
>already), so make sure you test the app for that MDAC
version.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Valencia" <vahorda@.hotmail.com> wrote in message
news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
>> Can you install SQL2000 on a server with an application
>> that is using MSDE 7.0 which was installed with the
>> software ?
>> If you can, what is the best way to do so without it
>> affecting the previous installation of MSDE 7.0 ?
>
>.
>sql
Wednesday, March 28, 2012
MSDE 7.0 and SQL2000
Can you install SQL2000 on a server with an application
that is using MSDE 7.0 which was installed with the
software ?
If you can, what is the best way to do so without it
affecting the previous installation of MSDE 7.0 ?Yes you can. BE aware, though, that MDAC on the machine will be upgraded to
2.6 (if not or higher
already), so make sure you test the app for that MDAC version.
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"Valencia" <vahorda@.hotmail.com> wrote in message news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...[Q
UOTE]
> Can you install SQL2000 on a server with an application
> that is using MSDE 7.0 which was installed with the
> software ?
> If you can, what is the best way to do so without it
> affecting the previous installation of MSDE 7.0 ?
>[/QUOTE]|||Thank you Tibor. I checked the version of MDAC and it is
2.5.
>--Original Message--
>Yes you can. BE aware, though, that MDAC on the machine
will be upgraded to 2.6 (if not or higher
>already), so make sure you test the app for that MDAC
version.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Valencia" <vahorda@.hotmail.com> wrote in message
news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
>
>.
>
that is using MSDE 7.0 which was installed with the
software ?
If you can, what is the best way to do so without it
affecting the previous installation of MSDE 7.0 ?Yes you can. BE aware, though, that MDAC on the machine will be upgraded to
2.6 (if not or higher
already), so make sure you test the app for that MDAC version.
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"Valencia" <vahorda@.hotmail.com> wrote in message news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...[Q
UOTE]
> Can you install SQL2000 on a server with an application
> that is using MSDE 7.0 which was installed with the
> software ?
> If you can, what is the best way to do so without it
> affecting the previous installation of MSDE 7.0 ?
>[/QUOTE]|||Thank you Tibor. I checked the version of MDAC and it is
2.5.
>--Original Message--
>Yes you can. BE aware, though, that MDAC on the machine
will be upgraded to 2.6 (if not or higher
>already), so make sure you test the app for that MDAC
version.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Valencia" <vahorda@.hotmail.com> wrote in message
news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
>
>.
>
MSDE 2K Is there a compatibility issue with Backupexe or Sharepoint
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
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
MSDE 2GB Limit
Hi
A Client has an MSDE install - checked by running @.@.version (clearly
says developer edition in the result text).
However the size of the data file is over 3GB, even allowing for empty
spaces the amount of data far exceeds 2GB. Pls explain?
The database was filled by regular insert statements.
Am 31 Oct 2005 04:14:49 -0800 schrieb yitzak:
> Hi
> A Client has an MSDE install - checked by running @.@.version (clearly
> says developer edition in the result text).
> However the size of the data file is over 3GB, even allowing for empty
> spaces the amount of data far exceeds 2GB. Pls explain?
> The database was filled by regular insert statements.
MSDE always shows "Desktop Engine" and not "Developer Edition"!
bye,
Helmut
A Client has an MSDE install - checked by running @.@.version (clearly
says developer edition in the result text).
However the size of the data file is over 3GB, even allowing for empty
spaces the amount of data far exceeds 2GB. Pls explain?
The database was filled by regular insert statements.
Am 31 Oct 2005 04:14:49 -0800 schrieb yitzak:
> Hi
> A Client has an MSDE install - checked by running @.@.version (clearly
> says developer edition in the result text).
> However the size of the data file is over 3GB, even allowing for empty
> spaces the amount of data far exceeds 2GB. Pls explain?
> The database was filled by regular insert statements.
MSDE always shows "Desktop Engine" and not "Developer Edition"!
bye,
Helmut
MSDE 2000sp3 and Full Text Indexing (Search Server)
I am new to MSDE, does anyone know if it comes with
Search Server or is that a full SQL Server app? If it is
available, how do I install it, or do I need to by it?
Thanks
Chris
Full-Text Search is not included with MSDE. It comes with the Enterprise,
Server, Personal (except on Windows 98), Developer, and Enterprise
Evaluation Editions.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chris Griffin" <msde@.doc-capture.co.uk> wrote in message
news:060d01c4b6c2$e0e65a80$a401280a@.phx.gbl...
>I am new to MSDE, does anyone know if it comes with
> Search Server or is that a full SQL Server app? If it is
> available, how do I install it, or do I need to by it?
> Thanks
> Chris
|||hi Chris,
"Chris Griffin" <msde@.doc-capture.co.uk> ha scritto nel messaggio
news:060d01c4b6c2$e0e65a80$a401280a@.phx.gbl
> I am new to MSDE, does anyone know if it comes with
> Search Server or is that a full SQL Server app? If it is
> available, how do I install it, or do I need to by it?
> Thanks
unfortunately MSDE does not support Full Text...
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
Search Server or is that a full SQL Server app? If it is
available, how do I install it, or do I need to by it?
Thanks
Chris
Full-Text Search is not included with MSDE. It comes with the Enterprise,
Server, Personal (except on Windows 98), Developer, and Enterprise
Evaluation Editions.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chris Griffin" <msde@.doc-capture.co.uk> wrote in message
news:060d01c4b6c2$e0e65a80$a401280a@.phx.gbl...
>I am new to MSDE, does anyone know if it comes with
> Search Server or is that a full SQL Server app? If it is
> available, how do I install it, or do I need to by it?
> Thanks
> Chris
|||hi Chris,
"Chris Griffin" <msde@.doc-capture.co.uk> ha scritto nel messaggio
news:060d01c4b6c2$e0e65a80$a401280a@.phx.gbl
> I am new to MSDE, does anyone know if it comes with
> Search Server or is that a full SQL Server app? If it is
> available, how do I install it, or do I need to by it?
> Thanks
unfortunately MSDE does not support Full Text...
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 2000a
What is going on with this program?
When I try to install it I get the error message:
"A strong SA password is required for security reasons. Please use SAPWD switch to supply the same. Refer to readme for more details. Setup will now exit."
Runing Win2k server, logged in as Administration.
Readme file says nothing about this
As usual, you can't find anything on M$ KB site.
I also tried the MSDE SP3 version - got the same results.I finally got it to install...had to edit the setup.ini file.
The server is running, the service is running but...
there is no enterprise manager...how are you suppose to manage your databases?|||There are a few things to manage your database. First of all there's the command-line tool called osql.exe that can be used to execute commands on your database. The second option is to use Access projects (supported on Access 2000 and higher if I'm not mistaken). Projects are a way to connect to a SQL Server or MSDE instance from within the Access product (pretty powerful). Last but not least there is the Web Data Administrator that can be downloaded fromhttp://www.microsoft.com/downloads/details.aspx?FamilyId=C039A798-C57A-419E-ACBC-2A332CB7F959&displaylang=en.
Hope this can help?|||Hi if anyone is still reading this thread this is very helpfull. I was trying to use MSDE via MATRIX but there seems to be only an option to create tables but not relationships between them so I am wondering how to actually access MSDE directly , which of above 3 ways do you suggest and where do I find more about command line and projects?sql
MSDE 2000 Wont Install after Uninstall
I installed MSDE 2000, then uninstalled it because of a
problem with a 3rd party program. I then uninstalled that
3rd party program and downloaded sql2kdesksp3.exe, and
unpacked the installer. I ran a command prompt and typed
setup SAPWD=password SecurityType=SQL
and it began to install, but when the installer came down 5
seconds it would just pause and not do anything. There is
no harddrive activity or anything. I have redownloaded the
package, and tried many things to try and get it to
working, but no success.
Help!
hi Mike,
"Mike" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:069c01c4b60c$09261510$a601280a@.phx.gbl
> I installed MSDE 2000, then uninstalled it because of a
> problem with a 3rd party program. I then uninstalled that
> 3rd party program and downloaded sql2kdesksp3.exe, and
> unpacked the installer. I ran a command prompt and typed
> setup SAPWD=password SecurityType=SQL
> and it began to install, but when the installer came down 5
> seconds it would just pause and not do anything. There is
> no harddrive activity or anything. I have redownloaded the
> package, and tried many things to try and get it to
> working, but no success.
first of all, you have to specify SECURITYMODE=SQL and not SecurityType=SQL
the problem you are facing is probably related to "Setup failed to configure
the server", as explained in
http://support.microsoft.com/default...99&Product=sql
due to a incomplete removal of MSDE instance... anyway, try adding the
/L*v "c:\MsdeLog.txt"
parameter to you command line call to setup.exe in order to create a (about
2mb) verbose log of the installation process, where you can search for
RETURN VALUE 3
condition and, about 10 lines before or after the failure cause is (little)
explained
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
problem with a 3rd party program. I then uninstalled that
3rd party program and downloaded sql2kdesksp3.exe, and
unpacked the installer. I ran a command prompt and typed
setup SAPWD=password SecurityType=SQL
and it began to install, but when the installer came down 5
seconds it would just pause and not do anything. There is
no harddrive activity or anything. I have redownloaded the
package, and tried many things to try and get it to
working, but no success.
Help!
hi Mike,
"Mike" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:069c01c4b60c$09261510$a601280a@.phx.gbl
> I installed MSDE 2000, then uninstalled it because of a
> problem with a 3rd party program. I then uninstalled that
> 3rd party program and downloaded sql2kdesksp3.exe, and
> unpacked the installer. I ran a command prompt and typed
> setup SAPWD=password SecurityType=SQL
> and it began to install, but when the installer came down 5
> seconds it would just pause and not do anything. There is
> no harddrive activity or anything. I have redownloaded the
> package, and tried many things to try and get it to
> working, but no success.
first of all, you have to specify SECURITYMODE=SQL and not SecurityType=SQL
the problem you are facing is probably related to "Setup failed to configure
the server", as explained in
http://support.microsoft.com/default...99&Product=sql
due to a incomplete removal of MSDE instance... anyway, try adding the
/L*v "c:\MsdeLog.txt"
parameter to you command line call to setup.exe in order to create a (about
2mb) verbose log of the installation process, where you can search for
RETURN VALUE 3
condition and, about 10 lines before or after the failure cause is (little)
explained
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 2000 SP4 Merge Modules
I have a MSDE 2000 InstallShield install package that I've created using the
merge modules. I downloaded the SP4 of the desktop engine from the microsoft
site. When downloaded and extracted, there is a folder on my machine
\MSDE\MSM which has all of the merge modules. I've noticed that the SP4
release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and qfepatch.msm.
In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I go
and build I receive the following error: "Error retrieving dependency
MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
why I'm getting this error?
Thanks.
Joanne
hi Joanne
jbayog wrote:
> I have a MSDE 2000 InstallShield install package that I've created
> using the merge modules. I downloaded the SP4 of the desktop engine
> from the microsoft site. When downloaded and extracted, there is a
> folder on my machine \MSDE\MSM which has all of the merge modules.
> I've noticed that the SP4 release has 3 new mm's: msxmlsql32.msm,
> msxmlsqlr32.msm, and qfepatch.msm. In the InstallShield DevStudio
> 9.01 IDE, I check the 3 new mm's. When I go and build I receive the
> following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone
> know why I'm getting this error?
no idea, never used MSDE merge modules, always installed using the setup.exe
boostrap installer.... but have you tried modifying the order of
installation?
http://msdn.microsoft.com/library/de...stsql_8yeq.asp
has not been updated (as BOL in general) at sp4 level, so no additional info
about those new merge modules seems available..
BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
specifies:
"Note Merge modules are not supported for new installations. They are
provided in SP4 for servicing instances of MSDE 2000 that were previously
installed using merge modules."
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I don't know much about MSDE and am just doing some research on it as of
this week.
However, I cam across this link yesterday which might be useful:
http://www.microsoft.com/sql/downloads/2000/sp4.asp
Here is an extract from the site:
"Users who have an existing instance of MSDE 2000 must know how their
instance of MSDE 2000 was installed to know how to update it. In particular,
you must know the original package name for your instance of MSDE 2000. To
determine the original package name, see the article How To Identify Which
MSI File Was Used for an Existing MSDE Installation in the Microsoft
Knowledge Base."
"jbayog" <jbayog@.discussions.microsoft.com> wrote in message
news:8D058312-1747-4A51-A100-FE79DC32C086@.microsoft.com...
>I have a MSDE 2000 InstallShield install package that I've created using
>the
> merge modules. I downloaded the SP4 of the desktop engine from the
> microsoft
> site. When downloaded and extracted, there is a folder on my machine
> \MSDE\MSM which has all of the merge modules. I've noticed that the SP4
> release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and
> qfepatch.msm.
> In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I
> go
> and build I receive the following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
> why I'm getting this error?
> Thanks.
> Joanne
|||Thanks so much for your help. This an existing MSDE 2000 InstallShield
install package and we have a client who wants to upgrade to SP4 so that is
why I'm trying to build an upgrade for them. I'd like to get rid of using
the MSDE 2000 merge modules per Microsoft's comment. I got it to build by
editing the msxmlsql32.msm and the msxmlsqlr32.msm using the Orca tool. I
think there is a problem with the rows in the ModuleDependency table. I
guess I have the option of building it without these two mm's as our database
application doesn't use xml. I'm a little apprehensive of doing this only
because there is no documentation on these new mm's. I might post to
InstallShield also. Again thanks.
Joanne
Joanne
"Andrea Montanari" wrote:
> hi Joanne
> jbayog wrote:
> no idea, never used MSDE merge modules, always installed using the setup.exe
> boostrap installer.... but have you tried modifying the order of
> installation?
> http://msdn.microsoft.com/library/de...stsql_8yeq.asp
> has not been updated (as BOL in general) at sp4 level, so no additional info
> about those new merge modules seems available..
> BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
> specifies:
> "Note Merge modules are not supported for new installations. They are
> provided in SP4 for servicing instances of MSDE 2000 that were previously
> installed using merge modules."
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
merge modules. I downloaded the SP4 of the desktop engine from the microsoft
site. When downloaded and extracted, there is a folder on my machine
\MSDE\MSM which has all of the merge modules. I've noticed that the SP4
release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and qfepatch.msm.
In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I go
and build I receive the following error: "Error retrieving dependency
MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
why I'm getting this error?
Thanks.
Joanne
hi Joanne
jbayog wrote:
> I have a MSDE 2000 InstallShield install package that I've created
> using the merge modules. I downloaded the SP4 of the desktop engine
> from the microsoft site. When downloaded and extracted, there is a
> folder on my machine \MSDE\MSM which has all of the merge modules.
> I've noticed that the SP4 release has 3 new mm's: msxmlsql32.msm,
> msxmlsqlr32.msm, and qfepatch.msm. In the InstallShield DevStudio
> 9.01 IDE, I check the 3 new mm's. When I go and build I receive the
> following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone
> know why I'm getting this error?
no idea, never used MSDE merge modules, always installed using the setup.exe
boostrap installer.... but have you tried modifying the order of
installation?
http://msdn.microsoft.com/library/de...stsql_8yeq.asp
has not been updated (as BOL in general) at sp4 level, so no additional info
about those new merge modules seems available..
BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
specifies:
"Note Merge modules are not supported for new installations. They are
provided in SP4 for servicing instances of MSDE 2000 that were previously
installed using merge modules."
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I don't know much about MSDE and am just doing some research on it as of
this week.
However, I cam across this link yesterday which might be useful:
http://www.microsoft.com/sql/downloads/2000/sp4.asp
Here is an extract from the site:
"Users who have an existing instance of MSDE 2000 must know how their
instance of MSDE 2000 was installed to know how to update it. In particular,
you must know the original package name for your instance of MSDE 2000. To
determine the original package name, see the article How To Identify Which
MSI File Was Used for an Existing MSDE Installation in the Microsoft
Knowledge Base."
"jbayog" <jbayog@.discussions.microsoft.com> wrote in message
news:8D058312-1747-4A51-A100-FE79DC32C086@.microsoft.com...
>I have a MSDE 2000 InstallShield install package that I've created using
>the
> merge modules. I downloaded the SP4 of the desktop engine from the
> microsoft
> site. When downloaded and extracted, there is a folder on my machine
> \MSDE\MSM which has all of the merge modules. I've noticed that the SP4
> release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and
> qfepatch.msm.
> In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I
> go
> and build I receive the following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
> why I'm getting this error?
> Thanks.
> Joanne
|||Thanks so much for your help. This an existing MSDE 2000 InstallShield
install package and we have a client who wants to upgrade to SP4 so that is
why I'm trying to build an upgrade for them. I'd like to get rid of using
the MSDE 2000 merge modules per Microsoft's comment. I got it to build by
editing the msxmlsql32.msm and the msxmlsqlr32.msm using the Orca tool. I
think there is a problem with the rows in the ModuleDependency table. I
guess I have the option of building it without these two mm's as our database
application doesn't use xml. I'm a little apprehensive of doing this only
because there is no documentation on these new mm's. I might post to
InstallShield also. Again thanks.
Joanne
Joanne
"Andrea Montanari" wrote:
> hi Joanne
> jbayog wrote:
> no idea, never used MSDE merge modules, always installed using the setup.exe
> boostrap installer.... but have you tried modifying the order of
> installation?
> http://msdn.microsoft.com/library/de...stsql_8yeq.asp
> has not been updated (as BOL in general) at sp4 level, so no additional info
> about those new merge modules seems available..
> BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
> specifies:
> "Note Merge modules are not supported for new installations. They are
> provided in SP4 for servicing instances of MSDE 2000 that were previously
> installed using merge modules."
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
MSDE 2000 SP3a Won't install on 2003 server
I hope someone has seen this... I have a 2003 server that refuses to install MSDE 2000 SP3a. The install goes to 99% complete, then rolls back and automatically uninstalls. I have seen this in the past when file and printer sharing is not installed or
insufficient permissions, but this time it has me stumped. Event viewer is useless, it just reports that the install failed and doesn't give any reason. No error logs get created, no errors come up, the install just won't take. I have sucessfully insta
lled MSDE 2000 on other 2003 servers and have never had this much trouble. I have a verbose install log available from the install if anyone wants to look at it. Any ideas?
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
hi,
<dnoble@.-NOSPAM-raymorgan.com> ha scritto nel messaggio
news:%23fZGykYpEHA.648@.tk2msftngp13.phx.gbl
> I hope someone has seen this... I have a 2003 server that refuses to
> install MSDE 2000 SP3a. The install goes to 99% complete, then rolls
> back and automatically uninstalls. I have seen this in the past when
> file and printer sharing is not installed or insufficient
> permissions, but this time it has me stumped. Event viewer is
> useless, it just reports that the install failed and doesn't give any
> reason. No error logs get created, no errors come up, the install
> just won't take. I have sucessfully installed MSDE 2000 on other
> 2003 servers and have never had this much trouble. I have a verbose
> install log available from the install if anyone wants to look at it.
> Any ideas?
search for
RETURN VALUE 3
in your install log... it usually reports where the problem is
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 the reply... I did locate a spot with Return Value 3. From the
log file:
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (FOX,LocalSystem,87).
Action ended 10:04:07: InstallFinalize. Return value 3.
Any thoughts on this?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2rtpgpF1f5farU1@.uni-berlin.de...
> hi,
> <dnoble@.-NOSPAM-raymorgan.com> ha scritto nel messaggio
> news:%23fZGykYpEHA.648@.tk2msftngp13.phx.gbl
> search for
> RETURN VALUE 3
> in your install log... it usually reports where the problem is
> --
> 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
>
|||"News" <david-noble@.sbcglobal.net> ha scritto nel messaggio
news:TDk6d.3964$nj.741@.newssvr13.news.prodigy.com
> Thanks for the reply... I did locate a spot with Return Value 3.
> From the log file:
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity failed (FOX,LocalSystem,87).
> Action ended 10:04:07: InstallFinalize. Return value 3.
> Any thoughts on this?
please have a look at http://tinyurl.com/69vo6 if can help solving your
problem
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
|||If you setup is failing, specify a command line parameter DISABLEROLLBACK =
1, this would stop MSDE Installer from rolling back in case of failure.
Also specify /L*v <log file patch with name>. This would enable setup to
write logs into the specified file. Try to search "return value 3" and
check where did it fail.
Once we know where it is failing we can help better. Also add the logfile
when you reply .
|||Thanks for all the replys, but so far all are off base a bit... The server
service is already running and file sharing is installed. A log file was
created and return value 3 came up with the following:
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (FOX,LocalSystem,87).
Action ended 10:04:07: InstallFinalize. Return value 3.
All responses to this so far have referred me to articles that talk about
making sure the server service is running, which is already the case.
<dnoble@.-NOSPAM-raymorgan.com> wrote in message
news:%23fZGykYpEHA.648@.tk2msftngp13.phx.gbl...
> I hope someone has seen this... I have a 2003 server that refuses to
install MSDE 2000 SP3a. The install goes to 99% complete, then rolls back
and automatically uninstalls. I have seen this in the past when file and
printer sharing is not installed or insufficient permissions, but this time
it has me stumped. Event viewer is useless, it just reports that the
install failed and doesn't give any reason. No error logs get created, no
errors come up, the install just won't take. I have sucessfully installed
MSDE 2000 on other 2003 servers and have never had this much trouble. I
have a verbose install log available from the install if anyone wants to
look at it. Any ideas?
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
insufficient permissions, but this time it has me stumped. Event viewer is useless, it just reports that the install failed and doesn't give any reason. No error logs get created, no errors come up, the install just won't take. I have sucessfully insta
lled MSDE 2000 on other 2003 servers and have never had this much trouble. I have a verbose install log available from the install if anyone wants to look at it. Any ideas?
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
hi,
<dnoble@.-NOSPAM-raymorgan.com> ha scritto nel messaggio
news:%23fZGykYpEHA.648@.tk2msftngp13.phx.gbl
> I hope someone has seen this... I have a 2003 server that refuses to
> install MSDE 2000 SP3a. The install goes to 99% complete, then rolls
> back and automatically uninstalls. I have seen this in the past when
> file and printer sharing is not installed or insufficient
> permissions, but this time it has me stumped. Event viewer is
> useless, it just reports that the install failed and doesn't give any
> reason. No error logs get created, no errors come up, the install
> just won't take. I have sucessfully installed MSDE 2000 on other
> 2003 servers and have never had this much trouble. I have a verbose
> install log available from the install if anyone wants to look at it.
> Any ideas?
search for
RETURN VALUE 3
in your install log... it usually reports where the problem is
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 the reply... I did locate a spot with Return Value 3. From the
log file:
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (FOX,LocalSystem,87).
Action ended 10:04:07: InstallFinalize. Return value 3.
Any thoughts on this?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2rtpgpF1f5farU1@.uni-berlin.de...
> hi,
> <dnoble@.-NOSPAM-raymorgan.com> ha scritto nel messaggio
> news:%23fZGykYpEHA.648@.tk2msftngp13.phx.gbl
> search for
> RETURN VALUE 3
> in your install log... it usually reports where the problem is
> --
> 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
>
|||"News" <david-noble@.sbcglobal.net> ha scritto nel messaggio
news:TDk6d.3964$nj.741@.newssvr13.news.prodigy.com
> Thanks for the reply... I did locate a spot with Return Value 3.
> From the log file:
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity failed (FOX,LocalSystem,87).
> Action ended 10:04:07: InstallFinalize. Return value 3.
> Any thoughts on this?
please have a look at http://tinyurl.com/69vo6 if can help solving your
problem
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
|||If you setup is failing, specify a command line parameter DISABLEROLLBACK =
1, this would stop MSDE Installer from rolling back in case of failure.
Also specify /L*v <log file patch with name>. This would enable setup to
write logs into the specified file. Try to search "return value 3" and
check where did it fail.
Once we know where it is failing we can help better. Also add the logfile
when you reply .
|||Thanks for all the replys, but so far all are off base a bit... The server
service is already running and file sharing is installed. A log file was
created and return value 3 came up with the following:
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (FOX,LocalSystem,87).
Action ended 10:04:07: InstallFinalize. Return value 3.
All responses to this so far have referred me to articles that talk about
making sure the server service is running, which is already the case.
<dnoble@.-NOSPAM-raymorgan.com> wrote in message
news:%23fZGykYpEHA.648@.tk2msftngp13.phx.gbl...
> I hope someone has seen this... I have a 2003 server that refuses to
install MSDE 2000 SP3a. The install goes to 99% complete, then rolls back
and automatically uninstalls. I have seen this in the past when file and
printer sharing is not installed or insufficient permissions, but this time
it has me stumped. Event viewer is useless, it just reports that the
install failed and doesn't give any reason. No error logs get created, no
errors come up, the install just won't take. I have sucessfully installed
MSDE 2000 on other 2003 servers and have never had this much trouble. I
have a verbose install log available from the install if anyone wants to
look at it. Any ideas?
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
MSDE 2000 SP3a install failure
I am getting an error when installing SP3a of MSDE. I get the error message "The instance name specified is invalid." This is the first SQL database installed, so there is no instance name. I have tried "default" and "MSSQLSERVER" as instance names without success.
your help is appreciated.the instance name is "MSDE"
Why is this not in the setup documentation?
your help is appreciated.the instance name is "MSDE"
Why is this not in the setup documentation?
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.
MSDE 2000 SP3 fails to install
MSDE 2000 SP3 fails to install on a windows 2000 terminal server. The error
message I get is "MSDE 200 SP3 installation failed with exit code 1603" and
“A strong password is required for security reasons. Please use SAPWD switch
to supply the same. Refer to read me for more details. Setup will now exit.”
I have come across this once before and removed the server from the domain,
in this case that is not an option. I have denied the read right to the
default domain policy which is the only policy that is applying. Anybody have
any ideas on how I can install this.
hi bob,
bob wrote:
> MSDE 2000 SP3 fails to install on a windows 2000 terminal server. The
> error message I get is "MSDE 200 SP3 installation failed with exit
> code 1603" and "A strong password is required for security reasons.
> Please use SAPWD switch to supply the same. Refer to read me for more
> details. Setup will now exit." I have come across this once before
> and removed the server from the domain, in this case that is not an
> option. I have denied the read right to the default domain policy
> which is the only policy that is applying. Anybody have any ideas on
> how I can install this.
as indicated by the error description, you have to provide a strong password
for "sa" login as a parameter, in the form of
c:\...\>setup.exe ... SAPWD="your strong password" ...
all available parameters for the setup.exe bootstrap installer are provided
at
http://msdn.microsoft.com/library/de...stsql_84xl.asp
or, if you really are sure (please don't) you do not need a strong sa
password, you have to provide the
BLANKSAPWD=1
parameter
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea
I tried BLANKSAPWD=1 and I even tried setting a strong password, neither one
worked. Do you have any other suggestions?
"Andrea Montanari" wrote:
> hi bob,
> bob wrote:
> as indicated by the error description, you have to provide a strong password
> for "sa" login as a parameter, in the form of
> c:\...\>setup.exe ... SAPWD="your strong password" ...
> all available parameters for the setup.exe bootstrap installer are provided
> at
> http://msdn.microsoft.com/library/de...stsql_84xl.asp
> or, if you really are sure (please don't) you do not need a strong sa
> password, you have to provide the
> BLANKSAPWD=1
> parameter
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Bob,
bob wrote:
> Andrea
> I tried BLANKSAPWD=1 and I even tried setting a strong password,
> neither one worked. Do you have any other suggestions?
>
can you please post your paramenters?
what kind of error do you get?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
message I get is "MSDE 200 SP3 installation failed with exit code 1603" and
“A strong password is required for security reasons. Please use SAPWD switch
to supply the same. Refer to read me for more details. Setup will now exit.”
I have come across this once before and removed the server from the domain,
in this case that is not an option. I have denied the read right to the
default domain policy which is the only policy that is applying. Anybody have
any ideas on how I can install this.
hi bob,
bob wrote:
> MSDE 2000 SP3 fails to install on a windows 2000 terminal server. The
> error message I get is "MSDE 200 SP3 installation failed with exit
> code 1603" and "A strong password is required for security reasons.
> Please use SAPWD switch to supply the same. Refer to read me for more
> details. Setup will now exit." I have come across this once before
> and removed the server from the domain, in this case that is not an
> option. I have denied the read right to the default domain policy
> which is the only policy that is applying. Anybody have any ideas on
> how I can install this.
as indicated by the error description, you have to provide a strong password
for "sa" login as a parameter, in the form of
c:\...\>setup.exe ... SAPWD="your strong password" ...
all available parameters for the setup.exe bootstrap installer are provided
at
http://msdn.microsoft.com/library/de...stsql_84xl.asp
or, if you really are sure (please don't) you do not need a strong sa
password, you have to provide the
BLANKSAPWD=1
parameter
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea
I tried BLANKSAPWD=1 and I even tried setting a strong password, neither one
worked. Do you have any other suggestions?
"Andrea Montanari" wrote:
> hi bob,
> bob wrote:
> as indicated by the error description, you have to provide a strong password
> for "sa" login as a parameter, in the form of
> c:\...\>setup.exe ... SAPWD="your strong password" ...
> all available parameters for the setup.exe bootstrap installer are provided
> at
> http://msdn.microsoft.com/library/de...stsql_84xl.asp
> or, if you really are sure (please don't) you do not need a strong sa
> password, you have to provide the
> BLANKSAPWD=1
> parameter
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Bob,
bob wrote:
> Andrea
> I tried BLANKSAPWD=1 and I even tried setting a strong password,
> neither one worked. Do you have any other suggestions?
>
can you please post your paramenters?
what kind of error do you get?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
MSDE 2000 Release A and Windows Installer
I am currently writing an installer for our product, which needs to incorporate MSDE 2000.
Previous versions of the MSDE install included merge modules (.msm files) that could be incorporated straight into a Windows Installer .msi file. However, the latest version (Release A) does not include the merge modules, and to top that, also states tha
t "Desktop Engine does not support nested installations. You must not call an .msi file from within another .msi file".
My questions are:
- How are we supposed to install MSDE when we are distributing .msi files? We need .msi functionality for other components of our install, so using a non-Windows Installer technology is not an option. Do we need to ask our users to install MSDE separat
ely (ouch)?
- Why did the merge modules disappear? I thought that these were the Microsoft-sanctioned method for installing runtime components...
- Are there any other options - we want to distribute a single file, and we really don't want to have to mix and match .msi and other setup technologies...
Marc Durdin
Software for Specialists
Hi Andy,
Thanks for the comment. However, this page is not up to date. It recommends using the merge modules... which are not supported any more by Microsoft (and are not even included in the latest release of MSDE). Any other suggestions?
Regards,
Marc
Previous versions of the MSDE install included merge modules (.msm files) that could be incorporated straight into a Windows Installer .msi file. However, the latest version (Release A) does not include the merge modules, and to top that, also states tha
t "Desktop Engine does not support nested installations. You must not call an .msi file from within another .msi file".
My questions are:
- How are we supposed to install MSDE when we are distributing .msi files? We need .msi functionality for other components of our install, so using a non-Windows Installer technology is not an option. Do we need to ask our users to install MSDE separat
ely (ouch)?
- Why did the merge modules disappear? I thought that these were the Microsoft-sanctioned method for installing runtime components...
- Are there any other options - we want to distribute a single file, and we really don't want to have to mix and match .msi and other setup technologies...
Marc Durdin
Software for Specialists
Hi Andy,
Thanks for the comment. However, this page is not up to date. It recommends using the merge modules... which are not supported any more by Microsoft (and are not even included in the latest release of MSDE). Any other suggestions?
Regards,
Marc
MSDE 2000 Release A - Instalation Problem in Windows XP SP2
I can't install MSDE release A in Windows XP SP2. I verified if Server
Service is started and it is ok. I also verified if File and Printer sharing
is checked on network properties and it is ok. The windows firewall also is
disabled but the instalation doesn't work. I run the follow comand setup.exe
sapwd="suportebsb." /L*v C:/MSDELog.log.
Anyone can help me?
Regards,
Cicero Galdino
******** This is the lastest lines in log instalation files
*******************
2005-06-01 16:49:35.64 spid4 Default collation successfully changed.
2005-06-01 16:49:35.67 spid4 Recovery complete.
2005-06-01 16:49:35.67 spid4 SQL global counter collection task is
created.
2005-06-01 16:49:35.69 spid4 Warning: override, autoexec procedures
skipped.
2005-06-01 16:49:43.36 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
=== Logging stopped: 01/06/2005 16:59:54 ===
MSI (c) (18:48) [16:59:54:724]: Note: 1: 1708
MSI (c) (18:48) [16:59:54:724]: Product: Microsoft SQL Server Desktop Engine
-- Installation operation failed.
MSI (c) (18:48) [16:59:54:724]: Grabbed execution mutex.
MSI (c) (18:48) [16:59:54:724]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (18:48) [16:59:54:740]: MainEngineThread is returning 1603
=== Verbose logging stopped: 01/06/2005 16:59:54 ===
hi Cicero,
Cicero wrote:
> I can't install MSDE release A in Windows XP SP2. I verified if Server
> Service is started and it is ok. I also verified if File and Printer
> sharing is checked on network properties and it is ok. The windows
> firewall also is disabled but the instalation doesn't work. I run the
> follow comand setup.exe sapwd="suportebsb." /L*v C:/MSDELog.log.
please inspect your C:/MSDELog.log for
RETURN VALUE 3
entrie(s), that reports exeptions duting the install process...
about 10/15 lines before each entry some (sometime cryptic) descritpion of
the problem will be available
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
Service is started and it is ok. I also verified if File and Printer sharing
is checked on network properties and it is ok. The windows firewall also is
disabled but the instalation doesn't work. I run the follow comand setup.exe
sapwd="suportebsb." /L*v C:/MSDELog.log.
Anyone can help me?
Regards,
Cicero Galdino
******** This is the lastest lines in log instalation files
*******************
2005-06-01 16:49:35.64 spid4 Default collation successfully changed.
2005-06-01 16:49:35.67 spid4 Recovery complete.
2005-06-01 16:49:35.67 spid4 SQL global counter collection task is
created.
2005-06-01 16:49:35.69 spid4 Warning: override, autoexec procedures
skipped.
2005-06-01 16:49:43.36 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
=== Logging stopped: 01/06/2005 16:59:54 ===
MSI (c) (18:48) [16:59:54:724]: Note: 1: 1708
MSI (c) (18:48) [16:59:54:724]: Product: Microsoft SQL Server Desktop Engine
-- Installation operation failed.
MSI (c) (18:48) [16:59:54:724]: Grabbed execution mutex.
MSI (c) (18:48) [16:59:54:724]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (18:48) [16:59:54:740]: MainEngineThread is returning 1603
=== Verbose logging stopped: 01/06/2005 16:59:54 ===
hi Cicero,
Cicero wrote:
> I can't install MSDE release A in Windows XP SP2. I verified if Server
> Service is started and it is ok. I also verified if File and Printer
> sharing is checked on network properties and it is ok. The windows
> firewall also is disabled but the instalation doesn't work. I run the
> follow comand setup.exe sapwd="suportebsb." /L*v C:/MSDELog.log.
please inspect your C:/MSDELog.log for
RETURN VALUE 3
entrie(s), that reports exeptions duting the install process...
about 10/15 lines before each entry some (sometime cryptic) descritpion of
the problem will be available
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 2000 Rel A Installation Failure
try install previuos version of msde 2000 rel a, and update with sp3.
"chris fearnley" <anonymous@.discussions.microsoft.com> escreveu na mensagem
news:3D93D00C-1AAD-427F-905C-26533B3388F6@.microsoft.com...
> I have the same problem. I am trying to do test installtions of MSDE 2000
Release A on several systems, along with our own app which uses .NET. About
half the PCs halt the installation, usually when there is '7 seconds left'
and just hang. Same problem on XP SP1 and even old Win98 SE.
all right, see the 320873 article from microsoft's knowledge base to
manually remove a msde. since you don't have msde installed anymore, looking
for the key in registry and delete them.
after that, try to install msde 2000 (not msde 2000 rel a) and sp3.
"Joe Schillace" <anonymous@.discussions.microsoft.com> escreveu na mensagem
news:B835C284-FF56-4A3E-82F3-E467218FAF03@.microsoft.com...
> Adriano:
> The previous version of MSDE that I had installed was from MS Office 2000.
It appears that it installs SQL 7.
> I re-installed this version and it went in without a hitch. I then tried
installing SP3a.
> It got to about 3 or 4 seconds left and then rolled back. The setup log
indicates a failed installation.
> It seems that MSDE 2000 Rel A left some scraps in the windows registry. I
searched for "microsoft sql server" and found more than a hundred. I can't
tell from the log file which entry is causing the problem.
> I have deleted the microsoft sql server folder and ran regclean, hoping it
would remove the orphans. But, I am still having the problem.
|||Just found some more info to help solve previous posting.
There is an error line in the install log file:
......
Executing "G:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "Latin1_General_CI_AS""
Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.
Action ended 10:43:17: InstallFinalize. Return value 3.
......
...and in the error log from the newly-crtated SQL folder: (created by cnfgsvr?)
.....
2004-05-28 10:41:11.83 spid3 Default collation successfully changed.
2004-05-28 10:41:11.93 spid3 Recovery complete.
2004-05-28 10:41:11.93 spid3 SQL global counter collection task is created.
2004-05-28 10:41:12.64 spid3 Warning: override, autoexec procedures skipped.
2004-05-28 10:42:58.51 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.
(that was the last line in the log)
Note the time delay between the last 2 entries.
"chris fearnley" <anonymous@.discussions.microsoft.com> escreveu na mensagem
news:3D93D00C-1AAD-427F-905C-26533B3388F6@.microsoft.com...
> I have the same problem. I am trying to do test installtions of MSDE 2000
Release A on several systems, along with our own app which uses .NET. About
half the PCs halt the installation, usually when there is '7 seconds left'
and just hang. Same problem on XP SP1 and even old Win98 SE.
all right, see the 320873 article from microsoft's knowledge base to
manually remove a msde. since you don't have msde installed anymore, looking
for the key in registry and delete them.
after that, try to install msde 2000 (not msde 2000 rel a) and sp3.
"Joe Schillace" <anonymous@.discussions.microsoft.com> escreveu na mensagem
news:B835C284-FF56-4A3E-82F3-E467218FAF03@.microsoft.com...
> Adriano:
> The previous version of MSDE that I had installed was from MS Office 2000.
It appears that it installs SQL 7.
> I re-installed this version and it went in without a hitch. I then tried
installing SP3a.
> It got to about 3 or 4 seconds left and then rolled back. The setup log
indicates a failed installation.
> It seems that MSDE 2000 Rel A left some scraps in the windows registry. I
searched for "microsoft sql server" and found more than a hundred. I can't
tell from the log file which entry is causing the problem.
> I have deleted the microsoft sql server folder and ran regclean, hoping it
would remove the orphans. But, I am still having the problem.
|||Just found some more info to help solve previous posting.
There is an error line in the install log file:
......
Executing "G:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q "Latin1_General_CI_AS""
Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.
Action ended 10:43:17: InstallFinalize. Return value 3.
......
...and in the error log from the newly-crtated SQL folder: (created by cnfgsvr?)
.....
2004-05-28 10:41:11.83 spid3 Default collation successfully changed.
2004-05-28 10:41:11.93 spid3 Recovery complete.
2004-05-28 10:41:11.93 spid3 SQL global counter collection task is created.
2004-05-28 10:41:12.64 spid3 Warning: override, autoexec procedures skipped.
2004-05-28 10:42:58.51 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.
(that was the last line in the log)
Note the time delay between the last 2 entries.
MSDE 2000 Question
Can you install the SQL client tools on a box running msde and register the msde database under enterprise manager?
Thanksyes, you cansql
Thanksyes, you cansql
Subscribe to:
Posts (Atom)