December 19, 2001 at 9:15 am
Hi everyone,
Sorry for the newbie-like post, but I've just started working with MSDE 2000 and I'm a little confused by the error being reported by the service pack install - error code 267. The installation in question is on a Windows XP Home Edition (not sure if this makes any difference). Below is a snipet of the install log, any suggestiosn would be greatly appreciated.
Thanks
******************** install log *******************************
Action 17:20:10: InstallServices. Installing new services
Action 17:20:11: InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
Loading extended custom action library sqlcax.dll
Starting custom action InstallPerfMon
Registering performance counters from sqlctr.ini
PerfmonLoad routine returned error code 267
Action ended 17:20:13: InstallFinalize. Return value 3.
Action 17:20:13: Rollback. Rolling back action:
December 19, 2001 at 5:28 pm
Found this in the MS newsgroups, posted by Rich B (RBeverly@Dickies.com):
"The cause of the problem in this case was that I was
failing to provide the same settings in the setup.ini file
that were present in the original install of MSDE.
For example:
Contents of setup.ini for original install of MSDE:
[Options]
TargetDir="Some path"
DataDir="Some other path"
If I apply the patch with the default setup.ini file:
[Options]
The patch fails at PerfmonLoad with error 267.
If I supply the same settings in setup.ini that were
present during the original install then all is well."
Maybe it will help!
Andy
December 21, 2001 at 7:57 am
Hi,
Thanks Andy for your post. I checked out the news groups and tried that suggestion without any luck. But, I was finally successfull yesterday. This is what I learned:
- The setup.ini file that I'm running has to include references to the actual instalation directories for TargetDir and DataDir, not necessarily the directories in the original INI (our users can change the install directory during the instal of our product). Makes perfect sense in retrospect :^)
- I had to include the line "UPGRADEUSER=sa " in my INI file and blank the sa password (I don't really like this much, but it worked). As in KB article Q303680.
- I had to install from the hard drive. If I tried to install from a CD part way through the install we would recieve a "Please insert the disk" message. No indication as to what disk it was looking for though, and it didn't seem to matter what disk we put in drives, the instalation wouldn't continue.
And, last but not least...I can't uninstall MSDE after installing SP2. I have to go in and manualy remove all the SQL Server references in the registry and then the uninstal will proceed. The error message is "Instance Name specified is invalid.", but I haven't specified an instance name (in either the install or the uninstall) and I have used the default. I've read a couple of KB articles about this one too, but no luck with any of the suggestions so far.
I must admit, this is the most counter intuitive instalation I've ever done, and the documentation is terrible. The idea of rolling out something this fragile makes me a little nervous.
Hope this helps others who are having issues.
Thanks again,
Bob
December 21, 2001 at 8:21 am
Thanks for the follow up. I agree, thats far more complicated than it should be. Might want to drop a line to sqlwish@microsoft.com, throw them suggestions for next time.
Andy
December 10, 2002 at 9:22 am
INFO: When to Choose MSDE 2000 as the Database Engine for Your Application
Http://support.microsoft.com/default.aspx?scid=kb;en-us;321518
Got this today in the daily MS Propaganda note. A good overview of the different SQL engines and how to move between them.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply