cannot open a jscript file

SQL Server CTP Sept 2005.

In Microsoft Visual Studio 8 after starting an Integration Services Project I tried to create a jscript file. A file was created but the browser was completely messed up.

First I was never able to open it (right after it was created but not yet saved). The file name "jscript1.js" would appear as a separate tab on top of the window next to the "start page" but when you click on it the the file does not appear in the editor window as I assume it should. Instead the same object browset or start page would stay under the tab name "jscript.js file." Sometimes strange vertical stipes appear next to the tool box or instead of it. Quite weird, obviously a bug in the designer. A MS error report was automatically generated at one point and sent to MS but it took almost 20 min to do despite a broadband connection.

After I tried to save the file the browser seemed to freeze but I could eventually shut it down. I found the file in the proper directory but there is no way to open it in the VS Browser now (I opened it in the notebook). The Windows dialog box simply freezes when the file is clicked on.

I am still experimenting. Finally I was able to open it when I changed the sequence of operations. First, I opened the file, then ADDed the project to it. It is very weird. Am I going crazy and doing something nobody has ever seen or it is a known bug?

Thanks.Well, I've been able to open it only two or three times out of many attempts. The browser is messed up. There are problems with many windows. I reinstalled the .NET Studio (repaired)--to no avail. I scanned my entire system for viruses. It is clean.

I need an answer why I see those weird things.

Thanks.|||Since JScript File is not an option that's available when you add a new item to a project, which item type did you choose? Maybe that has confused the IDE.

I created a text file in the file system, renamed it with the .js extension, added it to an SSIS project (where it appears in the Miscellaneous folder), and opened its editor window without any problems.

-Doug
|||Many many thanks,

I repeated what you suggested (created a text file, renamed it .js and, most importantly, MOVED it into the project). Yesterday I did not pay attention to the "move file **** into" tab and it never appeared in miscellaneous which made me wonder. Now it works perfectly fine. No weird behavior anymore for sure.

Actually you are wrong about jscript not bein an option, sorry about saying that. There are two options: "general" and "scripts" under "new file"; "general" then branches into "text, xml," etc... and "scripts" into Jscript, VBScripts and Windows Script host.

Still there is a problem with the arrangement. I just tried to create a jscript file as I did yesterday, save it as a jscript file and move it into the project. I observed that if I first saved it and then moved it then I could open it and see the content in the editor. If I MOVED it first and then saved it the things are messed up although not as badly as I saw yesterday.

In any event, you advanced my understanding of the GUI greatly and I am very appreciative of it.

Thanks.

Cannot install SSIS or Notification services

I'm trying to reinstall SQL Server 2005 STD but I cannot get Setup to install Integration Services or Notification Services. I looked in the log and this is what I found. Needless to say, it makes no sense to me. It seems that Setup is trying to find a missing source list for a certain product. I have no clue what that product is. I've spent endless hours trying to figure it out and I'm still drawing a blank. This is a printout of the log.

Integration services -
-
MSI (s) (F0:B0) [02:33:01:437]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (F0:B0) [02:33:02:188]: End dialog not enabled
MSI (s) (F0:B0) [02:33:02:188]: Original package ==> G:\Servers\Setup\SqlRun_DTS.msi
MSI (s) (F0:B0) [02:33:02:188]: Package we're running from ==> C:\WINDOWS\Installer\188966.msi
MSI (s) (F0:B0) [02:33:02:339]: APPCOMPAT: looking for appcompat database entry with ProductCode '{EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}'.
MSI (s) (F0:B0) [02:33:02:339]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (F0:B0) [02:33:02:339]: MSCOREE already loaded, using loaded copy
MSI (s) (F0:B0) [02:33:02:379]: Couldn't find local patch ''. Looking for it at its source.
MSI (s) (F0:B0) [02:33:02:379]: Resolving Patch source.
MSI (s) (F0:B0) [02:33:02:379]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (F0:B0) [02:33:02:379]: User policy value 'DisableMedia' is 0
MSI (s) (F0:B0) [02:33:02:379]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (F0:B0) [02:33:02:379]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (F0:B0) [02:33:02:379]: SOURCEMGMT: Looking for sourcelist for product {8B7E2749-624E-4C61-92FC-2BC18307FF24}
MSI (s) (F0:B0) [02:33:02:379]: Note: 1: 1706 2: {8B7E2749-624E-4C61-92FC-2BC18307FF24} 3:
MSI (s) (F0:B0) [02:33:02:379]: SOURCEMGMT: Failed to resolve source
MSI (s) (F0:B0) [02:33:02:399]: Note: 1: 1708
MSI (s) (F0:B0) [02:33:02:399]: Note: 1: 2729
MSI (s) (F0:B0) [02:33:02:409]: Note: 1: 2729
MSI (s) (F0:B0) [02:33:02:409]: Product: Microsoft SQL Server 2005 Integration Services -- Installation failed.

MSI (s) (F0:B0) [02:33:02:439]: MainEngineThread is returning 1612
The installation source for this product is not available. Verify that the source exists and that you can access it.
G:\Servers\Setup\SqlRun_DTS.msi
MSI (c) (B8:88) [02:33:02:439]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (B8:88) [02:33:02:439]: MainEngineThread is returning 1612
=== Verbose logging stopped: 5/19/2006 2:33:02 ===

--
Notification services -
--
MSI (s) (F0:30) [02:33:07:566]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (F0:30) [02:33:08:087]: End dialog not enabled
MSI (s) (F0:30) [02:33:08:087]: Original package ==> G:\Servers\Setup\SqlRun_NS.msi
MSI (s) (F0:30) [02:33:08:087]: Package we're running from ==> C:\WINDOWS\Installer\18898f.msi
MSI (s) (F0:30) [02:33:08:167]: APPCOMPAT: looking for appcompat database entry with ProductCode '{37E9AD9F-3217-4229-B5A5-7A0C82364C6C}'.
MSI (s) (F0:30) [02:33:08:167]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (F0:30) [02:33:08:167]: MSCOREE already loaded, using loaded copy
MSI (s) (F0:30) [02:33:08:187]: Couldn't find local patch ''. Looking for it at its source.
MSI (s) (F0:30) [02:33:08:187]: Resolving Patch source.
MSI (s) (F0:30) [02:33:08:187]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (F0:30) [02:33:08:187]: User policy value 'DisableMedia' is 0
MSI (s) (F0:30) [02:33:08:187]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (F0:30) [02:33:08:187]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (F0:30) [02:33:08:187]: SOURCEMGMT: Looking for sourcelist for product {65A498A6-83B9-4B91-99EA-1BA88D73F0AA}
MSI (s) (F0:30) [02:33:08:187]: Note: 1: 1706 2: {65A498A6-83B9-4B91-99EA-1BA88D73F0AA} 3:
MSI (s) (F0:30) [02:33:08:187]: SOURCEMGMT: Failed to resolve source
MSI (s) (F0:30) [02:33:08:187]: Note: 1: 1708
MSI (s) (F0:30) [02:33:08:187]: Note: 1: 2729
MSI (s) (F0:30) [02:33:08:187]: Note: 1: 2729
MSI (s) (F0:30) [02:33:08:187]: Product: Microsoft SQL Server 2005 Notification Services -- Installation failed.

MSI (s) (F0:30) [02:33:08:197]: MainEngineThread is returning 1612
The installation source for this product is not available. Verify that the source exists and that you can access it.
G:\Servers\Setup\SqlRun_NS.msi
MSI (c) (B8:DC) [02:33:08:207]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (B8:DC) [02:33:08:207]: MainEngineThread is returning 1612

During your first install, the MSIs were cached to the specified location (G:\servers\setup\...). Apparently those files were subsequently deleted or perhaps the drive is no longer accessible. Are you reinstalling from the original media or are you using add/remove programs?|||

Paul, I noticed these lines in the error log.

Integration services -
-
MSI (s) (F0:B0) [02:33:02:188]: Original package ==> G:\Servers\Setup\SqlRun_DTS.msi
MSI (s) (F0:B0) [02:33:02:188]: Package we're running from ==> C:\WINDOWS\Installer\188966.msi
--
Notification services -
--
MSI (s) (F0:30) [02:33:08:087]: Original package ==> G:\Servers\Setup\SqlRun_NS.msi
MSI (s) (F0:30) [02:33:08:087]: Package we're running from ==> C:\WINDOWS\Installer\18898f.msi

However, I can't find the C:\WINDOWS\Installer folder on my computer. Is this significant?

|||

The c:\windows\installer folder is ordinarily hidden. To see it, go to Windows Explorer tools\folder options and under the view tab turn on both "Display the contents of system folders" and "Show hidden files and folders". Once you've done that, the folder and its contents should be visible.

Paul

cannot install integration services

Hi!

During the installation of integration services (SQL 05 Developer RTM) I get the following error:

TITLE: Microsoft SQL Server 2005 Setup

Failed to install and configure assemblies C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: Failed to generate type library 'C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.tlb' for 'Microsoft.SqlServer.MSMQTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.

I had CTPs of SQL05 and VS05 installed before, but uninstalled them with the cleanup tool.

yeh, I had this issue and found a resolution... read my thread about the installation issue resolved (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1)

the other workaround really is not to select to install integration services but to install it after everything else|||Thank you for your fast reply. I'm trying to install SQL05 Developer on Windows XP Pro SP2. I forgot to mention that in my first post. So I think your solution won't help me :(|||I see!
Well, try to install everything except integration services and then install integration services after everything

The thread I created STILL DOES apply to WS2003, due to installed components still breaking and during installation (I know you are running XP so you do not need to go through the thread!) :)|||

I already did that. I uninstalled Integration Services (during the first installation, I ignored the error message, but IS didn't work then), and tried to reinstall them. I always get the same error.

|||have you:

tried completly removing SQL Server 2005.
Then installing it WITHOUT the integration and reporting services? :-)|||- I uninstalled SQL server, including SQL Native Client and Everything I found that had "sql" in it's name.
- rebooted
- Installed just the SQL Server engine, Clients, Documentation
- rebooted
- Instaled everything except Integration Services
- rebooted
- Tried to install Integration Services, I still get the same error|||Hi Mathias,

I am in exactly the same situation as you. If I find anything I will post here.

Regards,

Chris|||Thank you. Good luck! :)|||Hi all,
I had the same problem. I think it was because of a incomplete uninstall of a previous Beta Version. Check if in there an old version of one of the "Microsoft.SqlServer.DtsXXX" Assemblies (take a look at the Last Modified Date in the Properties) in the Global Assembly Cache.
If there is one or more, delete them.
If you can't delete them because there are references, eliminate these first (can be done by deleting some registry-keys, but I don't know exactly which ones).
Then, after all old assemblies are removed, reinstall the Integration Services using the Setup. Should then work flawlessy.
Greetings,
Ingo
|||Have the same problem with Win2K Pro, SQL 2000 already installed and then SQL
2005 DevEd

After uninstalling SQL2005 a few times in order to get it to install with this error, which also breaks Enterprise Manager on SQL2000 in the process, I then end up reinstalling both. What a pain!

Eventually, after many hours buggering around, got SQL2000 and SQL2005 working but this 'install bug' or 'another MS featurett' (which is still not resolved from what I can see), is such a time waster, in what already is limited!

Does anyone know of an easy fix or patch, rather than have to re-install IS again and possibly cause other issues?
|||This is somewhat related to the problem I had. See my resolution with SSIS at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124884&SiteID=1. Reinstall OS and then install SQL 2005 RTM Dev Edtion.

I still want to configure a mixed environment with SQL2000 SP4 and SQL2005 RTM Dev Edition on Win XP Pro SP2. I have tried it and cannot use SSIS to configure connections.

If someone has a workaround, please post but I do not want to go thru the pain of reinstalling the OS and my dev tools again.|||Hi centexbi,
I have SQL2000 and SQL2005 working side-by-side on my XP SP2.
Don't know if this is a solution for you and if it works, but you might give it a try:
- Completely remove anything that has to do with .NET (all framework version, VisualStudio, etc.)
- Ensure that you no longer have the directories %SYSTEMROOT%\assembly und %SYSTEMROOT%\Microsoft.NET, delete them if necessary
- Reinstall SQL2000 including SP4
- Try to install SQL2005
Greets,
Ingo
|||Appreciate Ingo and Centexbi thoughts but reinstall of OS is simply not an option.

As a developer, one has a large number of apps, tools etc installed and if the system (as in my case), is very stable apart from SQL2005 install then I would rather ditch install of SQL as opposed to spending a number of days re-assembling the PC OS etc.

Reinstall of SQL2005 has not resolved this - even from the point of painstakenly removing registry entries etc and trying to install as virgin. Maybe MS should provide a proper installer which will remove the masses of junk registry entries SQL2005 leaves behind when you unistall. How about a 'SQL2005 clean reg / os' tool - bit like what Symantec do for their AV?

This is the real world and time is as scarce as money. 'We' all spend far too much time working in this 'black art' industry and shame MS do not do more to help us!

|||Hi ComputerSolutions
An OS-Reinstall is of course _never_ an option.
I can only support your idea of a cleanup-tool.
Greets,
Ingo

cannot install integration services

