MartyConnelly
martyconnelly at shaw.ca
Sat Feb 18 19:38:56 CST 2006
Installing SQL Server 2005 from BOL http://msdn2.microsoft.com/en-us/library/ms143516.aspx You couuld try initially installing only the basic components like the database engine. Then add the other bits. You could try to install the Microsoft SQL Server 2005 Enterprise Evaluation Edition 180 day rather than the standard one But it is a 1 gig download, gag... http://www.microsoft.com/downloads/details.aspx?familyid=6931fa7f-c094-49a2-a050-2d07993566ec&displaylang=en Sounds like you may have to get the win server 2003 SP1 CD. These problems generally crop up with a previous Beta installation and occured between Beta 1 and 2 of SQL Express. reguiring a rigamorole uninstall. Jim Lawrence wrote: >Hi Marty: > >Thanks for the info on named instances but I had already reviewed that and >felt it would be better to only have one version on line. > >There is supposed to be the latest version of .Net Framework 2.0 on the SQL >Server 2005 installation DVD. The pre-install went through the process of >installing all foundation code and .Net framework installed without >incident. > >I am trying to install this MS SQL Standard edition onto a Windows standard >server 2003 SP1, so there should be no incompatible issues. > >I have also attempted to re-register a couple of related .Net plug-in >assemblies and a library on the chance that their setting may not have taken >properly: > >regasm extensibility.dll >regasm vslangproj.dll >regtlb vslangproj.tlb > >...the above was successful but the overall prognosis was not. > >Here is something that other individuals have attempted when a very similar >error had occurred: > >http://forums.microsoft.com/MSDN/ShowPost.aspx?PageIndex=1&SiteID=1&PostID=1 >36467 > >...and... > >http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134853&SiteID=1 > >...that does not work in this situation. > >Even though stated otherwise there appears to be no solid resolution other >than a gloomy OS re-install. > >These types of problems have been following along where ever an Express >version has preceded an upgrade. I have learned my lesson and will only >recommend the use of Express versions within their own virtual PC or request >an OS install package solution. It is sad but I believe MS has rushed these >products to market and have basically out-smarted themselves. > >Thanks so much for your help. I can not help but feel that I have missed >some obvious fix so if you have any revelations or insights I will be happy >to entertain them. > >Jim > > >-----Original Message----- >From: dba-sqlserver-bounces at databaseadvisors.com >[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of >MartyConnelly >Sent: February 18, 2006 10:56 AM >To: dba-sqlserver at databaseadvisors.com >Subject: Re: [dba-SQLServer] DTS > >Are you doing an upgrade or a side by side install of SQL 2000 and 2005? >side by side is supposed to require named instances or installs >what ever that is? > >Microsoft SQL Server 2005 Upgrade Advisor >http://www.microsoft.com/downloads/details.aspx?familyid=6107C27A-662C-4319- >AFE7-B52D1568C30A&displaylang=en >Do you have most recent version Microsoft .NET Framework 2.0 installed > >The most stable version of SQL 2005 might be the Developer Edition >rather than Standard or Enterprise. >At least it is the only version that will install on WinXP Home aside >from SQL Express. > >Jim Lawrence wrote: > > > >>Hi Marty: >> >>Well that utility sure did the trick. There were no references for the >>Express SQL, in the 'Add/Remove' file section, any directories and no >>obvious references in the registry but the utility pulled up at least 6 >>items/references. >> >>Thanks for the heads up. >> >>The installation went a lot further this time (an hour and a half later, >>approximately) but it finally hung up saying: >> >><error> >>Failed to install and configure assemblies C:\Program Files\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:\Program >>Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.tlb' >>for 'Microsoft.SqlServer.MSMQTask, Version=9.0.242.0, Culture=neutral, >>PublicKeyToken=89845dcd8080cc91'. >></error> >> >>It is fortunate that I have the rest of the weekend to get installation >>completed so now it is back to the web for answers. I am nearly at the >> >> >point > > >>of formatting this server and starting again... a task of last resort; set >>aside for Sunday evening. >> >>Again, thank you for your help as the process would not have got this far. >> >>Jim >> >>-----Original Message----- >>From: dba-sqlserver-bounces at databaseadvisors.com >>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of >>MartyConnelly >>Sent: February 16, 2006 9:23 PM >>To: dba-sqlserver at databaseadvisors.com >>Subject: Re: [dba-SQLServer] DTS >> >>If you are having trouble removing bits and pieces of an install made >>via the windows installer, >>Locate and run the MS Windows Installer CleanUp Utility msicuu2.exe. >>Some users have said they removed Symantec after faulty install and >>Visio without a necessary CD. >>Here is a brief article on it and download URL >>http://techrepublic.com.com/5100-10877_11-6030075.html?tag=nl.e064 >> >>or have a look through MSDN SQL Express Blog >>http://blogs.msdn.com/sqlexpress/archive/2004/07/04/172956.aspx >> >>Jim Lawrence wrote: >> >> >> >> >> >>>Hi Marty: >>> >>>Thanks for the heads up on that. I had found the new SSIS Integration >>>Services but had not yet discovered the section legacy folder. (In my >>>opinion MS SQL has gone a little over the top with features and >>>functionality... it is starting to look like Enterprise Oracle and not the >>>type little powerful SQL 2000.) >>> >>>Jim >>> >>>Now I have a heck of a problem removing some old versions of SQL Express >>> >>> >>> >>> >>>from a client's server. (Wished the beta stuff had been installed in a >> >> >> >> >>>Virtual PC.) I have just re-run VS-uninstall-betas after everything was >>>carefully removed through the Control Panel. (twice??) >>> >>>-----Original Message----- >>>From: dba-sqlserver-bounces at databaseadvisors.com >>>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of >>>MartyConnelly >>>Sent: February 16, 2006 8:15 PM >>>To: dba-sqlserver at databaseadvisors.com >>>Subject: Re: [dba-SQLServer] DTS >>> >>>You can run DTS (SS2000) from SS2005. >>>Under 2005 Mgt Studio is a folder called Legacy under Management folder. >>>SSIS Integration Services is the new name for the DTS >>> >>>Jim Lawrence wrote: >>> >>> >>> >>> >>> >>> >>> >>>>Hi All: >>>> >>>>I have just upgraded a client's SQL 2000 DB to SQL 2005 and a number of >>>>objects have been changed, modified or 'wandered'. One issue that is a >>>> >>>> >>>> >>>> >>>> >>>> >>>major >>> >>> >>> >>> >>> >>> >>>>problem is the original (2000) had a number of DTS executable files that >>>>were used to import some raw data through various function and SP calls. >>>> >>>>The DTS files have disappeared or when it is manually attempted to >>>> >>>> >>>> >>>> >>>> >>>> >>>re-create >>> >>> >>> >>> >>> >>> >>>>the process again the results seem to disappear(?) >>>> >>>>There must be so obvious reason for this but at this late hour it is not >>>>obvious. >>>> >>>>Any help or comments would be greatly appreciated... (I am going for a >>>>coffee.) >>>> >>>>Jim >>>> >>>>_______________________________________________ >>>>dba-SQLServer mailing list >>>>dba-SQLServer at databaseadvisors.com >>>>http://databaseadvisors.com/mailman/listinfo/dba-sqlserver >>>>http://www.databaseadvisors.com >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> >> >> >> >> > > > -- Marty Connelly Victoria, B.C. Canada