Problems Installing SQL Server when CTP was previously installed

If you are having problems installing SQL Server, including Express Edition, and you previously installed one of the Community Technology Preview (CTP) releases, then read on...

Please provide feedback if any of these steps are confusing.

--

Note that if the user already has .NET Framework on their machine, they're going to have to go back to an earlier version, do the SQL Uninstall, then go forward to the RTM version.

Please look at the %Program Files%\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup*_Core.log file. It should have a bit of
information in it saying what the conflict is and some GUIDs indicating
the product codes of the conflicting programs. The section you are looking
for will look something like this (and may repeat):
Running: PerformSCCAction2 at: 2004/6/27 13:54:12
Product "{982DB00A-9C4E-436B-8707-18E113BAA44C}" versioned
9.00.823 is not compatible with current builds of SQL
Server.Expected at least version: 9.00.849
The Product Name is "Microsoft SQL Server 2005 Analysis
Services Beta 2"
In this case, the offending product is “Microsoft SQL Server 2005 Analysis Services Beta 2" with a product code of "{982DB00A-9C4E-436B-8707-18E113BAA44C}"
If the programs are still visible in the Add/Remove Programs control panel (ARP),
please remove them in the order specified by the readme file.

If they are not in ARP, please run the following steps:
Assuming you still have the media for the old build,
1/ Uninstall the current SQL Support files.
2/ Uninstall the current SQL Native Client (SNAC)
3/ Uninstall the current .NET Frameworks 2.0
4/ Run the old setup.exe up until it starts asking you what you want to install
(let it install SNAC and .NET), then exit setup.
5/ (**Skip this step for: SNAC, SQL Support Files and .NET Frameworks 2.0) run "msiexec /x {ProductGUID} /l*v c:\logfile.txt" for each of the ProductGUIDs listed in your Core log file from above.

Assuming that succeeds,
6/ Uninstall SQL Support Files
7/ Uninstall SQL Native Client
8/ Uninstall .NET Frameworks 2.0
9/ Install the RTM product.
--

Wow!

Would it not be easier/faster to
1) backup schemas
2) backup data
3) wipe system clean
4) install OS
5) install RTM?|||left out two most important steps
6) restore schema
7) restore data

Problems installing SQL Server 2005

I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
mistake of uninstalling the Visual Studio CTP "first". After uninstalling it,
I was able to complete the installation of the "released" version of Visual
Studio. During the install, I did receive a few error messages about SQL
Server but proceeded with the install. VS completed its installation and
appears to OK.
However, whe I treid to continue with the SQL Server 2005 installation, my
real problems started. First, I had to "uninstall" the CTP components. I
started with "Add/Remove Programs" but the only SQL CTP components that were
listed would NOT uninstall. In fact, trying to uninstall them just resulted
in their entries disappearing from the "Add/Remove Programs" list. There is
nothing left in that list related to the VS or SQL CTP programs.
I was then able to install the SQL 2005 "native client" successfully but
cannot install SQL 2005 itself. I receive an error that "beta" compoents were
detected and must be removed before installing SQL 2005. I cannot uninstall
them through "Add/Remove Programs" so it looks like they'll have to be
uninstalled manually, assuming this is doable, of course. I have no idea how
to accomplish this.
Any help with removing the SQL Server 2005 Apr CTP components and/or
proceeding with the SQL 2005 installation would be "greatly" appreciated.
Thank you.
Denis W. Repke
Try running this MS uninstall utility...should do the trick for you.
http://go.microsoft.com/fwlink/?LinkId=47598
|||Gregg,
Thanks for the quick reply. However...
Doesn't this program just uninstall the Visual Studio components? If so,
that's not my problem.
I have already uninstalled all of the Visual Studio CTP components and
completed installation of the Visual Studio 2005 "released" version. My
problem is removing the SQL Server 2005 CTP components so that I can install
the "released" version of SQL Server 2005. I cannot do this using "Add/Remove
Programs".
Denis W. Repke
"Gregg Walker" wrote:

