February 25, 2010 at 12:13 pm
Hi All,
I'm trying install sqlserver 2005 express on a windows 2003 server with .net framework 2.0. It installs fine and I can create the databases that we have in production. However when I try to upgrade it to the standard 2005 edition I encounter the following error:
------------------------------
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]RegCreateKeyEx() returned error 5, 'Access is denied.'. To continue, correct the problem, and then run SQL Server Setup again.
--------------------------------
And a link to Microsoft's "help" for this:
--------------------------------
--------------------------------
The server is a new clean install of Windows 2003 with SP 1.
Has anyone encountered any similar issues with this in an install ??? Apologies if it is obvious as I'm more suited to Oracle than Sqlserver. Many thanks in advance.
rgds,
Jay
February 25, 2010 at 1:50 pm
OK so maybe this is a silly question...
If this is a clean install why install the Express version then upgrade to standard. Why not just install Standard edition from the get go? Are you actually doing an upgrade or are you installing a second instance? In the ORacle world, are you upgrading or installing a new ora_home (at least I think that somewhat of an approximation from the last time I installed oracle 3+ years ago)?
It looks like the user you are using to run the install doesn't have access to one of the registry keys it needs to modify. Are you using an account with admin rights on the local machine to run the install?
-Luke.
February 25, 2010 at 2:58 pm
Hi Luke,
Reason for installing express first is so that I can run through the upgrade process before upgrading the production servers. I'm installing the upgrade to the same instance (in-place upgrade).
E:\setup.exe SKUUPDATE=1
There is only one windows user on the system, Administrator.
So that leaves me kind of baffled. I also believe that it has something to do with registry access also from other searches on the net. Any other ideas? Cheers.
rgds,
Jay
February 26, 2010 at 5:57 am
Is your production server part of a domain? IS your test server part of the same domain?
What user installed the express instance on the test machine, the local administrator or a domain user?
Same question for production.
Are you logging in as the local administrator or using your domain credentials?
When the Express instance was installed, did you download the installer from MS or was it part of a packaged product like Visual Studio or Sharepoint or some other such app?
Are you using the 32 bit versions of both products?
Also, are you trying to install a lower version like SQL Server Std RTM on top of Express SP3? That may also cause some issues, although I would think you'd get different error messages.
Another thing to look out for is SQL Server Manangement Studio Express. It can't be installed with the full blown SSMS that comes with SQL Standard.
-Luke.
February 26, 2010 at 6:57 am
I strongly suggest that you not even bother with Express. Just in stall Standard Edition and be done. There is actually no "Upgrade" from Express to any other version. You can install one over the other. But I would not take a chance with my data. Just install SQL Server and be done.
Keep things simple.
Andrew SQLDBA
February 26, 2010 at 9:01 am
Hi Luke,
Q1. Yes production is part of a domain....but i've not gone near that yet. No the test box is not even on a network much less
a domain.
Q2. Is there is only one user on the test server, it must (??) be the administrator. On the domain...hmmmm.....not entirly sure tbh
as i have inherited this......I can only assume it to be domain or Server admin....how would I know for sure ? (forgive me...pure unix head)
Q3. Test server not on netweork...so local admin. On domain....again not entirely sure....I assume it is the local admin.
Q4. Downloaded from MS website as well as the Management Studio.
Q5. Yes.
Q6. Nope.
Q7. Tried without installing the management tool and still same error.
Cheers Luke.
Hi Andrew,
Yes I see your point although my reasons for installing and then upgrading is that I would have to do this in a production
environment where the Express Edition is already installed. Makes more sense to me to test this first on a dev server before upsetting the Boss man.
Many thanks.
rgds,
Jay
February 26, 2010 at 9:06 am
No, you would want to un-install the Express edition first, do not try to "upgrade". That is the very best way to approach this issue.
You can create a backup of the databases, and then restore them on the prod box once SQL Server is installed.
Andrew SQLDBA
February 26, 2010 at 9:10 am
AndrewSQLDBA (2/26/2010)
No, you would want to un-install the Express edition first, do not try to "upgrade". That is the very best way to approach this issue.You can create a backup of the databases, and then restore them on the prod box once SQL Server is installed.
Andrew SQLDBA
I get what you are trying to say here Andrew, but it is quite possible to upgrade Express to Standard, it is also quite possible to have the two exist on the same machine at the same time. Doing it you way creates a need for a substantial amount of downtime. Depending on the DB and the needs of the business this might be a serious issue. Also he'd need to recreate all of his security, maintenance plans, and other such things that just "happen" when you do an in place upgrade...
Best for you might not be "best" for someone else's environment.
-Luke.
February 26, 2010 at 9:22 am
Jay,
I say there is probably something going on here with servicepack levels. The Express edition that you downloaded is most likely at SP3 if it was downloaded recently. Unless you have the standard edition that is bundled with SP3 it might be trying to go backwards then forwards although I would think that would cause a different error message.
I'm somewhat and the end of my rope on suggestions beyond that, but I think that this might be a covered issue with MS PSS (MS Product Support Service).
I might suggest another option that may/may not work for you depending on how your application is configured. I might look to do this as a side by side migration. Basically you install the Standard Edition on the same box to a different instance. Then you can script out your users/logins and such add them to the new instance, Once you verify that everything is exactly the same, you can detach the database from the express instance and re-attach it to eh Standard edition instance.
The only drawback to the above is that your instance name will change, which if Express was installed in it's default configuration is called SQLExpress so you might want to change it anyhow, but that all depends on how easy it will be to change your connections in your application(s).
-Luke.
February 26, 2010 at 9:26 am
AndrewSQLDBA (2/26/2010)
No, you would want to un-install the Express edition first, do not try to "upgrade". That is the very best way to approach this issue.You can create a backup of the databases, and then restore them on the prod box once SQL Server is installed.
Andrew SQLDBA
Hi Andrew,
I get what you are saying ref...backup to disk/tape.....detach DB's.....blow away the previous version and go with the new install etc. However, at this moment I'd find that approach a tad to aggressive for my liking.....simply due to the fact of the downtime required and that who is to say I might not get the same error whilst installing the standard edition. Thanks again....I'm sure that there is another way around this tho.
rgds,
Jay
February 26, 2010 at 9:30 am
Luke L (2/26/2010)
Jay,I say there is probably something going on here with servicepack levels. The Express edition that you downloaded is most likely at SP3 if it was downloaded recently. Unless you have the standard edition that is bundled with SP3 it might be trying to go backwards then forwards although I would think that would cause a different error message.
I'm somewhat and the end of my rope on suggestions beyond that, but I think that this might be a covered issue with MS PSS (MS Product Support Service).
I might suggest another option that may/may not work for you depending on how your application is configured. I might look to do this as a side by side migration. Basically you install the Standard Edition on the same box to a different instance. Then you can script out your users/logins and such add them to the new instance, Once you verify that everything is exactly the same, you can detach the database from the express instance and re-attach it to eh Standard edition instance.
The only drawback to the above is that your instance name will change, which if Express was installed in it's default configuration is called SQLExpress so you might want to change it anyhow, but that all depends on how easy it will be to change your connections in your application(s).
-Luke.
Nice one Luke.....the more options the better. I'll keep looking for now tho as I'm in no panic to upgrade based on these findings......for obvious reasons 😀 . Many thanks again.
rgds,
Jay
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply