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