Hi!

During the installation of integration services (SQL 05 Developer RTM) I get the following error:

TITLE: Microsoft SQL Server 2005 Setup

Failed to install and configure assemblies C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: Failed to generate type library 'C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.tlb' for 'Microsoft.SqlServer.MSMQTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.

I had CTPs of SQL05 and VS05 installed before, but uninstalled them with the cleanup tool.

yeh, I had this issue and found a resolution... read my thread about the installation issue resolved (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1)

the other workaround really is not to select to install integration services but to install it after everything else|||Thank you for your fast reply. I'm trying to install SQL05 Developer on Windows XP Pro SP2. I forgot to mention that in my first post. So I think your solution won't help me :(|||I see!
Well, try to install everything except integration services and then install integration services after everything

The thread I created STILL DOES apply to WS2003, due to installed components still breaking and during installation (I know you are running XP so you do not need to go through the thread!) :)|||

I already did that. I uninstalled Integration Services (during the first installation, I ignored the error message, but IS didn't work then), and tried to reinstall them. I always get the same error.

|||have you:

tried completly removing SQL Server 2005.
Then installing it WITHOUT the integration and reporting services? :-)|||- I uninstalled SQL server, including SQL Native Client and Everything I found that had "sql" in it's name.
- rebooted
- Installed just the SQL Server engine, Clients, Documentation
- rebooted
- Instaled everything except Integration Services
- rebooted
- Tried to install Integration Services, I still get the same error|||Hi Mathias,

I am in exactly the same situation as you. If I find anything I will post here.

Regards,

Chris|||Thank you. Good luck! :)|||Hi all,
I had the same problem. I think it was because of a incomplete uninstall of a previous Beta Version. Check if in there an old version of one of the "Microsoft.SqlServer.DtsXXX" Assemblies (take a look at the Last Modified Date in the Properties) in the Global Assembly Cache.
If there is one or more, delete them.
If you can't delete them because there are references, eliminate these first (can be done by deleting some registry-keys, but I don't know exactly which ones).
Then, after all old assemblies are removed, reinstall the Integration Services using the Setup. Should then work flawlessy.
Greetings,
Ingo|||Have the same problem with Win2K Pro, SQL 2000 already installed and then SQL
2005 DevEd

After uninstalling SQL2005 a few times in order to get it to install with this error, which also breaks Enterprise Manager on SQL2000 in the process, I then end up reinstalling both. What a pain!

Eventually, after many hours buggering around, got SQL2000 and SQL2005 working but this 'install bug' or 'another MS featurett' (which is still not resolved from what I can see), is such a time waster, in what already is limited!

Does anyone know of an easy fix or patch, rather than have to re-install IS again and possibly cause other issues?|||This is somewhat related to the problem I had. See my resolution with SSIS at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124884&SiteID=1. Reinstall OS and then install SQL 2005 RTM Dev Edtion.

I still want to configure a mixed environment with SQL2000 SP4 and SQL2005 RTM Dev Edition on Win XP Pro SP2. I have tried it and cannot use SSIS to configure connections.

If someone has a workaround, please post but I do not want to go thru the pain of reinstalling the OS and my dev tools again.|||Hi centexbi,
I have SQL2000 and SQL2005 working side-by-side on my XP SP2.
Don't know if this is a solution for you and if it works, but you might give it a try:
- Completely remove anything that has to do with .NET (all framework version, VisualStudio, etc.)
- Ensure that you no longer have the directories %SYSTEMROOT%\assembly und %SYSTEMROOT%\Microsoft.NET, delete them if necessary
- Reinstall SQL2000 including SP4
- Try to install SQL2005
Greets,
Ingo|||Appreciate Ingo and Centexbi thoughts but reinstall of OS is simply not an option.

As a developer, one has a large number of apps, tools etc installed and if the system (as in my case), is very stable apart from SQL2005 install then I would rather ditch install of SQL as opposed to spending a number of days re-assembling the PC OS etc.

Reinstall of SQL2005 has not resolved this - even from the point of painstakenly removing registry entries etc and trying to install as virgin. Maybe MS should provide a proper installer which will remove the masses of junk registry entries SQL2005 leaves behind when you unistall. How about a 'SQL2005 clean reg / os' tool - bit like what Symantec do for their AV?

This is the real world and time is as scarce as money. 'We' all spend far too much time working in this 'black art' industry and shame MS do not do more to help us!|||Hi ComputerSolutions
An OS-Reinstall is of course _never_ an option.
I can only support your idea of a cleanup-tool.
Greets,
Ingo

cannot install integration services

Hi!

During the installation of integration services (SQL 05 Developer RTM) I get the following error:

TITLE: Microsoft SQL Server 2005 Setup

Failed to install and configure assemblies C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: Failed to generate type library 'C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.tlb' for 'Microsoft.SqlServer.MSMQTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.

I had CTPs of SQL05 and VS05 installed before, but uninstalled them with the cleanup tool.

yeh, I had this issue and found a resolution... read my thread about the installation issue resolved (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1)

the other workaround really is not to select to install integration services but to install it after everything else|||Thank you for your fast reply. I'm trying to install SQL05 Developer on Windows XP Pro SP2. I forgot to mention that in my first post. So I think your solution won't help me :(|||I see!
Well, try to install everything except integration services and then install integration services after everything

The thread I created STILL DOES apply to WS2003, due to installed components still breaking and during installation (I know you are running XP so you do not need to go through the thread!) :)|||

I already did that. I uninstalled Integration Services (during the first installation, I ignored the error message, but IS didn't work then), and tried to reinstall them. I always get the same error.

|||have you:

tried completly removing SQL Server 2005.
Then installing it WITHOUT the integration and reporting services? :-)|||- I uninstalled SQL server, including SQL Native Client and Everything I found that had "sql" in it's name.
- rebooted
- Installed just the SQL Server engine, Clients, Documentation
- rebooted
- Instaled everything except Integration Services
- rebooted
- Tried to install Integration Services, I still get the same error|||Hi Mathias,

I am in exactly the same situation as you. If I find anything I will post here.

Regards,

Chris|||Thank you. Good luck! :)|||Hi all,
I had the same problem. I think it was because of a incomplete uninstall of a previous Beta Version. Check if in there an old version of one of the "Microsoft.SqlServer.DtsXXX" Assemblies (take a look at the Last Modified Date in the Properties) in the Global Assembly Cache.
If there is one or more, delete them.
If you can't delete them because there are references, eliminate these first (can be done by deleting some registry-keys, but I don't know exactly which ones).
Then, after all old assemblies are removed, reinstall the Integration Services using the Setup. Should then work flawlessy.
Greetings,
Ingo|||Have the same problem with Win2K Pro, SQL 2000 already installed and then SQL
2005 DevEd