> Try running this MS uninstall utility...should do the trick for you.
> http://go.microsoft.com/fwlink/?LinkId=47598
>
>
|||Denis,
Given what you have done I think you need to go back a step in order
to have a chance of going forward successfully.
I suggest you do the following:
1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
it fairly straightforwardly)
2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
you could re-install it and try to uninstall April CTP components
using Add/Remove Programs.
3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
See http://support.microsoft.com/default...b;en-us;290301 for
further information. It's wise to back up important files.
4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
then install SQL Server 2005 RTM (it should be installed before Visual
Studio). This is the moment of truth - if SQL Server RTM installs
cleanly you should be in good shape to go on to Step 5.
5. Install Visual Studio 2005 RTM again.
Good luck.
Andrew Watt
MVP - InfoPath
On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
<DenisRepke@.discussions.microsoft.com> wrote:

>I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
>Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
>mistake of uninstalling the Visual Studio CTP "first". After uninstalling it,
>I was able to complete the installation of the "released" version of Visual
>Studio. During the install, I did receive a few error messages about SQL
>Server but proceeded with the install. VS completed its installation and
>appears to OK.
>However, whe I treid to continue with the SQL Server 2005 installation, my
>real problems started. First, I had to "uninstall" the CTP components. I
>started with "Add/Remove Programs" but the only SQL CTP components that were
>listed would NOT uninstall. In fact, trying to uninstall them just resulted
>in their entries disappearing from the "Add/Remove Programs" list. There is
>nothing left in that list related to the VS or SQL CTP programs.
>I was then able to install the SQL 2005 "native client" successfully but
>cannot install SQL 2005 itself. I receive an error that "beta" compoents were
>detected and must be removed before installing SQL 2005. I cannot uninstall
>them through "Add/Remove Programs" so it looks like they'll have to be
>uninstalled manually, assuming this is doable, of course. I have no idea how
>to accomplish this.
>Any help with removing the SQL Server 2005 Apr CTP components and/or
>proceeding with the SQL 2005 installation would be "greatly" appreciated.
>Thank you.
|||Andrew,
I guess I'll have to try your suggestions. Nothing else is working. I did
also try running the "build unistall" program from the Sept CTP. That did NOT
work. Thanks for the help.
Denis W. Repke
"Andrew Watt [MVP - InfoPath]" wrote:

> Denis,
> Given what you have done I think you need to go back a step in order
> to have a chance of going forward successfully.
> I suggest you do the following:
> 1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
> it fairly straightforwardly)
> 2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
> you could re-install it and try to uninstall April CTP components
> using Add/Remove Programs.
> 3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
> See http://support.microsoft.com/default...b;en-us;290301 for
> further information. It's wise to back up important files.
> 4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
> then install SQL Server 2005 RTM (it should be installed before Visual
> Studio). This is the moment of truth - if SQL Server RTM installs
> cleanly you should be in good shape to go on to Step 5.
> 5. Install Visual Studio 2005 RTM again.
> Good luck.
> Andrew Watt
> MVP - InfoPath
> On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
> <DenisRepke@.discussions.microsoft.com> wrote:
>
>

Problems installing SQL Server 2005

