MSDE 2000 installation on XP

We're having trouble installing MSDE 2000 on two machines here. They were Win98, upgraded to XP Professional using the upgrade CD labelled 'version 2002'. If we run MSDE installation the routine goes virtually to the end, then the progress bar runs backwards down to zero and the product is not installed. As an experiment we installed XP Pro from a full install (as opposed to upgrade) CD and then ran the MSDE installation, and it worked just fine on the same machine. Problem is we've sold these as XP Pro upgrades and so we don't have keys to install full version for the customer. The verbose log informs me that the installation failed but not clearly why (there's almost 3.5Mb of it).

I realise this might not be enough for anyone to help, but I was hoping that the reverse progress bar might be something someone else has experienced. The machines are Celeron 700 or 766, one has 64Mb the other has 128Mb, 20Gb HDDs with plenty (>18Gb) available. All ideas greatly appreciated.The following article addresses your issue:

MSDN Article (http://support.microsoft.com/default.aspx?scid=kb;EN-US;q313939)

Good luck.|||Thank you very much. I'll try that out - looks like it will do the trick as we didn't specifically have file and print sharing loaded.|||Originally posted by theosgb
Thank you very much. I'll try that out - looks like it will do the trick as we didn't specifically have file and print sharing loaded.

We had the same problem here. Once we ran lodctr /r:PrefStringBackup.ini we were able to install the software.|||Hi,
Would you please give me more details on this command.
Your immidiate response is truly appreciated.
Kal

Originally posted by csturgeon
We had the same problem here. Once we ran lodctr /r:PrefStringBackup.ini we were able to install the software.|||I found info on lodctr /r:PrefStringBackup.ini at this URL I don't see how it relates to an XP install problem. It appears to relate to an MSDE install problem on all NT OSes. But, I did NOT read all it said.

Tim S

http://support.microsoft.com/default.aspx?scid=kb;en-us;315083|||Originally posted by TimS
I found info on lodctr /r:PrefStringBackup.ini at this URL I don't see how it relates to an XP install problem. It appears to relate to an MSDE install problem on all NT OSes. But, I did NOT read all it said.

Tim S

http://support.microsoft.com/default.aspx?scid=kb;en-us;315083

We have found that when a user upgrades from 98/ME to XP. the performance counters get messed up. Once the counters are gone, MSDE will not go on. Running this command reset the counters thereby allowing MSDE to be installed.|||I got past the install after running the LODCTR command and then enabling File and Print Sharing. THANK you guys for all the help .

Best regards,
Kal

Msde 2000 - Sql 2005 Express Upgrade Issue.

Hey, This is my first time posting here but here goes nothing...

Ok I upgraded an xp machine running to sql express 2005 by doing the inplace upgrade. The upgrade process went great, after the upgrade I could connect to the databases that had been upgraded using the management studio.

BUT.

When I try to connect to the databases using the third party software which had always worked in the past I get the error when trying to access from both the client and server machines.

[DBNETLIB][Connection open()).]SQL Server does not exist or access denied.

I then tried setting up SQL express 2005 on another xp station just to test how things worked if it wasn't an upgrade. I installed, attached the databases (which I copied to that local machine) and I was able to connect to them through the third party software from the server machine, but not client machines. The client machines gave me the same error as above.

Does anyone have any ideas, I have been talking to the third party support but haven't gotten any where yet... does anyone have any suggestions?

Thanks,why would you want to upgrade from MSDE 2000 to SQL 2005 express? Microsoft has stated more than 80% of the application running on SQL 2000 will not work on SQL 2005. Why not using the same old MSDE 2000?

most probably you will need to rewrite your application to handle SQL 2005|||I spoke with the third party software company and they assure me everything will work on sql express. We wanted to switch to sql express because it had the report server stuff built in. I don't really know that much about this stuff, can the sql 2005 express reporting stuff be run on msde ?|||I am not the expert here but I will just share what I have experienced so far.

Report server is a built in feature in SQL 2005. However, it has its limitation when it comes to report designer. My personal experience, it's easy to use, but it's not acceptable by the end user. I end up writing my own long script to output the whole report to excel file.

You shall show your users instead of simply pushing them to another technology. MSDE can run well on WinXP, so why change? If you can't give yourself a good reason to change, it's better to stick to something that's working.

Remember, free stuff, doesn't come in handy :D unless your requirement is very very simple.

If the software vendor assure you that, ask them to show you how to migrate the thing over. You can always use VMware or Parallels to do all the testing before you screw up your MSDE.|||Thanks for the insight with the reporting stuff. Do you know if the report stuff from express can be used with msde?

Also, I think it's to late for me on the screwing up the msde. I removed sql express now and I have reinstalled msde, but I am getting the same error I was getting with the express. I have done a little reading and it seems like it might be a problem with remote connections. Does anyone know how to make sure remote connections are allowed in msde ?sql

MSDB Permissions Error

Hi,
We've just upgraded a server to a new box and copied all of the settings
from the existing box. We are running a VB client front end, with COM+ as
middle tier and SQL Server 2000 as BE.
The COM+ account is running under a windows domain account (which is also in
the local server administrators group), but all connections to the SQL Serve
r
database are under an SQL login 'AppUser'.
We are just testing the new configuration but are getting all sorts of
errors in the VB client FE. First of all, the FE tries to submit a job and
received error
'SELECT permission denied on msdb.sysjobs'
Does anyone know the cause of this error. As far as I can see, all of the
permissions on our new server are the same as the previous server' The logi
n
AppUser seems to be in all the correct groups.
(Just for testing purposes, I've made 'AppUser' part of the db_owner
database role in both these databases which of course fixes the above errors
.
But I do not want to leave it like this!!)
Any advice appreciated
ThanksHas the guest account been disabled in the msdb database. In the msdb
database, in Query Analyzer run the following command :
Select * from sysusers where name = 'guest'
Check the hasdbaccess column. It should be 1. If not run the following in
the msdb database:
sp_grantdbaccess 'guest'
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hi Rand,
Thanks for response, i ran the SQL & 'hasdbaccess' column is flagged as 1.
Any other possibilities to check...?
Thanks
Dylan|||Check the permissions of the public role in the database.
Rand
This posting is provided "as is" with no warranties and confers no rights.