After uninstalling SQL2005 a few times in order to get it to install with this error, which also breaks Enterprise Manager on SQL2000 in the process, I then end up reinstalling both. What a pain!

Eventually, after many hours buggering around, got SQL2000 and SQL2005 working but this 'install bug' or 'another MS featurett' (which is still not resolved from what I can see), is such a time waster, in what already is limited!

Does anyone know of an easy fix or patch, rather than have to re-install IS again and possibly cause other issues?|||This is somewhat related to the problem I had. See my resolution with SSIS at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124884&SiteID=1. Reinstall OS and then install SQL 2005 RTM Dev Edtion.

I still want to configure a mixed environment with SQL2000 SP4 and SQL2005 RTM Dev Edition on Win XP Pro SP2. I have tried it and cannot use SSIS to configure connections.

If someone has a workaround, please post but I do not want to go thru the pain of reinstalling the OS and my dev tools again.|||Hi centexbi,
I have SQL2000 and SQL2005 working side-by-side on my XP SP2.
Don't know if this is a solution for you and if it works, but you might give it a try:
- Completely remove anything that has to do with .NET (all framework version, VisualStudio, etc.)
- Ensure that you no longer have the directories %SYSTEMROOT%\assembly und %SYSTEMROOT%\Microsoft.NET, delete them if necessary
- Reinstall SQL2000 including SP4
- Try to install SQL2005
Greets,
Ingo|||Appreciate Ingo and Centexbi thoughts but reinstall of OS is simply not an option.

As a developer, one has a large number of apps, tools etc installed and if the system (as in my case), is very stable apart from SQL2005 install then I would rather ditch install of SQL as opposed to spending a number of days re-assembling the PC OS etc.

Reinstall of SQL2005 has not resolved this - even from the point of painstakenly removing registry entries etc and trying to install as virgin. Maybe MS should provide a proper installer which will remove the masses of junk registry entries SQL2005 leaves behind when you unistall. How about a 'SQL2005 clean reg / os' tool - bit like what Symantec do for their AV?

This is the real world and time is as scarce as money. 'We' all spend far too much time working in this 'black art' industry and shame MS do not do more to help us!|||Hi ComputerSolutions
An OS-Reinstall is of course _never_ an option.
I can only support your idea of a cleanup-tool.
Greets,
Ingo

cannot install integration services

Hi!

During the installation of integration services (SQL 05 Developer RTM) I get the following error:

TITLE: Microsoft SQL Server 2005 Setup

Failed to install and configure assemblies C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: Failed to generate type library 'C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.tlb' for 'Microsoft.SqlServer.MSMQTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.

I had CTPs of SQL05 and VS05 installed before, but uninstalled them with the cleanup tool.

yeh, I had this issue and found a resolution... read my thread about the installation issue resolved (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1)

the other workaround really is not to select to install integration services but to install it after everything else|||Thank you for your fast reply. I'm trying to install SQL05 Developer on Windows XP Pro SP2. I forgot to mention that in my first post. So I think your solution won't help me :(|||I see!
Well, try to install everything except integration services and then install integration services after everything

The thread I created STILL DOES apply to WS2003, due to installed components still breaking and during installation (I know you are running XP so you do not need to go through the thread!) :)|||

I already did that. I uninstalled Integration Services (during the first installation, I ignored the error message, but IS didn't work then), and tried to reinstall them. I always get the same error.

|||have you:

tried completly removing SQL Server 2005.
Then installing it WITHOUT the integration and reporting services? :-)|||- I uninstalled SQL server, including SQL Native Client and Everything I found that had "sql" in it's name.
- rebooted
- Installed just the SQL Server engine, Clients, Documentation
- rebooted
- Instaled everything except Integration Services
- rebooted
- Tried to install Integration Services, I still get the same error|||Hi Mathias,

I am in exactly the same situation as you. If I find anything I will post here.

Regards,

Chris|||Thank you. Good luck! :)|||Hi all,
I had the same problem. I think it was because of a incomplete uninstall of a previous Beta Version. Check if in there an old version of one of the "Microsoft.SqlServer.DtsXXX" Assemblies (take a look at the Last Modified Date in the Properties) in the Global Assembly Cache.
If there is one or more, delete them.
If you can't delete them because there are references, eliminate these first (can be done by deleting some registry-keys, but I don't know exactly which ones).
Then, after all old assemblies are removed, reinstall the Integration Services using the Setup. Should then work flawlessy.
Greetings,
Ingo
|||Have the same problem with Win2K Pro, SQL 2000 already installed and then SQL
2005 DevEd

After uninstalling SQL2005 a few times in order to get it to install with this error, which also breaks Enterprise Manager on SQL2000 in the process, I then end up reinstalling both. What a pain!

Eventually, after many hours buggering around, got SQL2000 and SQL2005 working but this 'install bug' or 'another MS featurett' (which is still not resolved from what I can see), is such a time waster, in what already is limited!

Does anyone know of an easy fix or patch, rather than have to re-install IS again and possibly cause other issues?
|||This is somewhat related to the problem I had. See my resolution with SSIS at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124884&SiteID=1. Reinstall OS and then install SQL 2005 RTM Dev Edtion.

I still want to configure a mixed environment with SQL2000 SP4 and SQL2005 RTM Dev Edition on Win XP Pro SP2. I have tried it and cannot use SSIS to configure connections.

If someone has a workaround, please post but I do not want to go thru the pain of reinstalling the OS and my dev tools again.|||Hi centexbi,
I have SQL2000 and SQL2005 working side-by-side on my XP SP2.
Don't know if this is a solution for you and if it works, but you might give it a try:
- Completely remove anything that has to do with .NET (all framework version, VisualStudio, etc.)
- Ensure that you no longer have the directories %SYSTEMROOT%\assembly und %SYSTEMROOT%\Microsoft.NET, delete them if necessary
- Reinstall SQL2000 including SP4
- Try to install SQL2005
Greets,
Ingo
|||Appreciate Ingo and Centexbi thoughts but reinstall of OS is simply not an option.

As a developer, one has a large number of apps, tools etc installed and if the system (as in my case), is very stable apart from SQL2005 install then I would rather ditch install of SQL as opposed to spending a number of days re-assembling the PC OS etc.

Reinstall of SQL2005 has not resolved this - even from the point of painstakenly removing registry entries etc and trying to install as virgin. Maybe MS should provide a proper installer which will remove the masses of junk registry entries SQL2005 leaves behind when you unistall. How about a 'SQL2005 clean reg / os' tool - bit like what Symantec do for their AV?