I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
mistake of uninstalling the Visual Studio CTP "first". After uninstalling it,
I was able to complete the installation of the "released" version of Visual
Studio. During the install, I did receive a few error messages about SQL
Server but proceeded with the install. VS completed its installation and
appears to OK.
However, whe I treid to continue with the SQL Server 2005 installation, my
real problems started. First, I had to "uninstall" the CTP components. I
started with "Add/Remove Programs" but the only SQL CTP components that were
listed would NOT uninstall. In fact, trying to uninstall them just resulted
in their entries disappearing from the "Add/Remove Programs" list. There is
nothing left in that list related to the VS or SQL CTP programs.
I was then able to install the SQL 2005 "native client" successfully but
cannot install SQL 2005 itself. I receive an error that "beta" compoents were
detected and must be removed before installing SQL 2005. I cannot uninstall
them through "Add/Remove Programs" so it looks like they'll have to be
uninstalled manually, assuming this is doable, of course. I have no idea how
to accomplish this.
Any help with removing the SQL Server 2005 Apr CTP components and/or
proceeding with the SQL 2005 installation would be "greatly" appreciated.
Thank you.
--
Denis W. RepkeTry running this MS uninstall utility...should do the trick for you.
http://go.microsoft.com/fwlink/?LinkId=47598|||Gregg,
Thanks for the quick reply. However...
Doesn't this program just uninstall the Visual Studio components? If so,
that's not my problem.
I have already uninstalled all of the Visual Studio CTP components and
completed installation of the Visual Studio 2005 "released" version. My
problem is removing the SQL Server 2005 CTP components so that I can install
the "released" version of SQL Server 2005. I cannot do this using "Add/Remove
Programs".
--
Denis W. Repke
"Gregg Walker" wrote:
> Try running this MS uninstall utility...should do the trick for you.
> http://go.microsoft.com/fwlink/?LinkId=47598
>
>|||Denis,
Given what you have done I think you need to go back a step in order
to have a chance of going forward successfully.
I suggest you do the following:
1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
it fairly straightforwardly)
2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
you could re-install it and try to uninstall April CTP components
using Add/Remove Programs.
3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
See http://support.microsoft.com/default.aspx?scid=kb;en-us;290301 for
further information. It's wise to back up important files.
4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
then install SQL Server 2005 RTM (it should be installed before Visual
Studio). This is the moment of truth - if SQL Server RTM installs
cleanly you should be in good shape to go on to Step 5.
5. Install Visual Studio 2005 RTM again.
Good luck.
Andrew Watt
MVP - InfoPath
On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
<DenisRepke@.discussions.microsoft.com> wrote:
>I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
>Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
>mistake of uninstalling the Visual Studio CTP "first". After uninstalling it,
>I was able to complete the installation of the "released" version of Visual
>Studio. During the install, I did receive a few error messages about SQL
>Server but proceeded with the install. VS completed its installation and
>appears to OK.
>However, whe I treid to continue with the SQL Server 2005 installation, my
>real problems started. First, I had to "uninstall" the CTP components. I
>started with "Add/Remove Programs" but the only SQL CTP components that were
>listed would NOT uninstall. In fact, trying to uninstall them just resulted
>in their entries disappearing from the "Add/Remove Programs" list. There is
>nothing left in that list related to the VS or SQL CTP programs.
>I was then able to install the SQL 2005 "native client" successfully but
>cannot install SQL 2005 itself. I receive an error that "beta" compoents were
>detected and must be removed before installing SQL 2005. I cannot uninstall
>them through "Add/Remove Programs" so it looks like they'll have to be
>uninstalled manually, assuming this is doable, of course. I have no idea how
>to accomplish this.
>Any help with removing the SQL Server 2005 Apr CTP components and/or
>proceeding with the SQL 2005 installation would be "greatly" appreciated.
>Thank you.|||Andrew,
I guess I'll have to try your suggestions. Nothing else is working. I did
also try running the "build unistall" program from the Sept CTP. That did NOT
work. Thanks for the help.
--
Denis W. Repke
"Andrew Watt [MVP - InfoPath]" wrote:
> Denis,
> Given what you have done I think you need to go back a step in order
> to have a chance of going forward successfully.
> I suggest you do the following:
> 1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
> it fairly straightforwardly)
> 2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
> you could re-install it and try to uninstall April CTP components
> using Add/Remove Programs.
> 3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
> See http://support.microsoft.com/default.aspx?scid=kb;en-us;290301 for
> further information. It's wise to back up important files.
> 4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
> then install SQL Server 2005 RTM (it should be installed before Visual
> Studio). This is the moment of truth - if SQL Server RTM installs
> cleanly you should be in good shape to go on to Step 5.
> 5. Install Visual Studio 2005 RTM again.
> Good luck.
> Andrew Watt
> MVP - InfoPath
> On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
> <DenisRepke@.discussions.microsoft.com> wrote:
> >I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
> >Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
> >mistake of uninstalling the Visual Studio CTP "first". After uninstalling it,
> >I was able to complete the installation of the "released" version of Visual
> >Studio. During the install, I did receive a few error messages about SQL
> >Server but proceeded with the install. VS completed its installation and
> >appears to OK.
> >
> >However, whe I treid to continue with the SQL Server 2005 installation, my
> >real problems started. First, I had to "uninstall" the CTP components. I
> >started with "Add/Remove Programs" but the only SQL CTP components that were
> >listed would NOT uninstall. In fact, trying to uninstall them just resulted
> >in their entries disappearing from the "Add/Remove Programs" list. There is
> >nothing left in that list related to the VS or SQL CTP programs.
> >
> >I was then able to install the SQL 2005 "native client" successfully but
> >cannot install SQL 2005 itself. I receive an error that "beta" compoents were
> >detected and must be removed before installing SQL 2005. I cannot uninstall
> >them through "Add/Remove Programs" so it looks like they'll have to be
> >uninstalled manually, assuming this is doable, of course. I have no idea how
> >to accomplish this.
> >
> >Any help with removing the SQL Server 2005 Apr CTP components and/or
> >proceeding with the SQL 2005 installation would be "greatly" appreciated.
> >Thank you.
>

