error when attaching DB

Msg 1813, Level 16, State 2, Line 1
Could not open new database 'Asset5'. CREATE DATABASE is aborted.
Msg 602, Level 21, State 50, Line 1
Could not find row in sysindexes for database ID 9, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.

I am just starting with a book sql server 2005 stored proc programming in tsql & .net and cant get the db to attach, any help pls

I find most publishers of SQL Server books are not careful but Microsoft is changing with their SQL Server books by posting mile long errata for a very respected writer. Their documentation however is the best in the business and their samples AdventureWorks is good size database easy to attach and play with. Try the link below for the samples it also comes with reporting services sample. Install it then go to Managment Studio right click and attach it. Download X86 case insensitive. Hope this helps.

http://www.microsoft.com/downloads/details.aspx?familyid=E719ECF7-9F46-4312-AF89-6AD8702E4E6E&displaylang=en

|||thanks allot, but... all the sprocs in this book are related to this asset5 db. can anyone help me with this error?|||

I already did could not find a solution so the questions is did you put the MDF and LDF in the location below before trying to attach it in Management Studio? Try deleting every thing and starting new put the MDF and LDF in the location below and go to Managment Studio and attach.

C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data

|||it was in the right place, when i try to install adventure works i get the same error. I havent used this install in 1yr, could it be an issue with needed service pack?|||I have installed AdventureWorks with service packs and without all without problems, I am using the developer edition. I remember getting problems with AdventureWorks install in with install.sql in 2000 but I looked in that location and found MDF and LDF created without a database so I deleted both files and the install was completed.

Error upon creation of Integration Services

After I aborted my installation of the tools that come with Katmai, I could not create Integration Services project nor add package to an existing project. I get the following error

Constructor on type 'Microsoft.DataTransformationServices.Wizards.EtlProjectWizardInitializer' not found.

I've removed anything that had the word 'Katmai' in Add/REmove programs. I've also reinstalled the 2005 tools. Still no luck. I'm just wondering if anyone here has encountered this error.
I guess the abort did not rollback completely, but then its just my guess.
Did you try re-installing katmai tools and do a complete un-install after that?.|||Hi sir. I did a complete uninstall of Katmai db and tools. I'll try to reinstall it again, maybe it will help. I just repaired my VS2005Pro installation thinking it can solve the problem but still no luck.
|||

[Microsoft follow-up]

Possible katmai bug here guys.

|||

This sounds like one of the known bugs for Katmai.

If this is the same issue that I'm thinking of, it's because the component which handles our project creation is pointing to the Katmai files.

In the registry, the keys under (CLSID, CurVer):

HKEY_CLASSES_ROOT\Microsoft.SqlServer.Management.UI.WizardManager

Should be the same as:

HKEY_CLASSES_ROOT\Microsoft.SqlServer.Management.UI.WizardManager.9

The values should be:

CLSID = {4503861B-5694-45AE-94DD-BC6541316FB7}

CurVer = Microsoft.SqlServer.Management.UI.WizardManager.9

If CurVer is Microsoft.SqlServer.Management.UI.WizardManager.10, then this is the issue that we've seen.

Note, I can't recommend tweaking the registry by hand... but if uninstalling SQL Server and Visual Studio doesn't fix the issue, this might be an alternative.

It's odd that you're still hitting it after uninstalling everything, but I guess aborting the installation might have left you in a bad state. I know that a number of setup related issues have been resolved since the June CTP, and hopefully the issue that put you into this state was one of them. Make sure that when you reinstall, you have no instances of Visual Studio running.

~Matt

|||Moving to the Katmai SSIS forum.|||

There is a workaround to get the SQL Server 2005 tools working when it is installed with Katmai server.

You need to update this file "<drive>:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\Business Intelligence Projects\DataTransformationsProject.vsz".

Replace the "Microsoft.SqlServer.Management.UI.WizardManager" with "Microsoft.SqlServer.Management.UI.WizardManager.9". Save the change and restart the SQL Server 2005 tools. You should be able to create the new projects.

|||This weekend, I reinstalled both my VS2005Pro and SQL2005Dev as a final brute force solution. I was hoping that this would also erase in the registry the entry key that points to the non-existing or invalid dll. I noticed that even for the supposed "fresh" install, the layout of my IDE did not change and the problem was still there.

Thanks so much for the replies guys. Feng, I will apply your solution.

|||I applied both solutions here. I don't care which one did it but the important thing is my headache is over. Thank you so much again! More power to you guys!

Error upon creation of Integration Services

After I aborted my installation of the tools that come with Katmai, I could not create Integration Services project nor add package to an existing project. I get the following error

Constructor on type 'Microsoft.DataTransformationServices.Wizards.EtlProjectWizardInitializer' not found.

I've removed anything that had the word 'Katmai' in Add/REmove programs. I've also reinstalled the 2005 tools. Still no luck. I'm just wondering if anyone here has encountered this error.
I guess the abort did not rollback completely, but then its just my guess.
Did you try re-installing katmai tools and do a complete un-install after that?.|||Hi sir. I did a complete uninstall of Katmai db and tools. I'll try to reinstall it again, maybe it will help. I just repaired my VS2005Pro installation thinking it can solve the problem but still no luck.
|||

[Microsoft follow-up]

Possible katmai bug here guys.

|||

This sounds like one of the known bugs for Katmai.

If this is the same issue that I'm thinking of, it's because the component which handles our project creation is pointing to the Katmai files.

In the registry, the keys under (CLSID, CurVer):

HKEY_CLASSES_ROOT\Microsoft.SqlServer.Management.UI.WizardManager

Should be the same as:

HKEY_CLASSES_ROOT\Microsoft.SqlServer.Management.UI.WizardManager.9

The values should be:

CLSID = {4503861B-5694-45AE-94DD-BC6541316FB7}

CurVer = Microsoft.SqlServer.Management.UI.WizardManager.9

If CurVer is Microsoft.SqlServer.Management.UI.WizardManager.10, then this is the issue that we've seen.

Note, I can't recommend tweaking the registry by hand... but if uninstalling SQL Server and Visual Studio doesn't fix the issue, this might be an alternative.

It's odd that you're still hitting it after uninstalling everything, but I guess aborting the installation might have left you in a bad state. I know that a number of setup related issues have been resolved since the June CTP, and hopefully the issue that put you into this state was one of them. Make sure that when you reinstall, you have no instances of Visual Studio running.

~Matt

|||Moving to the Katmai SSIS forum.|||

There is a workaround to get the SQL Server 2005 tools working when it is installed with Katmai server.

You need to update this file "<drive>:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\Business Intelligence Projects\DataTransformationsProject.vsz".

Replace the "Microsoft.SqlServer.Management.UI.WizardManager" with "Microsoft.SqlServer.Management.UI.WizardManager.9". Save the change and restart the SQL Server 2005 tools. You should be able to create the new projects.

|||This weekend, I reinstalled both my VS2005Pro and SQL2005Dev as a final brute force solution. I was hoping that this would also erase in the registry the entry key that points to the non-existing or invalid dll. I noticed that even for the supposed "fresh" install, the layout of my IDE did not change and the problem was still there.

Thanks so much for the replies guys. Feng, I will apply your solution.

|||I applied both solutions here. I don't care which one did it but the important thing is my headache is over. Thank you so much again! More power to you guys!