This is the real world and time is as scarce as money. 'We' all spend far too much time working in this 'black art' industry and shame MS do not do more to help us!

|||Hi ComputerSolutions
An OS-Reinstall is of course _never_ an option.
I can only support your idea of a cleanup-tool.
Greets,
Ingo

cannot install integration services

Hi!

During the installation of integration services (SQL 05 Developer RTM) I get the following error:

TITLE: Microsoft SQL Server 2005 Setup

Failed to install and configure assemblies C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: Failed to generate type library 'C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.tlb' for 'Microsoft.SqlServer.MSMQTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.

I had CTPs of SQL05 and VS05 installed before, but uninstalled them with the cleanup tool.

yeh, I had this issue and found a resolution... read my thread about the installation issue resolved (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1)

the other workaround really is not to select to install integration services but to install it after everything else|||Thank you for your fast reply. I'm trying to install SQL05 Developer on Windows XP Pro SP2. I forgot to mention that in my first post. So I think your solution won't help me :(|||I see!
Well, try to install everything except integration services and then install integration services after everything

The thread I created STILL DOES apply to WS2003, due to installed components still breaking and during installation (I know you are running XP so you do not need to go through the thread!) :)|||

I already did that. I uninstalled Integration Services (during the first installation, I ignored the error message, but IS didn't work then), and tried to reinstall them. I always get the same error.

|||have you:

tried completly removing SQL Server 2005.
Then installing it WITHOUT the integration and reporting services? :-)|||- I uninstalled SQL server, including SQL Native Client and Everything I found that had "sql" in it's name.
- rebooted
- Installed just the SQL Server engine, Clients, Documentation
- rebooted
- Instaled everything except Integration Services
- rebooted
- Tried to install Integration Services, I still get the same error|||Hi Mathias,

I am in exactly the same situation as you. If I find anything I will post here.

Regards,

Chris|||Thank you. Good luck! :)|||Hi all,
I had the same problem. I think it was because of a incomplete uninstall of a previous Beta Version. Check if in there an old version of one of the "Microsoft.SqlServer.DtsXXX" Assemblies (take a look at the Last Modified Date in the Properties) in the Global Assembly Cache.
If there is one or more, delete them.
If you can't delete them because there are references, eliminate these first (can be done by deleting some registry-keys, but I don't know exactly which ones).
Then, after all old assemblies are removed, reinstall the Integration Services using the Setup. Should then work flawlessy.
Greetings,
Ingo
|||Have the same problem with Win2K Pro, SQL 2000 already installed and then SQL
2005 DevEd

After uninstalling SQL2005 a few times in order to get it to install with this error, which also breaks Enterprise Manager on SQL2000 in the process, I then end up reinstalling both. What a pain!

Eventually, after many hours buggering around, got SQL2000 and SQL2005 working but this 'install bug' or 'another MS featurett' (which is still not resolved from what I can see), is such a time waster, in what already is limited!

Does anyone know of an easy fix or patch, rather than have to re-install IS again and possibly cause other issues?
|||This is somewhat related to the problem I had. See my resolution with SSIS at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124884&SiteID=1. Reinstall OS and then install SQL 2005 RTM Dev Edtion.

I still want to configure a mixed environment with SQL2000 SP4 and SQL2005 RTM Dev Edition on Win XP Pro SP2. I have tried it and cannot use SSIS to configure connections.

If someone has a workaround, please post but I do not want to go thru the pain of reinstalling the OS and my dev tools again.|||Hi centexbi,
I have SQL2000 and SQL2005 working side-by-side on my XP SP2.
Don't know if this is a solution for you and if it works, but you might give it a try:
- Completely remove anything that has to do with .NET (all framework version, VisualStudio, etc.)
- Ensure that you no longer have the directories %SYSTEMROOT%\assembly und %SYSTEMROOT%\Microsoft.NET, delete them if necessary
- Reinstall SQL2000 including SP4
- Try to install SQL2005
Greets,
Ingo
|||Appreciate Ingo and Centexbi thoughts but reinstall of OS is simply not an option.

As a developer, one has a large number of apps, tools etc installed and if the system (as in my case), is very stable apart from SQL2005 install then I would rather ditch install of SQL as opposed to spending a number of days re-assembling the PC OS etc.

Reinstall of SQL2005 has not resolved this - even from the point of painstakenly removing registry entries etc and trying to install as virgin. Maybe MS should provide a proper installer which will remove the masses of junk registry entries SQL2005 leaves behind when you unistall. How about a 'SQL2005 clean reg / os' tool - bit like what Symantec do for their AV?

This is the real world and time is as scarce as money. 'We' all spend far too much time working in this 'black art' industry and shame MS do not do more to help us!

|||Hi ComputerSolutions
An OS-Reinstall is of course _never_ an option.
I can only support your idea of a cleanup-tool.
Greets,
Ingo

cannot install integration services

Hi!

During the installation of integration services (SQL 05 Developer RTM) I get the following error:

TITLE: Microsoft SQL Server 2005 Setup

Failed to install and configure assemblies C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: Failed to generate type library 'C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.tlb' for 'Microsoft.SqlServer.MSMQTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.

I had CTPs of SQL05 and VS05 installed before, but uninstalled them with the cleanup tool.

yeh, I had this issue and found a resolution... read my thread about the installation issue resolved (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1)

the other workaround really is not to select to install integration services but to install it after everything else|||Thank you for your fast reply. I'm trying to install SQL05 Developer on Windows XP Pro SP2. I forgot to mention that in my first post. So I think your solution won't help me :(|||I see!
Well, try to install everything except integration services and then install integration services after everything

The thread I created STILL DOES apply to WS2003, due to installed components still breaking and during installation (I know you are running XP so you do not need to go through the thread!) :)|||

I already did that. I uninstalled Integration Services (during the first installation, I ignored the error message, but IS didn't work then), and tried to reinstall them. I always get the same error.

|||have you:

tried completly removing SQL Server 2005.
Then installing it WITHOUT the integration and reporting services? :-)|||- I uninstalled SQL server, including SQL Native Client and Everything I found that had "sql" in it's name.
- rebooted
- Installed just the SQL Server engine, Clients, Documentation
- rebooted
- Instaled everything except Integration Services
- rebooted
- Tried to install Integration Services, I still get the same error|||Hi Mathias,

I am in exactly the same situation as you. If I find anything I will post here.

Regards,