Problems installing SQL Server 2005

I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
mistake of uninstalling the Visual Studio CTP "first". After uninstalling it
,
I was able to complete the installation of the "released" version of Visual
Studio. During the install, I did receive a few error messages about SQL
Server but proceeded with the install. VS completed its installation and
appears to OK.
However, whe I treid to continue with the SQL Server 2005 installation, my
real problems started. First, I had to "uninstall" the CTP components. I
started with "Add/Remove Programs" but the only SQL CTP components that were
listed would NOT uninstall. In fact, trying to uninstall them just resulted
in their entries disappearing from the "Add/Remove Programs" list. There is
nothing left in that list related to the VS or SQL CTP programs.
I was then able to install the SQL 2005 "native client" successfully but
cannot install SQL 2005 itself. I receive an error that "beta" compoents wer
e
detected and must be removed before installing SQL 2005. I cannot uninstall
them through "Add/Remove Programs" so it looks like they'll have to be
uninstalled manually, assuming this is doable, of course. I have no idea how
to accomplish this.
Any help with removing the SQL Server 2005 Apr CTP components and/or
proceeding with the SQL 2005 installation would be "greatly" appreciated.
Thank you.
--
Denis W. RepkeTry running this MS uninstall utility...should do the trick for you.
http://go.microsoft.com/fwlink/?LinkId=47598|||Gregg,
Thanks for the quick reply. However...
Doesn't this program just uninstall the Visual Studio components? If so,
that's not my problem.
I have already uninstalled all of the Visual Studio CTP components and
completed installation of the Visual Studio 2005 "released" version. My
problem is removing the SQL Server 2005 CTP components so that I can install
the "released" version of SQL Server 2005. I cannot do this using "Add/Remov
e
Programs".
Denis W. Repke
"Gregg Walker" wrote:

> Try running this MS uninstall utility...should do the trick for you.
> http://go.microsoft.com/fwlink/?LinkId=47598
>
>|||Denis,
Given what you have done I think you need to go back a step in order
to have a chance of going forward successfully.
I suggest you do the following:
1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
it fairly straightforwardly)
2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
you could re-install it and try to uninstall April CTP components
using Add/Remove Programs.
3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
See http://support.microsoft.com/defaul...kb;en-us;290301 for
further information. It's wise to back up important files.
4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
then install SQL Server 2005 RTM (it should be installed before Visual
Studio). This is the moment of truth - if SQL Server RTM installs
cleanly you should be in good shape to go on to Step 5.
5. Install Visual Studio 2005 RTM again.
Good luck.
Andrew Watt
MVP - InfoPath
On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
<DenisRepke@.discussions.microsoft.com> wrote:

>I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
>Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
>mistake of uninstalling the Visual Studio CTP "first". After uninstalling i
t,
>I was able to complete the installation of the "released" version of Visual
>Studio. During the install, I did receive a few error messages about SQL
>Server but proceeded with the install. VS completed its installation and
>appears to OK.
>However, whe I treid to continue with the SQL Server 2005 installation, my
>real problems started. First, I had to "uninstall" the CTP components. I
>started with "Add/Remove Programs" but the only SQL CTP components that wer
e
>listed would NOT uninstall. In fact, trying to uninstall them just resulted
>in their entries disappearing from the "Add/Remove Programs" list. There is
>nothing left in that list related to the VS or SQL CTP programs.
>I was then able to install the SQL 2005 "native client" successfully but
>cannot install SQL 2005 itself. I receive an error that "beta" compoents we
re
>detected and must be removed before installing SQL 2005. I cannot uninstall
>them through "Add/Remove Programs" so it looks like they'll have to be
>uninstalled manually, assuming this is doable, of course. I have no idea ho
w
>to accomplish this.
>Any help with removing the SQL Server 2005 Apr CTP components and/or
>proceeding with the SQL 2005 installation would be "greatly" appreciated.
>Thank you.|||Andrew,
I guess I'll have to try your suggestions. Nothing else is working. I did
also try running the "build unistall" program from the Sept CTP. That did NO
T
work. Thanks for the help.
Denis W. Repke
"Andrew Watt [MVP - InfoPath]" wrote:

