SQL 2008 Upgrade Bug
- From: Lawrence Reed
- Date: Fri, 22 Jan 2010 12:16:26 -0800
I had a similar situation and after calling MS support it turns out there is a bug in the SISS that will prevent the upgrade of an expired evaluation edition. We had to uninstall the SISS and after that the upgrade ran flawlessly.
changli wrote:
Hi Mark,I performed a test on a DC at my side, however everything went fine
16-Oct-08
Hi Mark,
I performed a test on a DC at my side, however everything went fine and I did not reproduce your issue.
I am not sure if you have unintalled the SQL Server and then reinstalled it. Anyway I would like to summarize the steps of
the upgrade steps of mine and hope that it will help other community members.
1. Run SQL Server 2008 Upgrade Advisor to check if there are any issues that need your take action to resolve;
2. After you resolve all the found issues, run setup.exe from command line or directly run it via GUI to follow the setup
wizard to upgrade your SQL Server 2005 to 2008 .
3. Ensure that you specify a domain user for your SSIS service account during the upgrade process.
Appreciate your understanding that since this issue was environment specific, if you want to track the root cause of this
issue, dump analysis would be required. In this case I recommend that you contact Microsoft Customer Support Services
(CSS) via telephone for more dedicated support.
To obtain the phone numbers for specific technology request please take a look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for regional support phone numbers.
Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
=========================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
Previous Posts In This Thread:
On Wednesday, October 01, 2008 9:15 PM
Mark Olbert wrote:
Upgrade from 2005 to 2008: Invalid Credentials
My upgrade install of 2008 over 2005 had some failures, including the database engine services. So I tried a repair install, and it
keeps failing with an invalid credentials error:
TITLE: SQL Server Setup failure.
------------------------------
SQL Server Setup has encountered the following error:
The credentials you provided for the Integration Services service are invalid. To continue, provide a valid account and password for
the Integration Services service.
Error code 0x84B40000.
------------------------------
This is on a Server 2008 Standard platform. The box is also a domain controller (and yes, I know that's not recommended, but it's a
warning, not an error and I don't feel like shelling out the $$$ for yet another box).
What's weird about this is that, for fun, I tried logging in as the user that I had provided to Integration Services. I was able to
do that, no problem, so I know I'm using the correct password. Then I tried removing the user from the Domain Admin group; same
error.
I also checked that Integration Services was able to start and stop with the credentials I provided. No problem.
So....what the heck do I do?? I don't even see how I change the user credentials before initiating the repair install.
BTW, if it would help to post the output from the initial upgrade attempts error log -- the one that didn't install the database
engine services -- I'd be happy to do that.
- Mark
p.s. to Microsoft: not a good out of the box experience. And, I find it bizarre, what with all the tests, configuration checks, rule
checks, etc., that you made available -- and which I ran before doing the install -- a simple upgrade installation failed. Not to
mention failing with yet another unhelpful message.
On Thursday, October 02, 2008 3:02 AM
changli wrote:
Hi Mark,From your description, I understand that when you upgrade your SQL
Hi Mark,
From your description, I understand that when you upgrade your SQL Server 2005 to 2008, you encountered the error:"The credentials you provided for the Integration Services service are invalid. To continue, provide a valid account and password for the Integration Services service."
If I have misunderstood, please let me know.
According to my research, this seems to be a known issue for installing SQL Server 2008 on Domain Controller. Currently it has been reported to our product team and the root cause is still in
investigation. Based on the current status, it seems that this issue was related to NETWORK SERVICE account for SSIS service could not be validated on DC. By default SSIS uses NETWORK
SERVICES as its service account.
Please first go to your Services pane, double click your SQL Server Integration Services, switch to the Log On tab to check if the service account is NETWORK SERVICE account. If so, I
recommend that you first change you try the service account to a domain user account or a local user account and then upgrade your SQL Server 2005 to 2008 from command prompt.
For example:
========================================================
Setup.exe /q /ACTION=upgrade /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS" /RSUPGRADEDATABASEACCOUNT="<Provide a SQL Server logon
account that can connect to the report server during upgrade>" /RSUPGRADEPASSWORD="<Provide a password for the report server upgrade account>" /ISSVCAccount="<Provide a domain
user account for your integration service>" /ISVCPassword="<Provide the password for your domain user account for your integration service>"
=========================================================
For more information regarding install SQL Server 2008 from command prompt, please refer to this article:
How to: Install SQL Server 2008 from the Command Prompt
http://msdn.microsoft.com/en-us/library/ms144259.aspx
Hope this helps.
Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notifications.
Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
On Thursday, October 02, 2008 10:37 AM
Mark Olbert wrote:
Charles,Thanks for the quick and comprehensive reply.
Charles,
Thanks for the quick and comprehensive reply. I do have two questions, though:
1) Do I need to uninstall the broken installation first? FYI, after posting the first message I tried just doing a second upgrade
install, on top of the first, failed one. It only affected some ancillary things (e.g., books online).
2) I'm not that familiar with Reporting Services. WhenI installed it under SqlServer2005, I believe I used a Windows account and
Windows authentication for it. Does that make sense? If so, are those the account credentials I would supply?
As an aside, and again for Microsoft's benefit, "known installation problem on a domain controller" sounds to me like "nobody did an
install on a domain controller before releasing the product". Which means, at the very least, the warning about installation on a DC
needs to be an error. Of course, I suspect a lot of us who run small shops wish that Microsoft would stop releasing server software
that requires we buy additional machines. It's nice that they want to help Intel out, but it sure looks weird that Microsoft
products are incompatible with Microsoft products :).
- Mark
On Thu, 02 Oct 2008 07:02:18 GMT, changliw@xxxxxxxxxxxxxxxxxxxx ("Charles Wang [MSFT]") wrote:
On Thursday, October 02, 2008 12:00 PM
Mark Olbert wrote:
Charles,A couple of feedback items (I'm currently trying to get the
Charles,
A couple of feedback items (I'm currently trying to get the commandline upgrade process to work):
1) /ISVCPassword is incorrect, there's a missing 'S'. It should be /ISSVCPassword
2) Apparently, you can't specify the /SQLSYSADMINACCOUNTS option when you specify /ACTION=upgrade
setup completed, with no error messages. I rebooted the machine and all of the Sql Server services I expected to see running were
running...except for the database engine. It was marked as "Automatic" but wasn't running. I started it manually, but I'm not sure
why I had to do that.
However, now I can't connect to the server from Management Studio 2008. I get the following error:
TITLE: Connect to Server
------------------------------
Cannot connect to MAESTRO.
------------------------------
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was
not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
I'm attempting this on the server itself, so I don't understand the comment about needing to enable remote connections (I'm
accessing the server using remote desktop, in case that matters).
I went back to check the configuration, and noticed that the MSSQLSERVER service had stopped again. I restarted it, tried to connect
from Management Studio, got the same error, and found that the MSSQLSERVER service had stopped.
I checked the event logs with Event Viewer and saw the following installation-related errors:
Log Name: Application
Source: MSSQLSERVER
Date: 10/2/2008 8:53:06 AM
Event ID: 912
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: Maestro.arcabama.com
Description:
Script level upgrade for database 'master' failed because upgrade step 'sqlagent90_sysdbupg.sql' encountered error 598, state 1,
severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline.
If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine
the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script
upgrade steps run to completion.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event";>
<System>
<Provider Name="MSSQLSERVER" />
<EventID Qualifiers="49152">912</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-10-02T15:53:06.000Z" />
<EventRecordID>15253</EventRecordID>
<Channel>Application</Channel>
<Computer>Maestro.arcabama.com</Computer>
<Security />
</System>
<EventData>
<Data>master</Data>
<Data>sqlagent90_sysdbupg.sql</Data>
<Data>598</Data>
<Data>1</Data>
<Data>25</Data>
<Binary>9003000015000000080000004D00410045005300540052004F00000000000000</Binary>
</EventData>
</Event>
Something is seriously wrong somewhere. I'm going to try uninstalling everything, including SqlServer 2005, and do a fresh install
of 2008.
What a wonderful, wonderful upgrade experience. Does Microsoft actually test this stuff on real world systems before they release
it?
- Mark
On Thu, 02 Oct 2008 07:02:18 GMT, changliw@xxxxxxxxxxxxxxxxxxxx ("Charles Wang [MSFT]") wrote:
On Monday, October 06, 2008 6:47 AM
changli wrote:
Hi Mark,I am sorry for the typo error of missing an 'S' and the option
Hi Mark,
I am sorry for the typo error of missing an 'S' and the option /SQLSYSADMINACCOUNTS, however I am very glad to see that you did a great job here.
You said that you were going to fully uninstall SQL Server 2005 and then perform a fresh installation of SQL Server 2008. One thing I want to point out is that please change the SSIS service
account to a domain user account or a local user account instead of NETWORK SERVICE account, otherwise this issue still persists.
Regarding your concern, Does Microsoft actually test this stuff on real world systems before they release it?
Microsoft has identified this issue before, however its priority seems not very high and not added into the fix plan in the first release. I know that you are a senior developer and I believe that
you can understand this.
Thank you for your continously giving feedbacks to Microsoft. I belive that our products will be improved better and better with your contributions.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
=========================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
On Monday, October 06, 2008 6:53 AM
changli wrote:
Hi Mark,Regarding the other error message after you upgraded to SQL Server
Hi Mark,
Regarding the other error message after you upgraded to SQL Server 2008, I have submitted a request to our lab to establish a same environment as yours to perform a test. The process may
need two or three days, anyway I will let you know the result as soon as possible when I finshed it.
Thank you for your patience!
Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
=========================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
On Friday, October 10, 2008 8:35 AM
changli wrote:
Hi Mark,Sorry for delaying this response since I took a leave in the these two
Hi Mark,
Sorry for delaying this response since I took a leave in the these two days. I will reply you next Monday to let you know my test result on this issue.
Thank you!
Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
=========================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
On Thursday, October 16, 2008 4:09 AM
changli wrote:
Hi Mark,I performed a test on a DC at my side, however everything went fine
Hi Mark,
I performed a test on a DC at my side, however everything went fine and I did not reproduce your issue.
I am not sure if you have unintalled the SQL Server and then reinstalled it. Anyway I would like to summarize the steps of
the upgrade steps of mine and hope that it will help other community members.
1. Run SQL Server 2008 Upgrade Advisor to check if there are any issues that need your take action to resolve;
2. After you resolve all the found issues, run setup.exe from command line or directly run it via GUI to follow the setup
wizard to upgrade your SQL Server 2005 to 2008 .
3. Ensure that you specify a domain user for your SSIS service account during the upgrade process.
Appreciate your understanding that since this issue was environment specific, if you want to track the root cause of this
issue, dump analysis would be required. In this case I recommend that you contact Microsoft Customer Support Services
(CSS) via telephone for more dedicated support.
To obtain the phone numbers for specific technology request please take a look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for regional support phone numbers.
Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
=========================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
Submitted via EggHeadCafe - Software Developer Portal of Choice
Are you being FRAMED?
http://www.eggheadcafe.com/tutorials/aspnet/34e9de49-54ab-4b92-9e7b-0112a5e590db/are-you-being-framed.aspx
.
- Prev by Date: What happens after DTSWizard
- Next by Date: Error During Install Sql Server 2008 "Sql Server Setup requires .Net Framework 3.5"
- Previous by thread: What happens after DTSWizard
- Next by thread: Error During Install Sql Server 2008 "Sql Server Setup requires .Net Framework 3.5"
- Index(es):
Relevant Pages
|