Chris|||Thank you. Good luck! :)|||Hi all,
I had the same problem. I think it was because of a incomplete uninstall of a previous Beta Version. Check if in there an old version of one of the "Microsoft.SqlServer.DtsXXX" Assemblies (take a look at the Last Modified Date in the Properties) in the Global Assembly Cache.
If there is one or more, delete them.
If you can't delete them because there are references, eliminate these first (can be done by deleting some registry-keys, but I don't know exactly which ones).
Then, after all old assemblies are removed, reinstall the Integration Services using the Setup. Should then work flawlessy.
Greetings,
Ingo
|||Have the same problem with Win2K Pro, SQL 2000 already installed and then SQL
2005 DevEd

After uninstalling SQL2005 a few times in order to get it to install with this error, which also breaks Enterprise Manager on SQL2000 in the process, I then end up reinstalling both. What a pain!

Eventually, after many hours buggering around, got SQL2000 and SQL2005 working but this 'install bug' or 'another MS featurett' (which is still not resolved from what I can see), is such a time waster, in what already is limited!

Does anyone know of an easy fix or patch, rather than have to re-install IS again and possibly cause other issues?
|||This is somewhat related to the problem I had. See my resolution with SSIS at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124884&SiteID=1. Reinstall OS and then install SQL 2005 RTM Dev Edtion.

I still want to configure a mixed environment with SQL2000 SP4 and SQL2005 RTM Dev Edition on Win XP Pro SP2. I have tried it and cannot use SSIS to configure connections.

If someone has a workaround, please post but I do not want to go thru the pain of reinstalling the OS and my dev tools again.|||Hi centexbi,
I have SQL2000 and SQL2005 working side-by-side on my XP SP2.
Don't know if this is a solution for you and if it works, but you might give it a try:
- Completely remove anything that has to do with .NET (all framework version, VisualStudio, etc.)
- Ensure that you no longer have the directories %SYSTEMROOT%\assembly und %SYSTEMROOT%\Microsoft.NET, delete them if necessary
- Reinstall SQL2000 including SP4
- Try to install SQL2005
Greets,
Ingo
|||Appreciate Ingo and Centexbi thoughts but reinstall of OS is simply not an option.

As a developer, one has a large number of apps, tools etc installed and if the system (as in my case), is very stable apart from SQL2005 install then I would rather ditch install of SQL as opposed to spending a number of days re-assembling the PC OS etc.

Reinstall of SQL2005 has not resolved this - even from the point of painstakenly removing registry entries etc and trying to install as virgin. Maybe MS should provide a proper installer which will remove the masses of junk registry entries SQL2005 leaves behind when you unistall. How about a 'SQL2005 clean reg / os' tool - bit like what Symantec do for their AV?

This is the real world and time is as scarce as money. 'We' all spend far too much time working in this 'black art' industry and shame MS do not do more to help us!

|||Hi ComputerSolutions
An OS-Reinstall is of course _never_ an option.
I can only support your idea of a cleanup-tool.
Greets,
Ingo

cannot install integration services

Hi!

During the installation of integration services (SQL 05 Developer RTM) I get the following error:

TITLE: Microsoft SQL Server 2005 Setup

Failed to install and configure assemblies C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: Failed to generate type library 'C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.tlb' for 'Microsoft.SqlServer.MSMQTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.

I had CTPs of SQL05 and VS05 installed before, but uninstalled them with the cleanup tool.

yeh, I had this issue and found a resolution... read my thread about the installation issue resolved (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1)

the other workaround really is not to select to install integration services but to install it after everything else|||Thank you for your fast reply. I'm trying to install SQL05 Developer on Windows XP Pro SP2. I forgot to mention that in my first post. So I think your solution won't help me :(|||I see!
Well, try to install everything except integration services and then install integration services after everything

The thread I created STILL DOES apply to WS2003, due to installed components still breaking and during installation (I know you are running XP so you do not need to go through the thread!) :)|||

I already did that. I uninstalled Integration Services (during the first installation, I ignored the error message, but IS didn't work then), and tried to reinstall them. I always get the same error.

|||have you:

tried completly removing SQL Server 2005.
Then installing it WITHOUT the integration and reporting services? :-)|||- I uninstalled SQL server, including SQL Native Client and Everything I found that had "sql" in it's name.
- rebooted
- Installed just the SQL Server engine, Clients, Documentation
- rebooted
- Instaled everything except Integration Services
- rebooted
- Tried to install Integration Services, I still get the same error|||Hi Mathias,

I am in exactly the same situation as you. If I find anything I will post here.

Regards,

Chris|||Thank you. Good luck! :)|||Hi all,
I had the same problem. I think it was because of a incomplete uninstall of a previous Beta Version. Check if in there an old version of one of the "Microsoft.SqlServer.DtsXXX" Assemblies (take a look at the Last Modified Date in the Properties) in the Global Assembly Cache.
If there is one or more, delete them.
If you can't delete them because there are references, eliminate these first (can be done by deleting some registry-keys, but I don't know exactly which ones).
Then, after all old assemblies are removed, reinstall the Integration Services using the Setup. Should then work flawlessy.
Greetings,
Ingo
|||Have the same problem with Win2K Pro, SQL 2000 already installed and then SQL
2005 DevEd

After uninstalling SQL2005 a few times in order to get it to install with this error, which also breaks Enterprise Manager on SQL2000 in the process, I then end up reinstalling both. What a pain!

Eventually, after many hours buggering around, got SQL2000 and SQL2005 working but this 'install bug' or 'another MS featurett' (which is still not resolved from what I can see), is such a time waster, in what already is limited!

Does anyone know of an easy fix or patch, rather than have to re-install IS again and possibly cause other issues?
|||This is somewhat related to the problem I had. See my resolution with SSIS at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124884&SiteID=1. Reinstall OS and then install SQL 2005 RTM Dev Edtion.

I still want to configure a mixed environment with SQL2000 SP4 and SQL2005 RTM Dev Edition on Win XP Pro SP2. I have tried it and cannot use SSIS to configure connections.

If someone has a workaround, please post but I do not want to go thru the pain of reinstalling the OS and my dev tools again.|||Hi centexbi,
I have SQL2000 and SQL2005 working side-by-side on my XP SP2.
Don't know if this is a solution for you and if it works, but you might give it a try:
- Completely remove anything that has to do with .NET (all framework version, VisualStudio, etc.)
- Ensure that you no longer have the directories %SYSTEMROOT%\assembly und %SYSTEMROOT%\Microsoft.NET, delete them if necessary
- Reinstall SQL2000 including SP4
- Try to install SQL2005
Greets,
Ingo
|||Appreciate Ingo and Centexbi thoughts but reinstall of OS is simply not an option.

As a developer, one has a large number of apps, tools etc installed and if the system (as in my case), is very stable apart from SQL2005 install then I would rather ditch install of SQL as opposed to spending a number of days re-assembling the PC OS etc.