> Denis,
> Given what you have done I think you need to go back a step in order
> to have a chance of going forward successfully.
> I suggest you do the following:
> 1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
> it fairly straightforwardly)
> 2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
> you could re-install it and try to uninstall April CTP components
> using Add/Remove Programs.
> 3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
> See http://support.microsoft.com/defaul...kb;en-us;290301 for
> further information. It's wise to back up important files.
> 4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
> then install SQL Server 2005 RTM (it should be installed before Visual
> Studio). This is the moment of truth - if SQL Server RTM installs
> cleanly you should be in good shape to go on to Step 5.
> 5. Install Visual Studio 2005 RTM again.
> Good luck.
> Andrew Watt
> MVP - InfoPath
> On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
> <DenisRepke@.discussions.microsoft.com> wrote:
>
>

Problems connecting to "(LOCAL)" from SSIS

I've recently moved from June CTP to RTM. I'm now having a problem connecting to the (LOCAL) server in SSIS via a Native OLE DB\Microsoft OLE DB Provider for SQL Server connection. The error is:

Test connection failed because of an error in initializing provider. [DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied.

I'm connecting with Windows Authentication, and I can connect to (LOCAL) with Windows Authentication via Management Studio. If I change the server name to the actual name of my development box then it will connect. I'd like to use (LOCAL) though so it's easily portable between different development environments.

Anyone have any ideas?This is not an SSIS problem; the underlying OLE DB provider is evaluating server names.

Have you tried with "localhost" or "."?

Thanks.|||This doesn't appear to work unless you have TCP/IP enabled. It is disabled by default. It seems that "(local)" no longer forces the use of Shared Memory.

-Doug

Problems after installing SP2

I'm having some major problems with SSAS after installing SP2 (I never had an SP2 CTP installed, just SP1).

When I bring up BI Studio and select Open/Analysis Service Database, put in my server name (which is on the same machine that I'm running BI Studio), the click the "Database" drop down to select a database, it shows the following error in the bottom of the dialog:

Errors in the OLAP storage engine: The linked measure group with the ID of 'Sales', Name of 'Sales' cannot be processed because it contains MG dimension with the ID of 'Time', Name of 'Time' with different granularity attribute than its source object.
Errors in the metadata manager. An error occurred when loading the Sales measure group, from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\FoodMart.0.db\Trained Cube.0.cub\Sales.1.det.xml'.
Errors in the metadata manager. An error occurred when loading the Trained Cube cube, from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\FoodMart.0.db\Trained Cube.1.cub.xml'.

At this point, there doesn't seem to be any way to open any database in BI Studio. I always get that error, even if I try typing in another database name.

SQL Management Studio seems slightly better - I can at least connect there. But it only shows a couple of the databases that were on the machine - a bunch are missing. Any attempt to process or browse any of the databases results in the same error as above.

Any ideas?

Quoting the SP2 Readme: http://download.microsoft.com/download/2/B/5/2B5E5D37-9B17-423D-BC8F-B11ECD4195B4/ReadmeSQL2005SP2.htm

5.3.2 Analysis Services Databases that Contain a Linked Measure Group Might Become Unusable After Upgrade

Introduced in SQL Server 2005 SP2.

Analysis Services now requires that all dimensions contained in a linked measure group have the same granularity as the dimension in the source measure group. For example, if a time dimension in the source measure group has the day attribute as the granularity attribute, the linked measure group must also use the day attribute as the granularity attribute. The most common scenario for an Analysis Services database that violates this rule is a SQL Server 2000 Analysis Services database that was migrated by using a pre-release version of SQL Server 2005.

If you have a database that violates this granularity rule, you must modify the database containing the linked measure group before applying SP2. If you don't, the database will become invalid after SP2 is applied. Such invalid databases must be deleted.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Thanks Edward. RTFM, eh? Actually, I doubt it would have helped - this is a sample DB that I found somewhere, I wouldn't have realized it had this issue.

The problem is, I don't see a way to delete the database. The admin tools all barf with that error when I try to do anything, including deleting a DB. Is there some other way to nuke it?|||Unless you can go back to pre-SP2 build, you can stop the service, and manually delete all the files and folders in the Data directory. Then you will have to redeploy and reprocess the rest of your databases, unless you have backups in which case you would simply restore them.|||Thanks Mosha. I deleted the .0.db directory and the 0.db.xml file for the bad database (which I didn't need anyway, it was just for playing with), and have now regained access to my server. Any other files I should delete to clean things up?|||

This should be enough.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

I've recently installed SP2. All was fine initially but I'm now getting the error listed above having not changed anything significant (changed the membersname unique property of an attribute and then changed it back again). I'd been making changes all day to the attribute relationships and deploying without a problem.

I'm not using a linked measure group but the measure group it's reporting an error on has a different granularity key to the main measure group. Apart from changing the granularity key of the group that has a problem what can I do to fix this?

Mark

|||

I got the same error message which is posted in the first post here.

On a server which didn't had the foodmart database installed, I didn't get any problems after installing SP2. When I tossed the foodmart files away as described above, all problems vanished. It seems the problem here is the foodmart database. At the end of it Im glad I got my DB back, but "they" managed to scare the living daylight out of me with this, because I thought the whole AS had been turned into a wreck. Ironically the only database left in the management studio was the foodmart db. If you don't use it I would recommend to delete it before installing SP2.

Regards, Jeroen

Problems after installing SP2

I'm having some major problems with SSAS after installing SP2 (I never had an SP2 CTP installed, just SP1).

When I bring up BI Studio and select Open/Analysis Service Database, put in my server name (which is on the same machine that I'm running BI Studio), the click the "Database" drop down to select a database, it shows the following error in the bottom of the dialog:

Errors in the OLAP storage engine: The linked measure group with the ID of 'Sales', Name of 'Sales' cannot be processed because it contains MG dimension with the ID of 'Time', Name of 'Time' with different granularity attribute than its source object.
Errors in the metadata manager. An error occurred when loading the Sales measure group, from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\FoodMart.0.db\Trained Cube.0.cub\Sales.1.det.xml'.
Errors in the metadata manager. An error occurred when loading the Trained Cube cube, from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\FoodMart.0.db\Trained Cube.1.cub.xml'.

At this point, there doesn't seem to be any way to open any database in BI Studio. I always get that error, even if I try typing in another database name.

SQL Management Studio seems slightly better - I can at least connect there. But it only shows a couple of the databases that were on the machine - a bunch are missing. Any attempt to process or browse any of the databases results in the same error as above.

Any ideas?

Quoting the SP2 Readme: http://download.microsoft.com/download/2/B/5/2B5E5D37-9B17-423D-BC8F-B11ECD4195B4/ReadmeSQL2005SP2.htm

5.3.2 Analysis Services Databases that Contain a Linked Measure Group Might Become Unusable After Upgrade

Introduced in SQL Server 2005 SP2.

Analysis Services now requires that all dimensions contained in a linked measure group have the same granularity as the dimension in the source measure group. For example, if a time dimension in the source measure group has the day attribute as the granularity attribute, the linked measure group must also use the day attribute as the granularity attribute. The most common scenario for an Analysis Services database that violates this rule is a SQL Server 2000 Analysis Services database that was migrated by using a pre-release version of SQL Server 2005.

If you have a database that violates this granularity rule, you must modify the database containing the linked measure group before applying SP2. If you don't, the database will become invalid after SP2 is applied. Such invalid databases must be deleted.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Thanks Edward. RTFM, eh? Actually, I doubt it would have helped - this is a sample DB that I found somewhere, I wouldn't have realized it had this issue.

The problem is, I don't see a way to delete the database. The admin tools all barf with that error when I try to do anything, including deleting a DB. Is there some other way to nuke it?|||Unless you can go back to pre-SP2 build, you can stop the service, and manually delete all the files and folders in the Data directory. Then you will have to redeploy and reprocess the rest of your databases, unless you have backups in which case you would simply restore them.|||Thanks Mosha. I deleted the .0.db directory and the 0.db.xml file for the bad database (which I didn't need anyway, it was just for playing with), and have now regained access to my server. Any other files I should delete to clean things up?|||

This should be enough.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

I've recently installed SP2. All was fine initially but I'm now getting the error listed above having not changed anything significant (changed the membersname unique property of an attribute and then changed it back again). I'd been making changes all day to the attribute relationships and deploying without a problem.

I'm not using a linked measure group but the measure group it's reporting an error on has a different granularity key to the main measure group. Apart from changing the granularity key of the group that has a problem what can I do to fix this?

Mark

|||

I got the same error message which is posted in the first post here.

On a server which didn't had the foodmart database installed, I didn't get any problems after installing SP2. When I tossed the foodmart files away as described above, all problems vanished. It seems the problem here is the foodmart database. At the end of it Im glad I got my DB back, but "they" managed to scare the living daylight out of me with this, because I thought the whole AS had been turned into a wreck. Ironically the only database left in the management studio was the foodmart db. If you don't use it I would recommend to delete it before installing SP2.

Regards, Jeroen

Problems after installing SP2

I'm having some major problems with SSAS after installing SP2 (I never had an SP2 CTP installed, just SP1).

When I bring up BI Studio and select Open/Analysis Service Database, put in my server name (which is on the same machine that I'm running BI Studio), the click the "Database" drop down to select a database, it shows the following error in the bottom of the dialog:

Errors in the OLAP storage engine: The linked measure group with the ID of 'Sales', Name of 'Sales' cannot be processed because it contains MG dimension with the ID of 'Time', Name of 'Time' with different granularity attribute than its source object.
Errors in the metadata manager. An error occurred when loading the Sales measure group, from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\FoodMart.0.db\Trained Cube.0.cub\Sales.1.det.xml'.
Errors in the metadata manager. An error occurred when loading the Trained Cube cube, from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\FoodMart.0.db\Trained Cube.1.cub.xml'.

At this point, there doesn't seem to be any way to open any database in BI Studio. I always get that error, even if I try typing in another database name.

SQL Management Studio seems slightly better - I can at least connect there. But it only shows a couple of the databases that were on the machine - a bunch are missing. Any attempt to process or browse any of the databases results in the same error as above.

Any ideas?

Quoting the SP2 Readme: http://download.microsoft.com/download/2/B/5/2B5E5D37-9B17-423D-BC8F-B11ECD4195B4/ReadmeSQL2005SP2.htm

5.3.2 Analysis Services Databases that Contain a Linked Measure Group Might Become Unusable After Upgrade

Introduced in SQL Server 2005 SP2.

Analysis Services now requires that all dimensions contained in a linked measure group have the same granularity as the dimension in the source measure group. For example, if a time dimension in the source measure group has the day attribute as the granularity attribute, the linked measure group must also use the day attribute as the granularity attribute. The most common scenario for an Analysis Services database that violates this rule is a SQL Server 2000 Analysis Services database that was migrated by using a pre-release version of SQL Server 2005.

If you have a database that violates this granularity rule, you must modify the database containing the linked measure group before applying SP2. If you don't, the database will become invalid after SP2 is applied. Such invalid databases must be deleted.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Thanks Edward. RTFM, eh? Actually, I doubt it would have helped - this is a sample DB that I found somewhere, I wouldn't have realized it had this issue.

The problem is, I don't see a way to delete the database. The admin tools all barf with that error when I try to do anything, including deleting a DB. Is there some other way to nuke it?
|||Unless you can go back to pre-SP2 build, you can stop the service, and manually delete all the files and folders in the Data directory. Then you will have to redeploy and reprocess the rest of your databases, unless you have backups in which case you would simply restore them.|||Thanks Mosha. I deleted the .0.db directory and the 0.db.xml file for the bad database (which I didn't need anyway, it was just for playing with), and have now regained access to my server. Any other files I should delete to clean things up?
|||

This should be enough.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

I've recently installed SP2. All was fine initially but I'm now getting the error listed above having not changed anything significant (changed the membersname unique property of an attribute and then changed it back again). I'd been making changes all day to the attribute relationships and deploying without a problem.

I'm not using a linked measure group but the measure group it's reporting an error on has a different granularity key to the main measure group. Apart from changing the granularity key of the group that has a problem what can I do to fix this?

Mark

|||

I got the same error message which is posted in the first post here.

On a server which didn't had the foodmart database installed, I didn't get any problems after installing SP2. When I tossed the foodmart files away as described above, all problems vanished. It seems the problem here is the foodmart database. At the end of it Im glad I got my DB back, but "they" managed to scare the living daylight out of me with this, because I thought the whole AS had been turned into a wreck. Ironically the only database left in the management studio was the foodmart db. If you don't use it I would recommend to delete it before installing SP2.

Regards, Jeroen