Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise editio
n ?
I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
prompted the following message after a few step.
"To change existing instance of SQL2005 to a different edition of SQL2005,
you must run SQL2005 Setup from the command prompt and include the
SKUUPGRADE=1 parameter".
Followed the instruction to run setup with the parameter, upgraded
successfully but it got error when I started SSMS.
"could not load file or assembly Microsoft.Sqlserver.Management.Reports,
Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one o
f
its dependencies. The system could not find the file specified."
End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
Looking forward to your advices.Hi
"Johnny" wrote:
> Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edit
ion ?
> I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> prompted the following message after a few step.
> "To change existing instance of SQL2005 to a different edition of SQL2005,
> you must run SQL2005 Setup from the command prompt and include the
> SKUUPGRADE=1 parameter".
> Followed the instruction to run setup with the parameter, upgraded
> successfully but it got error when I started SSMS.
> "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one
of
> its dependencies. The system could not find the file specified."
> End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> Looking forward to your advices.
You don't say what options you used on the command prompt, at a guess you
didn't specify UPGRADE=SQL_Engine as shown in the example on
http://msdn2.microsoft.com/en-us/li...aspx#skuupgrade and have
also upgraded the tools as well, which for some reason didn't work?
You could have re-installed the tools on their own using the reinstallmode
parameter
http://msdn2.microsoft.com/en-us/li...x#reinstallmode and the
ADDLOCAL parameter set to the Client_components
You will now need to re-apply service pack 2 and subsequent hotfixes.
John|||Hi John,
I wish to clarify that upgrading the edition has to specify
UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
the client tools is no need for the edition upgrade (only sql_engine is
required.)
Johnny
"John Bell" wrote:
> Hi
> "Johnny" wrote:
>
> You don't say what options you used on the command prompt, at a guess you
> didn't specify UPGRADE=SQL_Engine as shown in the example on
> http://msdn2.microsoft.com/en-us/li...aspx#skuupgrade and have
> also upgraded the tools as well, which for some reason didn't work?
> You could have re-installed the tools on their own using the reinstallmode
> parameter
> http://msdn2.microsoft.com/en-us/li...x#reinstallmode and t
he
> ADDLOCAL parameter set to the Client_components
> You will now need to re-apply service pack 2 and subsequent hotfixes.
> John|||Hi
"Johnny" wrote:
> Hi John,
> I wish to clarify that upgrading the edition has to specify
> UPGRADE=SQL_ENGINE as well which I did not specify before. That means tha
t
> the client tools is no need for the edition upgrade (only sql_engine is
> required.)
> Johnny
> "John Bell" wrote:
Had you service packed the original installation, and were they re-applied
after the upgrade?
John|||Applied the service pack 2 before and after the edition upgrade.
Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
well for edition upgrade, isn't it ?
Ta.
"John Bell" wrote:
> Hi
> "Johnny" wrote:
>
> Had you service packed the original installation, and were they re-applied
> after the upgrade?
> John
>|||Hi
"Johnny" wrote:
> Applied the service pack 2 before and after the edition upgrade.
> Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
> well for edition upgrade, isn't it ?
> Ta.
>
I believe so, but I have not found anywhere to confirm this.
John
Showing posts with label loaded. Show all posts
Showing posts with label loaded. Show all posts
Friday, March 23, 2012
Migrate SQL2005 from Standard to Enterprise edition
Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
prompted the following message after a few step.
"To change existing instance of SQL2005 to a different edition of SQL2005,
you must run SQL2005 Setup from the command prompt and include the
SKUUPGRADE=1 parameter".
Followed the instruction to run setup with the parameter, upgraded
successfully but it got error when I started SSMS.
"could not load file or assembly Microsoft.Sqlserver.Management.Reports,
Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
its dependencies. The system could not find the file specified."
End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
Looking forward to your advices.
Hi
"Johnny" wrote:
> Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
> I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> prompted the following message after a few step.
> "To change existing instance of SQL2005 to a different edition of SQL2005,
> you must run SQL2005 Setup from the command prompt and include the
> SKUUPGRADE=1 parameter".
> Followed the instruction to run setup with the parameter, upgraded
> successfully but it got error when I started SSMS.
> "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
> its dependencies. The system could not find the file specified."
> End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> Looking forward to your advices.
You don't say what options you used on the command prompt, at a guess you
didn't specify UPGRADE=SQL_Engine as shown in the example on
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
also upgraded the tools as well, which for some reason didn't work?
You could have re-installed the tools on their own using the reinstallmode
parameter
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
ADDLOCAL parameter set to the Client_components
You will now need to re-apply service pack 2 and subsequent hotfixes.
John
|||Hi John,
I wish to clarify that upgrading the edition has to specify
UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
the client tools is no need for the edition upgrade (only sql_engine is
required.)
Johnny
"John Bell" wrote:
> Hi
> "Johnny" wrote:
>
> You don't say what options you used on the command prompt, at a guess you
> didn't specify UPGRADE=SQL_Engine as shown in the example on
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
> also upgraded the tools as well, which for some reason didn't work?
> You could have re-installed the tools on their own using the reinstallmode
> parameter
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
> ADDLOCAL parameter set to the Client_components
> You will now need to re-apply service pack 2 and subsequent hotfixes.
> John
|||Hi
"Johnny" wrote:
> Hi John,
> I wish to clarify that upgrading the edition has to specify
> UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
> the client tools is no need for the edition upgrade (only sql_engine is
> required.)
> Johnny
> "John Bell" wrote:
Had you service packed the original installation, and were they re-applied
after the upgrade?
John
|||Applied the service pack 2 before and after the edition upgrade.
Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
well for edition upgrade, isn't it ?
Ta.
"John Bell" wrote:
> Hi
> "Johnny" wrote:
>
> Had you service packed the original installation, and were they re-applied
> after the upgrade?
> John
>
|||Hi
"Johnny" wrote:
> Applied the service pack 2 before and after the edition upgrade.
> Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
> well for edition upgrade, isn't it ?
> Ta.
>
I believe so, but I have not found anywhere to confirm this.
John
I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
prompted the following message after a few step.
"To change existing instance of SQL2005 to a different edition of SQL2005,
you must run SQL2005 Setup from the command prompt and include the
SKUUPGRADE=1 parameter".
Followed the instruction to run setup with the parameter, upgraded
successfully but it got error when I started SSMS.
"could not load file or assembly Microsoft.Sqlserver.Management.Reports,
Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
its dependencies. The system could not find the file specified."
End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
Looking forward to your advices.
Hi
"Johnny" wrote:
> Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
> I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> prompted the following message after a few step.
> "To change existing instance of SQL2005 to a different edition of SQL2005,
> you must run SQL2005 Setup from the command prompt and include the
> SKUUPGRADE=1 parameter".
> Followed the instruction to run setup with the parameter, upgraded
> successfully but it got error when I started SSMS.
> "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
> its dependencies. The system could not find the file specified."
> End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> Looking forward to your advices.
You don't say what options you used on the command prompt, at a guess you
didn't specify UPGRADE=SQL_Engine as shown in the example on
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
also upgraded the tools as well, which for some reason didn't work?
You could have re-installed the tools on their own using the reinstallmode
parameter
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
ADDLOCAL parameter set to the Client_components
You will now need to re-apply service pack 2 and subsequent hotfixes.
John
|||Hi John,
I wish to clarify that upgrading the edition has to specify
UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
the client tools is no need for the edition upgrade (only sql_engine is
required.)
Johnny
"John Bell" wrote:
> Hi
> "Johnny" wrote:
>
> You don't say what options you used on the command prompt, at a guess you
> didn't specify UPGRADE=SQL_Engine as shown in the example on
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
> also upgraded the tools as well, which for some reason didn't work?
> You could have re-installed the tools on their own using the reinstallmode
> parameter
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
> ADDLOCAL parameter set to the Client_components
> You will now need to re-apply service pack 2 and subsequent hotfixes.
> John
|||Hi
"Johnny" wrote:
> Hi John,
> I wish to clarify that upgrading the edition has to specify
> UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
> the client tools is no need for the edition upgrade (only sql_engine is
> required.)
> Johnny
> "John Bell" wrote:
Had you service packed the original installation, and were they re-applied
after the upgrade?
John
|||Applied the service pack 2 before and after the edition upgrade.
Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
well for edition upgrade, isn't it ?
Ta.
"John Bell" wrote:
> Hi
> "Johnny" wrote:
>
> Had you service packed the original installation, and were they re-applied
> after the upgrade?
> John
>
|||Hi
"Johnny" wrote:
> Applied the service pack 2 before and after the edition upgrade.
> Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
> well for edition upgrade, isn't it ?
> Ta.
>
I believe so, but I have not found anywhere to confirm this.
John
Migrate SQL2005 from Standard to Enterprise edition
Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
prompted the following message after a few step.
"To change existing instance of SQL2005 to a different edition of SQL2005,
you must run SQL2005 Setup from the command prompt and include the
SKUUPGRADE=1 parameter".
Followed the instruction to run setup with the parameter, upgraded
successfully but it got error when I started SSMS.
"could not load file or assembly Microsoft.Sqlserver.Management.Reports,
Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
its dependencies. The system could not find the file specified."
End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
Looking forward to your advices.Hi
"Johnny" wrote:
> Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
> I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> prompted the following message after a few step.
> "To change existing instance of SQL2005 to a different edition of SQL2005,
> you must run SQL2005 Setup from the command prompt and include the
> SKUUPGRADE=1 parameter".
> Followed the instruction to run setup with the parameter, upgraded
> successfully but it got error when I started SSMS.
> "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
> its dependencies. The system could not find the file specified."
> End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> Looking forward to your advices.
You don't say what options you used on the command prompt, at a guess you
didn't specify UPGRADE=SQL_Engine as shown in the example on
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
also upgraded the tools as well, which for some reason didn't work?
You could have re-installed the tools on their own using the reinstallmode
parameter
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
ADDLOCAL parameter set to the Client_components
You will now need to re-apply service pack 2 and subsequent hotfixes.
John|||Hi John,
I wish to clarify that upgrading the edition has to specify
UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
the client tools is no need for the edition upgrade (only sql_engine is
required.)
Johnny
"John Bell" wrote:
> Hi
> "Johnny" wrote:
> > Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
> >
> > I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> > prompted the following message after a few step.
> >
> > "To change existing instance of SQL2005 to a different edition of SQL2005,
> > you must run SQL2005 Setup from the command prompt and include the
> > SKUUPGRADE=1 parameter".
> >
> > Followed the instruction to run setup with the parameter, upgraded
> > successfully but it got error when I started SSMS.
> >
> > "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> > Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
> > its dependencies. The system could not find the file specified."
> >
> > End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> > Looking forward to your advices.
> You don't say what options you used on the command prompt, at a guess you
> didn't specify UPGRADE=SQL_Engine as shown in the example on
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
> also upgraded the tools as well, which for some reason didn't work?
> You could have re-installed the tools on their own using the reinstallmode
> parameter
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
> ADDLOCAL parameter set to the Client_components
> You will now need to re-apply service pack 2 and subsequent hotfixes.
> John|||Hi
"Johnny" wrote:
> Hi John,
> I wish to clarify that upgrading the edition has to specify
> UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
> the client tools is no need for the edition upgrade (only sql_engine is
> required.)
> Johnny
> "John Bell" wrote:
Had you service packed the original installation, and were they re-applied
after the upgrade?
John|||Applied the service pack 2 before and after the edition upgrade.
Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
well for edition upgrade, isn't it ?
Ta.
"John Bell" wrote:
> Hi
> "Johnny" wrote:
> > Hi John,
> >
> > I wish to clarify that upgrading the edition has to specify
> > UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
> > the client tools is no need for the edition upgrade (only sql_engine is
> > required.)
> >
> > Johnny
> > "John Bell" wrote:
> Had you service packed the original installation, and were they re-applied
> after the upgrade?
> John
>|||Hi
"Johnny" wrote:
> Applied the service pack 2 before and after the edition upgrade.
> Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
> well for edition upgrade, isn't it ?
> Ta.
>
I believe so, but I have not found anywhere to confirm this.
Johnsql
I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
prompted the following message after a few step.
"To change existing instance of SQL2005 to a different edition of SQL2005,
you must run SQL2005 Setup from the command prompt and include the
SKUUPGRADE=1 parameter".
Followed the instruction to run setup with the parameter, upgraded
successfully but it got error when I started SSMS.
"could not load file or assembly Microsoft.Sqlserver.Management.Reports,
Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
its dependencies. The system could not find the file specified."
End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
Looking forward to your advices.Hi
"Johnny" wrote:
> Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
> I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> prompted the following message after a few step.
> "To change existing instance of SQL2005 to a different edition of SQL2005,
> you must run SQL2005 Setup from the command prompt and include the
> SKUUPGRADE=1 parameter".
> Followed the instruction to run setup with the parameter, upgraded
> successfully but it got error when I started SSMS.
> "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
> its dependencies. The system could not find the file specified."
> End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> Looking forward to your advices.
You don't say what options you used on the command prompt, at a guess you
didn't specify UPGRADE=SQL_Engine as shown in the example on
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
also upgraded the tools as well, which for some reason didn't work?
You could have re-installed the tools on their own using the reinstallmode
parameter
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
ADDLOCAL parameter set to the Client_components
You will now need to re-apply service pack 2 and subsequent hotfixes.
John|||Hi John,
I wish to clarify that upgrading the edition has to specify
UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
the client tools is no need for the edition upgrade (only sql_engine is
required.)
Johnny
"John Bell" wrote:
> Hi
> "Johnny" wrote:
> > Has anyone tried to migrate SQL2005 from Standard (SP2) to Enterprise edition ?
> >
> > I have trouble with it. I loaded the SQL2005 Enterprise edition CD, it
> > prompted the following message after a few step.
> >
> > "To change existing instance of SQL2005 to a different edition of SQL2005,
> > you must run SQL2005 Setup from the command prompt and include the
> > SKUUPGRADE=1 parameter".
> >
> > Followed the instruction to run setup with the parameter, upgraded
> > successfully but it got error when I started SSMS.
> >
> > "could not load file or assembly Microsoft.Sqlserver.Management.Reports,
> > Version=9.0.242.0, Culture=Nature, PublicKeyToken=89845dcd8080cc91' or one of
> > its dependencies. The system could not find the file specified."
> >
> > End up, I got to uninstall SQL2005 and reinstall with Enterprise Edition.
> > Looking forward to your advices.
> You don't say what options you used on the command prompt, at a guess you
> didn't specify UPGRADE=SQL_Engine as shown in the example on
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#skuupgrade and have
> also upgraded the tools as well, which for some reason didn't work?
> You could have re-installed the tools on their own using the reinstallmode
> parameter
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode and the
> ADDLOCAL parameter set to the Client_components
> You will now need to re-apply service pack 2 and subsequent hotfixes.
> John|||Hi
"Johnny" wrote:
> Hi John,
> I wish to clarify that upgrading the edition has to specify
> UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
> the client tools is no need for the edition upgrade (only sql_engine is
> required.)
> Johnny
> "John Bell" wrote:
Had you service packed the original installation, and were they re-applied
after the upgrade?
John|||Applied the service pack 2 before and after the edition upgrade.
Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
well for edition upgrade, isn't it ?
Ta.
"John Bell" wrote:
> Hi
> "Johnny" wrote:
> > Hi John,
> >
> > I wish to clarify that upgrading the edition has to specify
> > UPGRADE=SQL_ENGINE as well which I did not specify before. That means that
> > the client tools is no need for the edition upgrade (only sql_engine is
> > required.)
> >
> > Johnny
> > "John Bell" wrote:
> Had you service packed the original installation, and were they re-applied
> after the upgrade?
> John
>|||Hi
"Johnny" wrote:
> Applied the service pack 2 before and after the edition upgrade.
> Back to my previous question. I needed to specify UPGRADE=SQL_ENGINE as
> well for edition upgrade, isn't it ?
> Ta.
>
I believe so, but I have not found anywhere to confirm this.
Johnsql
Wednesday, March 7, 2012
Microsoft Visual Studio is unable to load this document after SQL Server SP2 install.
Hello all,
Over the weekend, I loaded the SQL Server SP2 on to my production database after having it on my dev server for two weeks with out any problems.
After I did this, I went to check all my SSIS packages and found them not able to load.
I get this message “Microsoft Visual Studio is unable to load this document: The package failed to load due to error 0xC0010014 “One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors”. This occurs when CPackage::LoadFromXML fails.
Now when I look at the errors I see:
Error 1 Error loading Master_Full_Weekly.dtsx: Error loading value "<DTS:LogProvider xmlns : DTS="www.microsoft.com/SqlServer/Dts" > <DTS : Property DTS:Name="ConfigString">SQL_TPMTSH_Datamart</DTS: Property><DTS : Property DTS:Name="DelayValidation">0</DTS: Property><DTS: Property DTS:Name="ObjectName">DTS Log Provider for SQL Serve" from node "DTS: LogProvider". D:\ETL\Projects\TPM\TPMTSH\Master_Full_Weekly.dtsx 1 1
Does anyone know what this is about and how I can go about fixing it?Anyone?|||
Could you try to register xml modules:
regsvr32 msxml3.dll
regsvr32 msxml6.dll
HTH.
Subscribe to:
Posts (Atom)