Reinstall of SQL2005 has not resolved this - even from the point of painstakenly removing registry entries etc and trying to install as virgin. Maybe MS should provide a proper installer which will remove the masses of junk registry entries SQL2005 leaves behind when you unistall. How about a 'SQL2005 clean reg / os' tool - bit like what Symantec do for their AV?

This is the real world and time is as scarce as money. 'We' all spend far too much time working in this 'black art' industry and shame MS do not do more to help us!

|||Hi ComputerSolutions
An OS-Reinstall is of course _never_ an option.
I can only support your idea of a cleanup-tool.
Greets,
Ingo

cannot install integration services

Hi!

During the installation of integration services (SQL 05 Developer RTM) I get the following error:

TITLE: Microsoft SQL Server 2005 Setup

Failed to install and configure assemblies C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: Failed to generate type library 'C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.tlb' for 'Microsoft.SqlServer.MSMQTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.

I had CTPs of SQL05 and VS05 installed before, but uninstalled them with the cleanup tool.

yeh, I had this issue and found a resolution... read my thread about the installation issue resolved (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1)

the other workaround really is not to select to install integration services but to install it after everything else|||Thank you for your fast reply. I'm trying to install SQL05 Developer on Windows XP Pro SP2. I forgot to mention that in my first post. So I think your solution won't help me :(|||I see!
Well, try to install everything except integration services and then install integration services after everything

The thread I created STILL DOES apply to WS2003, due to installed components still breaking and during installation (I know you are running XP so you do not need to go through the thread!) :)|||

I already did that. I uninstalled Integration Services (during the first installation, I ignored the error message, but IS didn't work then), and tried to reinstall them. I always get the same error.

|||have you:

tried completly removing SQL Server 2005.
Then installing it WITHOUT the integration and reporting services? :-)|||- I uninstalled SQL server, including SQL Native Client and Everything I found that had "sql" in it's name.
- rebooted
- Installed just the SQL Server engine, Clients, Documentation
- rebooted
- Instaled everything except Integration Services
- rebooted
- Tried to install Integration Services, I still get the same error|||Hi Mathias,

I am in exactly the same situation as you. If I find anything I will post here.

Regards,

Chris|||Thank you. Good luck! :)|||Hi all,
I had the same problem. I think it was because of a incomplete uninstall of a previous Beta Version. Check if in there an old version of one of the "Microsoft.SqlServer.DtsXXX" Assemblies (take a look at the Last Modified Date in the Properties) in the Global Assembly Cache.
If there is one or more, delete them.
If you can't delete them because there are references, eliminate these first (can be done by deleting some registry-keys, but I don't know exactly which ones).
Then, after all old assemblies are removed, reinstall the Integration Services using the Setup. Should then work flawlessy.
Greetings,
Ingo|||Have the same problem with Win2K Pro, SQL 2000 already installed and then SQL
2005 DevEd

After uninstalling SQL2005 a few times in order to get it to install with this error, which also breaks Enterprise Manager on SQL2000 in the process, I then end up reinstalling both. What a pain!

Eventually, after many hours buggering around, got SQL2000 and SQL2005 working but this 'install bug' or 'another MS featurett' (which is still not resolved from what I can see), is such a time waster, in what already is limited!

Does anyone know of an easy fix or patch, rather than have to re-install IS again and possibly cause other issues?|||This is somewhat related to the problem I had. See my resolution with SSIS at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124884&SiteID=1. Reinstall OS and then install SQL 2005 RTM Dev Edtion.

I still want to configure a mixed environment with SQL2000 SP4 and SQL2005 RTM Dev Edition on Win XP Pro SP2. I have tried it and cannot use SSIS to configure connections.

If someone has a workaround, please post but I do not want to go thru the pain of reinstalling the OS and my dev tools again.|||Hi centexbi,
I have SQL2000 and SQL2005 working side-by-side on my XP SP2.
Don't know if this is a solution for you and if it works, but you might give it a try:
- Completely remove anything that has to do with .NET (all framework version, VisualStudio, etc.)
- Ensure that you no longer have the directories %SYSTEMROOT%\assembly und %SYSTEMROOT%\Microsoft.NET, delete them if necessary
- Reinstall SQL2000 including SP4
- Try to install SQL2005
Greets,
Ingo|||Appreciate Ingo and Centexbi thoughts but reinstall of OS is simply not an option.

As a developer, one has a large number of apps, tools etc installed and if the system (as in my case), is very stable apart from SQL2005 install then I would rather ditch install of SQL as opposed to spending a number of days re-assembling the PC OS etc.

Reinstall of SQL2005 has not resolved this - even from the point of painstakenly removing registry entries etc and trying to install as virgin. Maybe MS should provide a proper installer which will remove the masses of junk registry entries SQL2005 leaves behind when you unistall. How about a 'SQL2005 clean reg / os' tool - bit like what Symantec do for their AV?

This is the real world and time is as scarce as money. 'We' all spend far too much time working in this 'black art' industry and shame MS do not do more to help us!|||Hi ComputerSolutions
An OS-Reinstall is of course _never_ an option.
I can only support your idea of a cleanup-tool.
Greets,
Ingo

cannot install integration services

Hi!

During the installation of integration services (SQL 05 Developer RTM) I get the following error:

TITLE: Microsoft SQL Server 2005 Setup

Failed to install and configure assemblies C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: Failed to generate type library 'C:\Programme\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.tlb' for 'Microsoft.SqlServer.MSMQTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.

I had CTPs of SQL05 and VS05 installed before, but uninstalled them with the cleanup tool.

yeh, I had this issue and found a resolution... read my thread about the installation issue resolved (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1)

the other workaround really is not to select to install integration services but to install it after everything else|||Thank you for your fast reply. I'm trying to install SQL05 Developer on Windows XP Pro SP2. I forgot to mention that in my first post. So I think your solution won't help me :(|||I see!
Well, try to install everything except integration services and then install integration services after everything

The thread I created STILL DOES apply to WS2003, due to installed components still breaking and during installation (I know you are running XP so you do not need to go through the thread!) :)|||

I already did that. I uninstalled Integration Services (during the first installation, I ignored the error message, but IS didn't work then), and tried to reinstall them. I always get the same error.

|||have you:

tried completly removing SQL Server 2005.
Then installing it WITHOUT the integration and reporting services? :-)|||- I uninstalled SQL server, including SQL Native Client and Everything I found that had "sql" in it's name.
- rebooted
- Installed just the SQL Server engine, Clients, Documentation
- rebooted
- Instaled everything except Integration Services
- rebooted
- Tried to install Integration Services, I still get the same error|||Hi Mathias,

I am in exactly the same situation as you. If I find anything I will post here.

Regards,

