Installing MSDE2000 sp3 - help

Hiya folks,
I'm a newbie at this, so forgive the ignorance that I may display!
I have installed a software package on my system that installs MSDE through
merge modules contained in its MSI. I have several workstations that
connect. Unfortunately, with SP2 coming down the pipe for windows xp, i
have to do lots of fancy stuff to make sure they still connect (it uses
named pipes tcp/ip). The solution according to microsoft is to install SP3
for sql...i've downloaded the MSDE version of the upgrade, and attempted to
install for several hours with no luck.
First, it said i required a strong password, which i supplised in the
setup.ini:
[options]
sapassword="mypassword"
Things started to load, and then the installer quit. Confused, I started it
again. Now the installer is giving me '
the instance name specified is invalid'
Ok, so i go back to the setup.ini and add a line
[options]
sapassword="mypassword"
instancename="liveddm"
and STILL, i get the invalid instance name error message. No matter what I
seem to try, it is telling me i have an invalid instance name; if i use
enterprise manager, i can clearly see my instance and browse the attached
database. I've also tried instancename="computername\liveddm" with no luck.
Any help would be greatly appreciated.
Thanks!
Sheldon
sheldon@.REMOVETHISthedoctorcompany.com
Sheldon Purkiss wrote:
> Hiya folks,
> I'm a newbie at this, so forgive the ignorance that I may display!
> I have installed a software package on my system that installs MSDE through
> merge modules contained in its MSI. I have several workstations that
> connect. Unfortunately, with SP2 coming down the pipe for windows xp, i
> have to do lots of fancy stuff to make sure they still connect (it uses
> named pipes tcp/ip). The solution according to microsoft is to install SP3
> for sql...i've downloaded the MSDE version of the upgrade, and attempted to
> install for several hours with no luck.
> First, it said i required a strong password, which i supplised in the
> setup.ini:
> [options]
> sapassword="mypassword"
> Things started to load, and then the installer quit. Confused, I started it
> again. Now the installer is giving me '
> the instance name specified is invalid'
> Ok, so i go back to the setup.ini and add a line
> [options]
> sapassword="mypassword"
> instancename="liveddm"
> and STILL, i get the invalid instance name error message. No matter what I
> seem to try, it is telling me i have an invalid instance name; if i use
> enterprise manager, i can clearly see my instance and browse the attached
> database. I've also tried instancename="computername\liveddm" with no luck.
> Any help would be greatly appreciated.
> Thanks!
> Sheldon
> sheldon@.REMOVETHISthedoctorcompany.com
>
>
>
Hi Sheldon
Unfortunately, I believe that if your software vendor has installed MSDE
using merge modules from within their own MSI they will need to supply
you with the patch package themselves.
See http://www.microsoft.com/sql/downloads/2000/sp3.asp
Tony

Installing MSDE SP3 to Win98 causes an error.

Ok I have an MSI file that installs an instance of the MSDE. I recently updated my install to used the SP3 MSMs of the MSDE. I have the installation working correctly on XP. However it fails rather quickly on install to Win98. I will paste the log file of the failure below.

To create the installation I used the VisualStudio installer. Afte the installtion I use ORCA and edit the MSI with the following values in the property table.

ProductLanguage = 1033
SqlBlankPwd = 1
SqlSecurityMode = SQL

No special actions are being used by my installer. Yet according to MS the reason for my error is that I am using a special action with a non-c++ dll (KB Article (http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B306627)) . I am guessing that this is something that MS is doing. Has anyone else gotten a successful install of SP3 onto Win98? Any info would be helpful.

Mike Villaronga
mike_villaronga@.yahoo.com

LogFile:

Internal Error 2737. StreamSupportFiles.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B, C:\WINDOWS\TEMP\MSI60B6.TMP, StreamSupportFiles
=== Logging stopped: 2/3/03 10:06:17 ===I have not gotten SP3 to install on win98. I have tried to do it manually as well as from an install shield application. I get an error message that there is a dll missing. It doesn't specify which dll or give any kind of clue.

[SIZE=1]Originally posted by mvillaronga
Ok I have an MSI file that installs an instance of the MSDE. I recently updated my install to used the SP3 MSMs of the MSDE. I have the installation working correctly on XP. However it fails rather quickly on install to Win98. I will paste the log file of the failure below.

I am guessing that this is something that MS is doing. Has anyone else gotten a successful install of SP3 onto Win98? Any info would be helpful.

Installing MSDE 2000 on Server with SQL 2005 Express

Can anybody help?

I have a Windows XP and 2003 server; we have installed SQL 2005 Express on it but have an application that installs MSDE 2000 to connect to an application. After the MSDE 2000 is installed we can no longer see the instance across the network. If we uninstall the SQL 2005 express version we can see the Instance in MSDE 2000.

Is there any compatibility issue with install MSDE 2000 after SQL 2005 has been installed.

Many Thanks in advance

David

In general, this should work. There are specific limitations, which I think are well spelled out in BOL. Here's a copy and paste; hopefully this will describe your issue:

In SQL Server 2000, the identification of the server connection endpoints was performed by the SQL Server service. SQL Server 2005 replaces that function with the SQL Server Browser service. If you install SQL Server on a computer that is also running SQL Server 2000 or MSDE, you must ensure that SQL Server 2000 or MSDE is upgraded to Service Pack 3 (SP3) or later. Versions prior to SP3 do not properly share port 1434 and may not make your SQL Server instances available to requesting client applications. Although you can change the services startup order so that the SQL Server Browser service starts before SQL Server 2000 or MSDE, the recommended resolution is to update all older versions of SQL Server to the latest service pack.

When an instance of SQL Server 2000 is installed on the computer, if the SQL Server Browser is not running, the SQL Server 2000 listener service starts. If SQL Server Browser starts after the listener service, it waits 5 seconds for SQL Server 2000 to give up port 1434. If that does not occur, SQL Server Browser fails to start. To resolve this problem with versions of SQL Server 2000 prior to service pack 3, stop SQL Server 2000, start SQL Server Browser, then restart SQL Server 2000. The SQL Server 2000 listener service continues to attempt to start on port 1434, so the SQL Server 2000 instance should be upgraded to service pack 3 as soon as possible.

SQL Server 7.0 had no similar capabilities and has no conflicts with SQL Server Browser.

Installation problems with Reportin Services

I'm having problem installing SQL Server 2005 Express Edition with Advanced Services SP1. Everything installs fine until I reach the installation of Reporting Services, there I get the following message --> "IID_IIMSAdminBase object error. The error code is -2147221164."

Any ideas as to how to solve this..?

Thanks in advance.

Could you post the information from the setup logs?

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

Mike

|||

Any answer to this post?....I am having the same problem.

Patrick (pdill@.clovor.com)

|||Same for you, can you post the log files of the installer ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Jens,

I uninstalled SQL Server(all parts of it), Uninstalled IIS, and the reinstalled worked fine.

Patrick.

Installation problems with Reportin Services

I'm having problem installing SQL Server 2005 Express Edition with Advanced Services SP1. Everything installs fine until I reach the installation of Reporting Services, there I get the following message --> "IID_IIMSAdminBase object error. The error code is -2147221164."

Any ideas as to how to solve this..?

Thanks in advance.

Could you post the information from the setup logs?

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

Mike