Chris|||Thank you. Good luck! :)|||Hi all,
I had the same problem. I think it was because of a incomplete uninstall of a previous Beta Version. Check if in there an old version of one of the "Microsoft.SqlServer.DtsXXX" Assemblies (take a look at the Last Modified Date in the Properties) in the Global Assembly Cache.
If there is one or more, delete them.
If you can't delete them because there are references, eliminate these first (can be done by deleting some registry-keys, but I don't know exactly which ones).
Then, after all old assemblies are removed, reinstall the Integration Services using the Setup. Should then work flawlessy.
Greetings,
Ingo|||Have the same problem with Win2K Pro, SQL 2000 already installed and then SQL
2005 DevEd

After uninstalling SQL2005 a few times in order to get it to install with this error, which also breaks Enterprise Manager on SQL2000 in the process, I then end up reinstalling both. What a pain!

Eventually, after many hours buggering around, got SQL2000 and SQL2005 working but this 'install bug' or 'another MS featurett' (which is still not resolved from what I can see), is such a time waster, in what already is limited!

Does anyone know of an easy fix or patch, rather than have to re-install IS again and possibly cause other issues?|||This is somewhat related to the problem I had. See my resolution with SSIS at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124884&SiteID=1. Reinstall OS and then install SQL 2005 RTM Dev Edtion.

I still want to configure a mixed environment with SQL2000 SP4 and SQL2005 RTM Dev Edition on Win XP Pro SP2. I have tried it and cannot use SSIS to configure connections.

If someone has a workaround, please post but I do not want to go thru the pain of reinstalling the OS and my dev tools again.|||Hi centexbi,
I have SQL2000 and SQL2005 working side-by-side on my XP SP2.
Don't know if this is a solution for you and if it works, but you might give it a try:
- Completely remove anything that has to do with .NET (all framework version, VisualStudio, etc.)
- Ensure that you no longer have the directories %SYSTEMROOT%\assembly und %SYSTEMROOT%\Microsoft.NET, delete them if necessary
- Reinstall SQL2000 including SP4
- Try to install SQL2005
Greets,
Ingo|||Appreciate Ingo and Centexbi thoughts but reinstall of OS is simply not an option.

As a developer, one has a large number of apps, tools etc installed and if the system (as in my case), is very stable apart from SQL2005 install then I would rather ditch install of SQL as opposed to spending a number of days re-assembling the PC OS etc.

Reinstall of SQL2005 has not resolved this - even from the point of painstakenly removing registry entries etc and trying to install as virgin. Maybe MS should provide a proper installer which will remove the masses of junk registry entries SQL2005 leaves behind when you unistall. How about a 'SQL2005 clean reg / os' tool - bit like what Symantec do for their AV?

This is the real world and time is as scarce as money. 'We' all spend far too much time working in this 'black art' industry and shame MS do not do more to help us!|||Hi ComputerSolutions
An OS-Reinstall is of course _never_ an option.
I can only support your idea of a cleanup-tool.
Greets,
Ingo

Cannot insert explicit value for identity...

I am developing an integration process between two databases. One of
them is a SQL Server 2000 and the other is using MSDE 2000. The
integration process is done in C# (VS2003).

The main database is the SQL Server, the MSDE will contain a really
small subset of the data found on the main. To help diminish the amount
of time taken to develop an integration process between those
databases, the same structure are found on both side. The only
difference, when I insert data in the MSDE from the SQL Server, I set
the IDENTITY_INSERT to ON and use the same IDs found on the SQL Server.

I can insert one set of data without problem, but from there, if I try
again, I will always receive the "Cannot insert explicit value for
identity column in table ... when IDENTITY_INSERT is set to OFF." I
saw on Microsoft website the article ID 878501; I noticed I was using
MSDE sp3, I upgraded to SP4... and I still have the problem.

I know, when I call the update function on the sqldataadapter, the
adapters contain the IDENTITY_INSERT ON and it's set to OFF after the
insert. The "Cannot insert..." error is the only one I received.

Can anyone help me on that issue? Take note that this approach was
used because of customer requirements; the size of the database also
causes some problem (over 200 tables) and we decided to use the same
structure on both side to minimize the support time.Just thought about posting the SQL command in the adapter, it will look
something like:

SET IDENTITY_INSERT myTable ON; INSERT INTO myTable (myId, myCol1)
VALUES (@.myId, @.myCol1); SELECT myId, myCol1 FROM myTable WHERE (myId =
@.@.IDENTITY); SET IDENTITY_INSERT myTable OFF;

I hope that will help !|||(nicolas.bouchard@.gmail.com) writes:
> I am developing an integration process between two databases. One of
> them is a SQL Server 2000 and the other is using MSDE 2000. The
> integration process is done in C# (VS2003).
> The main database is the SQL Server, the MSDE will contain a really
> small subset of the data found on the main. To help diminish the amount
> of time taken to develop an integration process between those
> databases, the same structure are found on both side. The only
> difference, when I insert data in the MSDE from the SQL Server, I set
> the IDENTITY_INSERT to ON and use the same IDs found on the SQL Server.

The first reaction is: have you considered replication?

The second reaction is: skip IDENTITY, and generate the IDs on your
own. That is a trivial business. It's only if you have a high INSERT
rate from simultaneous processes that you need IDENTITY, as rolling
your own key can result in contention issues.

IDENTITY is convenient at times, but not in a situation like this. It
causes more problems than it solves.

Yet, an alternative is to use bulk load to extract and load data.
Moving one at time as you do not is not terribly effecient. Which may
not matter if the data size is moderate, but for something like
10-20 MB it could. With BCP it's easy to insert explicit IDENTITY
values with the -E option.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Hi,

thanks for the reply!

We did considered replication but for a reason unknown to me, we didn't
choose that solution; I can still imagine why, due to the fact we had
to develop an ownership process on certain tables, some tables are
owned by the main and others by the MSDE system and again, depending on
the state of the system.

The system (the main one) will be used by 200+ persons during the day,
the insert rate may be quite a problem with our own generated ids.

Until few days ago, I didn't know of bulk load, I will definitely look
into that for future projects. For this project, the amount of data
transfered between databases are not that big (talking less than 1MB
for the first transfer, then it will be almost nothing).

About my problem, I fixed it and I had few more tests to do; I was
planning to post the fix to my problem here, hoping it will help
someone else. I tried to do too much instructions in one command (my
guess is). Instead of doing everything in the same SQLCommand, I
modified the command to only manage the insert and the select to get
the new values; before calling the update command of the DataAdapter, I
disable the IDENTITY_INSERT then after the comand I enable it.

As I said, thanks for the quick answer !

Nicolas Bouchard