Showing posts with label ctp. Show all posts
Showing posts with label ctp. Show all posts

Thursday, March 29, 2012

Cannot Remove SQL 2005 June CTP

I have SQL 2005 June CTP installed and running. I previously had VS 2005 CTP installed as well. I removed VS with the beta removal tool and installed the release version. I am now trying to remove SQL and cannot do it.

First I tried Add / Remove programs. I chose remove for SQL 2005 and it removed the entry from Add / Remove programs but did nothing else. I then tried the beta removal tool sqlbuw.exe on the CD which detectes 3 instances of SQL 2005 but when it tries to remove them it says "There are no SQL Server 2005 or .NET Framework components to uninstall. You may now run the setup wizard to install new instances."

When I run the setup wizard it says i must uninstall the previous incompatible beta versions first.

Talk about catch 22. Are there instructions for manually removing SQL 2005 June CTP?

Thanks
MartinMartin,

It sounds like you got yourself into trouble by removing VS prior to SQL Server. The SQL Server uninstall requires that .Net Framework 2.0 still be present on the machine. The reason for this is some assemblies are placed in the GAC (Global Assembly Cache) and the only way to clean up the GAC is through the .Net Framework.

We have an uninstall script that I can send you. You should know that this script is not supported and is not tested to a full release level. We've been using it internally and I've given it out to some folks - we've had no reports of the script causing any machine corruption, however, this is a run at your own risk deal. If you're interested in the script email me at dan.jones@.microsoft.com.

Cheers,
Dan|||Unfortuantly the script did not work and a rebuild was required. At least my computer is faster now :o)

Martin

Monday, March 19, 2012

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 open a connection with SQL Server 2005 Developer Edition.

I have installed on one computer Sql Server 2005 Developer Edition (CTP Version) together with a Visual Studio 2005 Beta Edition (July Version) and after configuration some properties by example the Network access, I had a lot of errors from the SQL Server Management Studio received(The most of them are a Connection timeout error but others errors too).
In the same time I have made a test program to test the new SQL Server 2005 using DB Library or ATL OLE DB Consumer Templates.
The Both test programs are not running because I cannot open a connection on the SQL Server.
I've tried using the Windows Authentification and the SQL Server Authentification too. The both methods are not able to connect with the SQL Server.
The Programs are written in Visual C++ under the Visual Studio 2005.
I need help to my problems!
First why I cannot connect to the Sql Server. With DB Library example I was able to do it with a Beta Version from SQL Server 2005 but not any more with the CTP Version.
Why I cannot connect with the ATL OLE DB Consumer Templates ?
I want to hear some experiences from others developers with this CTP Version from SQL Server 2005.
It is really so buggy or it is not compatible with Window Server 2003 or it is because after installing the SQL Server 2005 I have made an update of the Visual Studio 2005 to be able to create Projects in Visual C++ and run some examples ?
The problem was that with the Visual Studio that it is coming with the SQL Server I was not able to create any Project under Visual C++ because I was receiving an error that the Template for the Visual C++ failed.
I need help !

For the detailed information about the Versions please read the next list:

Microsoft SQL Server Management Studio - Version 9.0.1187.
MDAC - Version 2000.086.1830.00(srv03_sp1_rtm.050324_1447)
Microsoft .Net Framework - Version 2.0.50712.6.
Microsoft Visual Studio 2005 - Version 8.0.50712.6(lab23df.050712-0600)

The Operating System it is an Windows Server 2003 Professional Version with SP1.
What are the specific errors you are seeing when you try to connect to SQL Server. Could you please post your sample code
SQL Server projects are only available in Visual Studio pro. SKU and above. What SKU of Visual Studio are you using. Are you able to get C# and VB.NET SQL Server projects working?

Thanks,
-Vineet.|||So first what you've asked:
The Visual Studio Version it is :
Team Edition for Software Architects. Version 8.0.50712.6(lab23df.050712-0600)
It is installed from MSDN Team Suite DVD Beta 2 Version.
The Windows it is Windows 2003 Server Enterprise Edition(first time I was wrong, it was no Profesional version) with SP1.
The c# or VB.Net projects are working just fine. Only the connection to Sql Server it is not working.
The Sample code I will send you in the project on your email address:vineetr@.microsoft.com. The project it is imported from Visual Studio 6.0 Samples and coverted to Visual Studio 2005. It is writed in unmanaged code in Visual c++. Please don't forget to copy the db library files that are included in the archive on C:\ or to change the path for include in the code.
In the Sample I am using two tables here it is the SQL code to create the tables:

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[TestTable]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)

drop table [dbo].[TestTable]

GO

CREATE TABLE [dbo].[TestTable] (

[Id] uniqueidentifier ROWGUIDCOL NOT NULL ,

[Text1] [varchar] (10) COLLATE Latin1_General_CI_AS NOT NULL ,

[Text2] [char] (10) COLLATE Latin1_General_CI_AS NOT NULL ,

[Int1] [int] NOT NULL ,

[Float1] [float] NOT NULL ,

[Short1] [smallint] NOT NULL

) ON [PRIMARY]

GO

CREATE CLUSTERED INDEX [index_clustered] ON [dbo].[TestTable]([Id] DESC ) ON [PRIMARY]

GO

CREATE INDEX [index_mixt] ON [dbo].[TestTable]([Int1] DESC , [Short1] DESC ) ON [PRIMARY]

GO

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[TestTable2]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)

drop table [dbo].[TestTable2]

GO

CREATE TABLE [dbo].[TestTable2] (

[autoid] [int] IDENTITY (1, 1) NOT NULL ,

[value1] [int] NULL ,

[value2] [int] NULL

) ON [PRIMARY]

GO

ALTER TABLE [dbo].[TestTable2] WITH NOCHECK ADD

CONSTRAINT [PK_TestTable2] PRIMARY KEY CLUSTERED

(

[autoid]

) ON [PRIMARY]

GO


In the mean time I have made some more research trying to find where the problem it is located. In the Sql Server components or in the library components that I am using in my code example (DB Library and ATL OLE DB Comsumer Templates library) and I found the next problem:
In the Microsoft Management Studio I have made the next four steps:
1. Create the tables ruuning the upper script. After this you will find in the database two sample tables TestTable and TestTable2.
2.Run the Query : Select * from TestTable2. No result but no error too.
3.Run the Query :Insert into testTable2 values (1,1). No I get allready the timeout Error and the query it is making the insert in the Table (Unexpected behavior).
4.Run the Query again: Select * from TestTable2. To check and see if the insert it is made. Now we can see in the table one row with the just inserted result. I got an error and the query it it succesfully executed.
Please see the archive that I will send you in there you will find the print screens.

So my opinion it is that the problem it is in the SQL Server itself.
This Timeout error I got it in the Microsoft Management Studio when I try to update some properties from Databases, Updating properties from the Server itself or Scripting a table etc...

I my head it stays one modification that I have made in the timeout value for the connections in the SQL Server properties. I have seted the value to 6000 and after a while again to 0(no limit). And after this modification I've retarted the computer (all the SQL server services should read again the settings after restart).

This can be one reason. The second reason can be: I have made some modification for the protocolls to access the SQL Server from another remote computer. I have read that default it cannot be accesed remote.
Anyhow I have undone all the modification and still the SQL it not reacting normally (when I access the Sql Server locally- or just from the Microsoft Management Studio ).

So please read your email to get the sample code and the print screen with th errors. I f you need more print screen with other error please tell me.
I wait for your help.

Thanks,
Vasile.|||I want help.
Do you need more infos ?
Have you found something ?
Can somebody help ?
Maybe I should wait for the release version.

Sunday, March 11, 2012

cannot login to SQLExpress 2005 help please!!

I just installed SQL express couple of days ago.

Then I tried using SQL Management Express Studio CTP. I select

SQL Authetication, key in the correct password but

it says "A connection was succesfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error:0 - No process is on the other end of the pipe). (Microsoft Sql Error: 233)

When i tried windows authetication, it say cannot initialise SSPI package.

I went to download the windows fix after reading this article

http://www.pcreview.co.uk/forums/thread-1714474-2.php

since google on SSPI has no useful results.... I will be grateful if microsoft people fix this bug with SQL Server 2005 express cos newbies will not be able to understand what

SSPI means.... and failure to install and use an easy software like MS SQL Server will lead to people running to Mysql . sighed.

Thursday, March 8, 2012

Cannot install Workstation components, fails on report server upgrade

I have hard time installing July CTP as it is failing on workstation component and fails on report server upgrade.

Any ideas for ther resolution.

Property(S): AdministratorsGroup = BUILTIN\Administrators
Property(S): PerformanceMontiorUsersGroup = BUILTIN\Performance Monitor Users
Property(S): PerformanceLogUsersGroup = BUILTIN\Performance Log Users
Property(S): UsersGroup = BUILTIN\Users
Property(S): SCMNetworkServiceAccount = NT AUTHORITY\NetworkService
Property(S): SCMLocalServiceAccount = NT AUTHORITY\LocalService
Property(S): IISCHECKED = 1
Property(S): SqlIISInstalled = 1
Property(S): SqlASPNETInstalled = 1
Property(S): SqlCOMPlusInstalled = 1
Property(S): RSPREREQUISITECHECKED = 1
Property(S): RSSqlPoolLimit = 100
Property(S): RSGUIDVALUE = {ec3b61d7-2813-485b-a55d-e0c931740946}
Property(S): RemoveFeatureList = Client_Components,Connectivity,SQL_Tools,SQL_WarehouseDevWorkbench,SDK,SQLXML,Tools_Legacy,TOOLS_BC_DEP,SQL_Documentation,SQL_Samples,SQL_BooksOnline,SQL_DatabaseSamples
Property(S): SqlOriginalMachineName = TAHITI
Property(S): Namechecksumcommon_32 = Developer Edition
Property(S): SqlSubDir = \MSSQL
Property(S): EditionTypechecksumcommon_32 = Developer Edition
Property(S): Namechecksumtools = Developer Edition
Property(S): EditionTypechecksumtools = Developer Edition
Property(S): ValidMOFInstanceName = 1
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer
Property(S): RSVirtualDirectoryManager = Reports
Property(S): SQLStatusBeforeInstall = 3
Property(S): SOURCEDIR = Z:\Tools\Setup\
Property(S): SourcedirProduct = {D6251ACA-3FD4-49D1-8FCF-182B980B19E3}
Property(S): HxDs_Tmp_3643236F_FC70_11D3_A536_0090278A1BB8 = C:\DOCUME~1\abahl\LOCALS~1\Temp\HxEA.tmp
Property(S): HxDs_Tmp_Hash_3643236F_FC70_11D3_A536_0090278A1BB8 = B40B0DC6C3C19C68E0101E0E2A647F0C3A18F6
Property(S): InstallNgenTicks = 1750000
Property(S): ProductToBeRegistered = 1
MSI (s) (38:20) [17:31:47:165]: Note: 1: 1708
MSI (s) (38:20) [17:31:47:165]: Product: Microsoft SQL Server 2008 Tools -- Installation failed.

You shouldn't be able to upgrade your report server. We don't support upgrade in the July CTP. Can you install a new instance?|||

No I am not trying to upgrade, but trying to install a clean install on windows 2003 box and I cannot.

Any thoughts, ideas.

Atul

|||What if you don't install the workstation tools? Just install the Report Server and see if you can configure it. Can you install the relational database by itself?|||

I am able to install the report server as well as the db from the looks of it.

But since management studio does not gets installed, I cannot verify or do anything with the DB.

I need to evaluate reporting services so it is very crucial to get this up and running.

Atul

|||You don't need Management Studio to use Reporting Services. But if you really need it on this machine, I would recommend you post the question over in the Katmai setup forum.

Cannot install Workstation components, fails on report server upgrade

I have hard time installing July CTP as it is failing on workstation component and fails on report server upgrade.

Any ideas for ther resolution.

Property(S): AdministratorsGroup = BUILTIN\Administrators
Property(S): PerformanceMontiorUsersGroup = BUILTIN\Performance Monitor Users
Property(S): PerformanceLogUsersGroup = BUILTIN\Performance Log Users
Property(S): UsersGroup = BUILTIN\Users
Property(S): SCMNetworkServiceAccount = NT AUTHORITY\NetworkService
Property(S): SCMLocalServiceAccount = NT AUTHORITY\LocalService
Property(S): IISCHECKED = 1
Property(S): SqlIISInstalled = 1
Property(S): SqlASPNETInstalled = 1
Property(S): SqlCOMPlusInstalled = 1
Property(S): RSPREREQUISITECHECKED = 1
Property(S): RSSqlPoolLimit = 100
Property(S): RSGUIDVALUE = {ec3b61d7-2813-485b-a55d-e0c931740946}
Property(S): RemoveFeatureList = Client_Components,Connectivity,SQL_Tools,SQL_WarehouseDevWorkbench,SDK,SQLXML,Tools_Legacy,TOOLS_BC_DEP,SQL_Documentation,SQL_Samples,SQL_BooksOnline,SQL_DatabaseSamples
Property(S): SqlOriginalMachineName = TAHITI
Property(S): Namechecksumcommon_32 = Developer Edition
Property(S): SqlSubDir = \MSSQL
Property(S): EditionTypechecksumcommon_32 = Developer Edition
Property(S): Namechecksumtools = Developer Edition
Property(S): EditionTypechecksumtools = Developer Edition
Property(S): ValidMOFInstanceName = 1
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer
Property(S): RSVirtualDirectoryManager = Reports
Property(S): SQLStatusBeforeInstall = 3
Property(S): SOURCEDIR = Z:\Tools\Setup\
Property(S): SourcedirProduct = {D6251ACA-3FD4-49D1-8FCF-182B980B19E3}
Property(S): HxDs_Tmp_3643236F_FC70_11D3_A536_0090278A1BB8 = C:\DOCUME~1\abahl\LOCALS~1\Temp\HxEA.tmp
Property(S): HxDs_Tmp_Hash_3643236F_FC70_11D3_A536_0090278A1BB8 = B40B0DC6C3C19C68E0101E0E2A647F0C3A18F6
Property(S): InstallNgenTicks = 1750000
Property(S): ProductToBeRegistered = 1
MSI (s) (38:20) [17:31:47:165]: Note: 1: 1708
MSI (s) (38:20) [17:31:47:165]: Product: Microsoft SQL Server 2008 Tools -- Installation failed.

You shouldn't be able to upgrade your report server. We don't support upgrade in the July CTP. Can you install a new instance?|||

No I am not trying to upgrade, but trying to install a clean install on windows 2003 box and I cannot.

Any thoughts, ideas.

Atul

|||What if you don't install the workstation tools? Just install the Report Server and see if you can configure it. Can you install the relational database by itself?|||

I am able to install the report server as well as the db from the looks of it.

But since management studio does not gets installed, I cannot verify or do anything with the DB.

I need to evaluate reporting services so it is very crucial to get this up and running.

Atul

|||You don't need Management Studio to use Reporting Services. But if you really need it on this machine, I would recommend you post the question over in the Katmai setup forum.

Cannot install Workstation components, fails on report server upgrade

I have hard time installing July CTP as it is failing on workstation component and fails on report server upgrade.

Any ideas for ther resolution.

Property(S): AdministratorsGroup = BUILTIN\Administrators
Property(S): PerformanceMontiorUsersGroup = BUILTIN\Performance Monitor Users
Property(S): PerformanceLogUsersGroup = BUILTIN\Performance Log Users
Property(S): UsersGroup = BUILTIN\Users
Property(S): SCMNetworkServiceAccount = NT AUTHORITY\NetworkService
Property(S): SCMLocalServiceAccount = NT AUTHORITY\LocalService
Property(S): IISCHECKED = 1
Property(S): SqlIISInstalled = 1
Property(S): SqlASPNETInstalled = 1
Property(S): SqlCOMPlusInstalled = 1
Property(S): RSPREREQUISITECHECKED = 1
Property(S): RSSqlPoolLimit = 100
Property(S): RSGUIDVALUE = {ec3b61d7-2813-485b-a55d-e0c931740946}
Property(S): RemoveFeatureList = Client_Components,Connectivity,SQL_Tools,SQL_WarehouseDevWorkbench,SDK,SQLXML,Tools_Legacy,TOOLS_BC_DEP,SQL_Documentation,SQL_Samples,SQL_BooksOnline,SQL_DatabaseSamples
Property(S): SqlOriginalMachineName = TAHITI
Property(S): Namechecksumcommon_32 = Developer Edition
Property(S): SqlSubDir = \MSSQL
Property(S): EditionTypechecksumcommon_32 = Developer Edition
Property(S): Namechecksumtools = Developer Edition
Property(S): EditionTypechecksumtools = Developer Edition
Property(S): ValidMOFInstanceName = 1
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer
Property(S): RSVirtualDirectoryManager = Reports
Property(S): SQLStatusBeforeInstall = 3
Property(S): SOURCEDIR = Z:\Tools\Setup\
Property(S): SourcedirProduct = {D6251ACA-3FD4-49D1-8FCF-182B980B19E3}
Property(S): HxDs_Tmp_3643236F_FC70_11D3_A536_0090278A1BB8 = C:\DOCUME~1\abahl\LOCALS~1\Temp\HxEA.tmp
Property(S): HxDs_Tmp_Hash_3643236F_FC70_11D3_A536_0090278A1BB8 = B40B0DC6C3C19C68E0101E0E2A647F0C3A18F6
Property(S): InstallNgenTicks = 1750000
Property(S): ProductToBeRegistered = 1
MSI (s) (38:20) [17:31:47:165]: Note: 1: 1708
MSI (s) (38:20) [17:31:47:165]: Product: Microsoft SQL Server 2008 Tools -- Installation failed.

You shouldn't be able to upgrade your report server. We don't support upgrade in the July CTP. Can you install a new instance?|||

No I am not trying to upgrade, but trying to install a clean install on windows 2003 box and I cannot.

Any thoughts, ideas.

Atul

|||What if you don't install the workstation tools? Just install the Report Server and see if you can configure it. Can you install the relational database by itself?|||

I am able to install the report server as well as the db from the looks of it.

But since management studio does not gets installed, I cannot verify or do anything with the DB.

I need to evaluate reporting services so it is very crucial to get this up and running.

Atul

|||You don't need Management Studio to use Reporting Services. But if you really need it on this machine, I would recommend you post the question over in the Katmai setup forum.

Cannot install Workstation components, fails on report server upgrade

I have hard time installing July CTP as it is failing on workstation component and fails on report server upgrade.

Any ideas for ther resolution.

Property(S): AdministratorsGroup = BUILTIN\Administrators
Property(S): PerformanceMontiorUsersGroup = BUILTIN\Performance Monitor Users
Property(S): PerformanceLogUsersGroup = BUILTIN\Performance Log Users
Property(S): UsersGroup = BUILTIN\Users
Property(S): SCMNetworkServiceAccount = NT AUTHORITY\NetworkService
Property(S): SCMLocalServiceAccount = NT AUTHORITY\LocalService
Property(S): IISCHECKED = 1
Property(S): SqlIISInstalled = 1
Property(S): SqlASPNETInstalled = 1
Property(S): SqlCOMPlusInstalled = 1
Property(S): RSPREREQUISITECHECKED = 1
Property(S): RSSqlPoolLimit = 100
Property(S): RSGUIDVALUE = {ec3b61d7-2813-485b-a55d-e0c931740946}
Property(S): RemoveFeatureList = Client_Components,Connectivity,SQL_Tools,SQL_WarehouseDevWorkbench,SDK,SQLXML,Tools_Legacy,TOOLS_BC_DEP,SQL_Documentation,SQL_Samples,SQL_BooksOnline,SQL_DatabaseSamples
Property(S): SqlOriginalMachineName = TAHITI
Property(S): Namechecksumcommon_32 = Developer Edition
Property(S): SqlSubDir = \MSSQL
Property(S): EditionTypechecksumcommon_32 = Developer Edition
Property(S): Namechecksumtools = Developer Edition
Property(S): EditionTypechecksumtools = Developer Edition
Property(S): ValidMOFInstanceName = 1
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer
Property(S): RSVirtualDirectoryManager = Reports
Property(S): SQLStatusBeforeInstall = 3
Property(S): SOURCEDIR = Z:\Tools\Setup\
Property(S): SourcedirProduct = {D6251ACA-3FD4-49D1-8FCF-182B980B19E3}
Property(S): HxDs_Tmp_3643236F_FC70_11D3_A536_0090278A1BB8 = C:\DOCUME~1\abahl\LOCALS~1\Temp\HxEA.tmp
Property(S): HxDs_Tmp_Hash_3643236F_FC70_11D3_A536_0090278A1BB8 = B40B0DC6C3C19C68E0101E0E2A647F0C3A18F6
Property(S): InstallNgenTicks = 1750000
Property(S): ProductToBeRegistered = 1
MSI (s) (38:20) [17:31:47:165]: Note: 1: 1708
MSI (s) (38:20) [17:31:47:165]: Product: Microsoft SQL Server 2008 Tools -- Installation failed.

You shouldn't be able to upgrade your report server. We don't support upgrade in the July CTP. Can you install a new instance?|||

No I am not trying to upgrade, but trying to install a clean install on windows 2003 box and I cannot.

Any thoughts, ideas.

Atul

|||

What if you don't install the workstation tools? Just install the Report Server and see if you can configure it. Can you install the relational database by itself?|||

I am able to install the report server as well as the db from the looks of it.

But since management studio does not gets installed, I cannot verify or do anything with the DB.

I need to evaluate reporting services so it is very crucial to get this up and running.

Atul

|||

You don't need Management Studio to use Reporting Services. But if you really need it on this machine, I would recommend you post the question over in the Katmai setup forum.

Wednesday, March 7, 2012

Cannot install SQLExpress after uninstalling June CTP

I try to install SQL Server Express after uninstalling its beta and get the following error in the log file. Can anyone help me? Thanks.

Microsoft SQL Server 2005 Setup beginning at Thu Dec 15 20:28:39 2005
Process ID : 110612
c:\e7b4645908c60721e3107fa330d0184a\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2005/11/15 20:28:38
Complete: LoadResourcesAction at: 2005/11/15 20:28:38, returned true
Running: ParseBootstrapOptionsAction at: 2005/11/15 20:28:38
Loaded DLL:c:\e7b4645908c60721e3107fa330d0184a\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2005/11/15 20:28:39, returned true
Running: ValidateWinNTAction at: 2005/11/15 20:28:39
Complete: ValidateWinNTAction at: 2005/11/15 20:28:39, returned true
Running: ValidateMinOSAction at: 2005/11/15 20:28:39
Complete: ValidateMinOSAction at: 2005/11/15 20:28:39, returned true
Running: PerformSCCAction at: 2005/11/15 20:28:39
Complete: PerformSCCAction at: 2005/11/15 20:28:39, returned true
Running: ActivateLoggingAction at: 2005/11/15 20:28:39
Complete: ActivateLoggingAction at: 2005/11/15 20:28:39, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__110612" returned false.
Running: PerformSCCAction2 at: 2005/11/15 20:28:39
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.06
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.

Class not registered.
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.
Message pump returning: 70032

Here's the problem:

Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.06

You can uninstall this from the command line using the following command:

msiexec /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}

jeff.

|||

I get the following error when I execute the command msiexec /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}

Thanks,

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 12/15/2005
Time: 11:59:17 PM
User: TWSERVER3\Administrator
Computer: TWSERVER3
Description:
Product: Microsoft SQL Server 2005 Express Edition CTP -- Error 29628. The setup has encountered an unexpected error in datastore. The action is RestoreSetupParams. The error is :Failed to read property "InstallIds" {"MachineConfiguration", "", "TWSERVER3"} from cache
Unable to write property into cache: IsClustered
Unable to write property into cache: "IsClustered"
XmlRW Error: Failure loading xmlrw.dll
CheckAllProcedures() returned: 2


|||Different server, same error message though on trying to uninstall.|||Yep, me too. Exactly the same problem as you guys. How do we get rid of the wretched thing?|||

I am not sure if the following will work in your case, but that work in my case finally:

1. Delete all directories related to the previous version of SQL Server.

2. Search and deleted all keys(or parent key) of 2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F(in my case).

After that, I successfully install SQL Server Express.

|||

That seems to have worked for me too.

Many thanks for your help.

Cannot install SQL Server 2005 CTP on WinXP Pro machine

Hi all,

I have tried to install SQL Server 2005 CTP version on my machine WinXP Pro
-1GB RAM but it gave me the following error.

/**********************************
The SQL Server System Configuration Checker cannot be executed due to WMI
configuration on the machine USPC180 Error:2147749896 (0x80041008).
*********************/

I have tried to do the following things but nothing helps.
A. To rebuild WMI
Start|Run|Command
1. type Mofcomp.exe %windir%\system32\wbem\cimwin32.mof and press enter.
2. type Regsvr32 wbemupgd.dll and press enter.
3. type regsvr32 wbemsvc.dll and press enter.

but step 1 was failed with access denied

B. To rebuild the WMI http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/reinstalling_wmi.asp

If you have any suggestions, please email to me at john_dang@.dril-quip.com

Regards,

John Dang

The following link has information on how to repair WMI

http://windowsxp.mvps.org/repairwmi.htm

Cannot install SQL Server 2005 CTP on WinXP Pro machine

Hi all,

I have tried to install SQL Server 2005 CTP version on my machine WinXP Pro
-1GB RAM but it gave me the following error.

/**********************************
The SQL Server System Configuration Checker cannot be executed due to WMI
configuration on the machine USPC180 Error:2147749896 (0x80041008).
*********************/

I have tried to do the following things but nothing helps.
A. To rebuild WMI
Start|Run|Command
1. type Mofcomp.exe %windir%\system32\wbem\cimwin32.mof and press enter.
2. type Regsvr32 wbemupgd.dll and press enter.
3. type regsvr32 wbemsvc.dll and press enter.

but step 1 was failed with access denied

B. To rebuild the WMI http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/reinstalling_wmi.asp

If you have any suggestions, please email to me at john_dang@.dril-quip.com

Regards,

John Dang

The following link has information on how to repair WMI

http://windowsxp.mvps.org/repairwmi.htm

Cannot install SQL Server 2005 CTP on WinXP Pro machine

Hi all,
I have tried to install SQL Server 2005 CTP version on my machine WinXP Pro
-1GB RAM but it gave me the following error.
/**********************************
The SQL Server System Configuration Checker cannot be executed due to WMI
configuration on the machine USPC180 Error:2147749896 (0x80041008).
*********************/
I have tried to do the following things but nothing helps.
A. To rebuild WMI
Start|Run|Command
1. type Mofcomp.exe %windir%\system32\wbem\cimwin32.mof and press enter.
2. type Regsvr32 wbemupgd.dll and press enter.
3. type regsvr32 wbemsvc.dll and press enter.
but step 1 was failed with access denied
B. To rebuild the WMI
http://msdn.microsoft.com/library/de...alling_wmi.asp
If you have any suggestions, please email to me at john_dang@.dril-quip.com
Regards,
John Dang
Since SQL 2005 is still in beta, you'll want to post this in the Community
Newsgroups:
http://communities.microsoft.com/new...r2005&slcid=us
--Brian
(Please reply to the newsgroups only.)
"jdang" <jdang@.discussions.microsoft.com> wrote in message
news:0F2AA951-7079-482D-9621-51834198E769@.microsoft.com...
> Hi all,
> I have tried to install SQL Server 2005 CTP version on my machine WinXP
> Pro
> -1GB RAM but it gave me the following error.
> /**********************************
> The SQL Server System Configuration Checker cannot be executed due to WMI
> configuration on the machine USPC180 Error:2147749896 (0x80041008).
> *********************/
> I have tried to do the following things but nothing helps.
>
> A. To rebuild WMI
> Start|Run|Command
> 1. type Mofcomp.exe %windir%\system32\wbem\cimwin32.mof and press enter.
> 2. type Regsvr32 wbemupgd.dll and press enter.
> 3. type regsvr32 wbemsvc.dll and press enter.
> but step 1 was failed with access denied
> B. To rebuild the WMI
> http://msdn.microsoft.com/library/de...alling_wmi.asp
> If you have any suggestions, please email to me at john_dang@.dril-quip.com
> Regards,
> John Dang
>

Cannot Install SQL Server 2005 along side SQL Server Express

Hi,

I have SQL Express edition installed. Now when i am trying to install SQL server 2005 June CTP i get an error saying "SQL Server setup cannot run. Another instance SQL Server Setup is already running. The running instance must complete before you can run the SQL Server setup again". I have restarted my machine twce but still i get this error message.

Any ideas?

Regards

Deepak

I'm having the same problem. I installed the Visual Web Developer 2005 Express Edition a couple of weeks ago, then attempted to install SQL Server 2005. I had to completely uninstall VWD to get the SQL Server 2005 install to work. After that, I tried to re-install VWD with SQL Server Express and it wouldn't work. I'm running all of this on XP Pro with .NET Framework 2.0 (not the BETA). One thing I haven't checked is if VWD can detect the SQL Server 2005 installation somehow, without having to install SQL Server Express altogether. I'll let you know what I find out.

-- TreeSapp

|||Try checking out Task Manager. See if there is a "setup.exe" running, but not doing anything. If you aren't installing, try killing it off, then running again. Not sure if this will help or not, but it's the only suggestion that I have.|||

No, I rebooted between installs to make sure that nothing else was running, checking Task Manager each time. I even made sure that the "PendingFileRenameOperations" registry entry was not set before and after each install. I also verified that each install completed successfully by simply executing the apps. I just can't seem to get both installed at the same time.

- TreeSapp

|||

Okay, go ahead, clean up the machine again (uninstall SQL and delete the %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\Log\Files directory), then install VWD Express. Then install SQL (I'm assuming you'll get your error).

Can you then look at %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\Log\Summary.txt. It should say what the problem is. If so, great, if not, can you copy/paste the error segment +/- 10 lines?

Thanks,

-Jeffrey

Cannot Install SQL Server 2005 [SOLVED]

I'm trying to install the final releases of Visual Studio 2005 Pro and SQL Server 2005 Developer's Edition. Unfortunately, I uninstalled VS Apr CTP "first" INSTEAD OF SQL Server 2005 Apr CTP.

I was then able to install the final release of VS 2005 without any problems but now I cannot install the SQL Server 2005 because it finds the beta components that must be uninstalled before proceeding. I tried using "Add/Remove Programs" but when I selected any of the SQL "CTP" programs that were there, I received a message that there was nothing to uninstall but I could have the "entry" removed from the "Add/Remove Programs" screen -- which I did.

I now have nothing related to the VS or SQL Server CTP's showing in "Add/Remove Programs". So it looks like I have to figure out how to unintall the SQL CTP components "manually". I have no idea how to proceed with this, however.

Any help in removing these CTP components would be greatly appreciated. Thank you.There is a tool under your "setup tools" folder on your beta media made for this purpose. I would try the one for SQL Server september CTP if you have that available.

|||Thanks for the suggestion but it did NOT work. When I ran the "build uninstall" from the Sept CTP, it gave me the same error messages when I tried to uninstall the four Apr CTP components it found:

"A component failed to uninistall. The file specified by the link could not be found."

Status: "(13) The data is invalid."

Any other suggestions?|||Too bad.

Well this is a little backwards, but how about reinstalling april (just the prereq and engine) then run the uninstall tool?

This might potentially do more harm then good, but I would try.|||This is a problem for me, too.
You cannot reinstall the April beta version, but you can't remove it either.
For one thing, the beta versions of SQL Server 2005 are impossible to remove manually, and the uninstall beta tool from Microsoft assumes that you do this first. I tried all kinds of different things to remove it, but nothing worked.
In the forums, people have even come up with programs to uninstall the betas, unfortunately, none of them uninstall SQL Server 2005 beta. If Microsoft can come up with all this great software, why can't they come up with a tool that can uninstall one of the old beta versions of SQL Server 2005?
Considering how many other people have had this same problem, could someone at Microsoft please look into this? SQL Server 2005 could be the best database product in the world, but if you can't install it ( without reinstalling your operating system first ), what's the point ?
|||Guys .... If you have problems with Sep CTP you MUST use Sep CTP Build Uninstall Tool ...

If you still have problems start uninstalling things .... Last install first ...

/h|||I believed I have a workaround on how to uninstall Sep CTP. After so many tries, the SQLBUW.exe on the Sep CTP was also not working. This program requires that all the SQL Server 2005 Sep CTP components are there before it would work.

As suggested by the released SQL Server 2005 readme file, I used the Control Panel Add/Remove program tool to remove a bunch of SQL server 2005 Sep CTP components in the order suggested by the readme file. Using Add/Remove, however, does not actually uninstall the SEP CTP and just removed the signature of these components from a list . Then after searching, I found out about SQLBUW.EXE (sql server uninstall wizard), but since I did some manual remove, the sqlbuw.exe was not working for me either.

To get SQLBUW.EXE to work correctly, I reinstalled all these SQLServer 2005 Sep CTP components and to make sure all the SQL Server 2005 services are running. Then run sqlbuw.exe again, and this time the uninstall wizard worked. Several hours of my time is wasted on a problem that MSFT could have easily solved. This makes me worry about the overall quality of this release. It seemed that a simple problem like this was not addressed makes me wonder.
Rgds, Thuyen|||I had the same problem, I ran across a blog that pointed to this utility http://support.microsoft.com/default.aspx?scid=kb;en-us;290301. It appears the VS 2005 uninstall removes SQL 2005 CTP Tools from the add/remove programs but does not really unistall. You can verify which product is causing the problems by going to %programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\%CORE%. You should see the GUID and the program name.

If you run the "WIndows Installer CleanUp Utility" and remove the programs it will work, now I wonder which to install first VS 2005 Pro or SQL Server 2005 Dev?

Michael|||Thanks, this post helped me clean out the beta registry entries.

I simply searched the registry for all keys containing the offending Guid and wiped them, after which I was able to install the final versions (I went with the SQL Server Express edition this time - the full product boggles down the desktop more than I need it)!

Yours,
Morten|||I've been on vacation for the past week or so and I just returned to work yesterday to, once again, face my SQL Server 2005 installation problems.

The previous suggestions I had tried did not work so I started over using your suggestion.

First, I ran the "Windows Installer Cleanup Utility" to remove any existing instances of the SQL 2005 beta programs. This actually worked. I was then able to install the released version of SQL 2005 -- except for Analysis Services.

Next, I tried to install the released version of Visual Studio 2005 Pro. Unfortunately, the installer found some instances of the VS 2005 beta programs that had to be removed before continuing. I "should" have checked for this before doing the SQL 2005 install, especially because using the "Installer Cleanup Utility" wanted to remove some SQL 2005 componets that would no doubt "break" my SQL 2005 install. Therefore, I decided to "uninstall" SQL 2005 using "Add/Remove Programs" and then use the "Installer Cleanup Utility" to remove any remaining pieces of VS 2005 beta.

I then reinstalled SQL 2005 without incident (except for "Analysis Service" which would not install because of a "supposedly" existing instance of the same name).

After installing SQL 2005, I was then able to install VS 2005 without receiving any error messages. I did receive one error message when starting VS for the first time (something about an assembly that wouldn't load -- which I bypassed). It seems to be working okay.

SLQ 2005 is also working except for Analysis Services. However, although I can connect to my local version of SQL 2005 and to the SQL 2000 databases on our SQL Server, I "cannot" connect to the SQL 2005 databases on our SQL Server that were created using the SQL 2005 April CTP. I can connect to those databases directly from the Server (which still has the April CTP loaded) but NOT from my workstation using the "released" version of SQL 2005. The error I receive is:
--
An exception occurred by executing a Transact-SQL statement or batch (Microsoft.SqlServer.ConnectionInfo)
Additional Information: Insert Error: Column name or number or number of supplied values does not match table definition. (Microsoft SQL Server, Error: 213)

Shouldn't the "released" version of SQL 2005 be able to connect to a database created by the April CTP?

Thanks very much for everyone's help in solving my install problems.|||Morten,

Thanks for this post it was a simple solution that I didn't think of before and it was able to solve my problem as well.

-Brandon

Cannot Install SQL Server 2005 [SOLVED]

I'm trying to install the final releases of Visual Studio 2005 Pro and SQL Server 2005 Developer's Edition. Unfortunately, I uninstalled VS Apr CTP "first" INSTEAD OF SQL Server 2005 Apr CTP.

I was then able to install the final release of VS 2005 without any problems but now I cannot install the SQL Server 2005 because it finds the beta components that must be uninstalled before proceeding. I tried using "Add/Remove Programs" but when I selected any of the SQL "CTP" programs that were there, I received a message that there was nothing to uninstall but I could have the "entry" removed from the "Add/Remove Programs" screen -- which I did.

I now have nothing related to the VS or SQL Server CTP's showing in "Add/Remove Programs". So it looks like I have to figure out how to unintall the SQL CTP components "manually". I have no idea how to proceed with this, however.

Any help in removing these CTP components would be greatly appreciated. Thank you.There is a tool under your "setup tools" folder on your beta media made for this purpose. I would try the one for SQL Server september CTP if you have that available.

|||Thanks for the suggestion but it did NOT work. When I ran the "build uninstall" from the Sept CTP, it gave me the same error messages when I tried to uninstall the four Apr CTP components it found:

"A component failed to uninistall. The file specified by the link could not be found."

Status: "(13) The data is invalid."

Any other suggestions?|||Too bad.

Well this is a little backwards, but how about reinstalling april (just the prereq and engine) then run the uninstall tool?

This might potentially do more harm then good, but I would try.|||This is a problem for me, too.
You cannot reinstall the April beta version, but you can't remove it either.
For one thing, the beta versions of SQL Server 2005 are impossible to remove manually, and the uninstall beta tool from Microsoft assumes that you do this first. I tried all kinds of different things to remove it, but nothing worked.
In the forums, people have even come up with programs to uninstall the betas, unfortunately, none of them uninstall SQL Server 2005 beta. If Microsoft can come up with all this great software, why can't they come up with a tool that can uninstall one of the old beta versions of SQL Server 2005?
Considering how many other people have had this same problem, could someone at Microsoft please look into this? SQL Server 2005 could be the best database product in the world, but if you can't install it ( without reinstalling your operating system first ), what's the point ?
|||Guys .... If you have problems with Sep CTP you MUST use Sep CTP Build Uninstall Tool ...

If you still have problems start uninstalling things .... Last install first ...

/h|||I believed I have a workaround on how to uninstall Sep CTP. After so many tries, the SQLBUW.exe on the Sep CTP was also not working. This program requires that all the SQL Server 2005 Sep CTP components are there before it would work.

As suggested by the released SQL Server 2005 readme file, I used the Control Panel Add/Remove program tool to remove a bunch of SQL server 2005 Sep CTP components in the order suggested by the readme file. Using Add/Remove, however, does not actually uninstall the SEP CTP and just removed the signature of these components from a list . Then after searching, I found out about SQLBUW.EXE (sql server uninstall wizard), but since I did some manual remove, the sqlbuw.exe was not working for me either.

To get SQLBUW.EXE to work correctly, I reinstalled all these SQLServer 2005 Sep CTP components and to make sure all the SQL Server 2005 services are running. Then run sqlbuw.exe again, and this time the uninstall wizard worked. Several hours of my time is wasted on a problem that MSFT could have easily solved. This makes me worry about the overall quality of this release. It seemed that a simple problem like this was not addressed makes me wonder.
Rgds, Thuyen|||I had the same problem, I ran across a blog that pointed to this utility http://support.microsoft.com/default.aspx?scid=kb;en-us;290301. It appears the VS 2005 uninstall removes SQL 2005 CTP Tools from the add/remove programs but does not really unistall. You can verify which product is causing the problems by going to %programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\%CORE%. You should see the GUID and the program name.

If you run the "WIndows Installer CleanUp Utility" and remove the programs it will work, now I wonder which to install first VS 2005 Pro or SQL Server 2005 Dev?

Michael|||Thanks, this post helped me clean out the beta registry entries.

I simply searched the registry for all keys containing the offending Guid and wiped them, after which I was able to install the final versions (I went with the SQL Server Express edition this time - the full product boggles down the desktop more than I need it)!

Yours,
Morten|||I've been on vacation for the past week or so and I just returned to work yesterday to, once again, face my SQL Server 2005 installation problems.

The previous suggestions I had tried did not work so I started over using your suggestion.

First, I ran the "Windows Installer Cleanup Utility" to remove any existing instances of the SQL 2005 beta programs. This actually worked. I was then able to install the released version of SQL 2005 -- except for Analysis Services.

Next, I tried to install the released version of Visual Studio 2005 Pro. Unfortunately, the installer found some instances of the VS 2005 beta programs that had to be removed before continuing. I "should" have checked for this before doing the SQL 2005 install, especially because using the "Installer Cleanup Utility" wanted to remove some SQL 2005 componets that would no doubt "break" my SQL 2005 install. Therefore, I decided to "uninstall" SQL 2005 using "Add/Remove Programs" and then use the "Installer Cleanup Utility" to remove any remaining pieces of VS 2005 beta.

I then reinstalled SQL 2005 without incident (except for "Analysis Service" which would not install because of a "supposedly" existing instance of the same name).

After installing SQL 2005, I was then able to install VS 2005 without receiving any error messages. I did receive one error message when starting VS for the first time (something about an assembly that wouldn't load -- which I bypassed). It seems to be working okay.

SLQ 2005 is also working except for Analysis Services. However, although I can connect to my local version of SQL 2005 and to the SQL 2000 databases on our SQL Server, I "cannot" connect to the SQL 2005 databases on our SQL Server that were created using the SQL 2005 April CTP. I can connect to those databases directly from the Server (which still has the April CTP loaded) but NOT from my workstation using the "released" version of SQL 2005. The error I receive is:
--
An exception occurred by executing a Transact-SQL statement or batch (Microsoft.SqlServer.ConnectionInfo)
Additional Information: Insert Error: Column name or number or number of supplied values does not match table definition. (Microsoft SQL Server, Error: 213)

Shouldn't the "released" version of SQL 2005 be able to connect to a database created by the April CTP?

Thanks very much for everyone's help in solving my install problems.|||Morten,

Thanks for this post it was a simple solution that I didn't think of before and it was able to solve my problem as well.

-Brandon

Cannot Install SQL Server 2005

I'm trying to install the final releases of Visual Studio 2005 Pro and SQL Server 2005 Developer's Edition. Unfortunately, I uninstalled VS Apr CTP "first" INSTEAD OF SQL Server 2005 Apr CTP.

I was then able to install the final release of VS 2005 without any problems but now I cannot install the SQL Server 2005 because it finds the beta components that must be uninstalled before proceeding. I tried using "Add/Remove Programs" but when I selected any of the SQL "CTP" programs that were there, I received a message that there was nothing to uninstall but I could have the "entry" removed from the "Add/Remove Programs" screen -- which I did.

I now have nothing related to the VS or SQL Server CTP's showing in "Add/Remove Programs". So it looks like I have to figure out how to unintall the SQL CTP components "manually". I have no idea how to proceed with this, however.

Any help in removing these CTP components would be greatly appreciated. Thank you.There is a tool under your "setup tools" folder on your beta media made for this purpose. I would try the one for SQL Server september CTP if you have that available.

|||Thanks for the suggestion but it did NOT work. When I ran the "build uninstall" from the Sept CTP, it gave me the same error messages when I tried to uninstall the four Apr CTP components it found:

"A component failed to uninistall. The file specified by the link could not be found."

Status: "(13) The data is invalid."

Any other suggestions?|||Too bad.

Well this is a little backwards, but how about reinstalling april (just the prereq and engine) then run the uninstall tool?

This might potentially do more harm then good, but I would try.|||This is a problem for me, too.
You cannot reinstall the April beta version, but you can't remove it either.
For one thing, the beta versions of SQL Server 2005 are impossible to remove manually, and the uninstall beta tool from Microsoft assumes that you do this first. I tried all kinds of different things to remove it, but nothing worked.
In the forums, people have even come up with programs to uninstall the betas, unfortunately, none of them uninstall SQL Server 2005 beta. If Microsoft can come up with all this great software, why can't they come up with a tool that can uninstall one of the old beta versions of SQL Server 2005?
Considering how many other people have had this same problem, could someone at Microsoft please look into this? SQL Server 2005 could be the best database product in the world, but if you can't install it ( without reinstalling your operating system first ), what's the point ?
|||Guys .... If you have problems with Sep CTP you MUST use Sep CTP Build Uninstall Tool ...

If you still have problems start uninstalling things .... Last install first ...

/h|||I believed I have a workaround on how to uninstall Sep CTP. After so many tries, the SQLBUW.exe on the Sep CTP was also not working. This program requires that all the SQL Server 2005 Sep CTP components are there before it would work.

As suggested by the released SQL Server 2005 readme file, I used the Control Panel Add/Remove program tool to remove a bunch of SQL server 2005 Sep CTP components in the order suggested by the readme file. Using Add/Remove, however, does not actually uninstall the SEP CTP and just removed the signature of these components from a list . Then after searching, I found out about SQLBUW.EXE (sql server uninstall wizard), but since I did some manual remove, the sqlbuw.exe was not working for me either.

To get SQLBUW.EXE to work correctly, I reinstalled all these SQLServer 2005 Sep CTP components and to make sure all the SQL Server 2005 services are running. Then run sqlbuw.exe again, and this time the uninstall wizard worked. Several hours of my time is wasted on a problem that MSFT could have easily solved. This makes me worry about the overall quality of this release. It seemed that a simple problem like this was not addressed makes me wonder.
Rgds, Thuyen|||I had the same problem, I ran across a blog that pointed to this utility http://support.microsoft.com/default.aspx?scid=kb;en-us;290301. It appears the VS 2005 uninstall removes SQL 2005 CTP Tools from the add/remove programs but does not really unistall. You can verify which product is causing the problems by going to %programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\%CORE%. You should see the GUID and the program name.

If you run the "WIndows Installer CleanUp Utility" and remove the programs it will work, now I wonder which to install first VS 2005 Pro or SQL Server 2005 Dev?

Michael|||Thanks, this post helped me clean out the beta registry entries.

I simply searched the registry for all keys containing the offending Guid and wiped them, after which I was able to install the final versions (I went with the SQL Server Express edition this time - the full product boggles down the desktop more than I need it)!

Yours,
Morten|||I've been on vacation for the past week or so and I just returned to work yesterday to, once again, face my SQL Server 2005 installation problems.

The previous suggestions I had tried did not work so I started over using your suggestion.

First, I ran the "Windows Installer Cleanup Utility" to remove any existing instances of the SQL 2005 beta programs. This actually worked. I was then able to install the released version of SQL 2005 -- except for Analysis Services.

Next, I tried to install the released version of Visual Studio 2005 Pro. Unfortunately, the installer found some instances of the VS 2005 beta programs that had to be removed before continuing. I "should" have checked for this before doing the SQL 2005 install, especially because using the "Installer Cleanup Utility" wanted to remove some SQL 2005 componets that would no doubt "break" my SQL 2005 install. Therefore, I decided to "uninstall" SQL 2005 using "Add/Remove Programs" and then use the "Installer Cleanup Utility" to remove any remaining pieces of VS 2005 beta.

I then reinstalled SQL 2005 without incident (except for "Analysis Service" which would not install because of a "supposedly" existing instance of the same name).

After installing SQL 2005, I was then able to install VS 2005 without receiving any error messages. I did receive one error message when starting VS for the first time (something about an assembly that wouldn't load -- which I bypassed). It seems to be working okay.

SLQ 2005 is also working except for Analysis Services. However, although I can connect to my local version of SQL 2005 and to the SQL 2000 databases on our SQL Server, I "cannot" connect to the SQL 2005 databases on our SQL Server that were created using the SQL 2005 April CTP. I can connect to those databases directly from the Server (which still has the April CTP loaded) but NOT from my workstation using the "released" version of SQL 2005. The error I receive is:
--
An exception occurred by executing a Transact-SQL statement or batch (Microsoft.SqlServer.ConnectionInfo)
Additional Information: Insert Error: Column name or number or number of supplied values does not match table definition. (Microsoft SQL Server, Error: 213)

Shouldn't the "released" version of SQL 2005 be able to connect to a database created by the April CTP?

Thanks very much for everyone's help in solving my install problems.|||Morten,

Thanks for this post it was a simple solution that I didn't think of before and it was able to solve my problem as well.

-Brandon

Cannot Install SQL Server 2005

I'm trying to install the final releases of Visual Studio 2005 Pro and SQL Server 2005 Developer's Edition. Unfortunately, I uninstalled VS Apr CTP "first" INSTEAD OF SQL Server 2005 Apr CTP.

I was then able to install the final release of VS 2005 without any problems but now I cannot install the SQL Server 2005 because it finds the beta components that must be uninstalled before proceeding. I tried using "Add/Remove Programs" but when I selected any of the SQL "CTP" programs that were there, I received a message that there was nothing to uninstall but I could have the "entry" removed from the "Add/Remove Programs" screen -- which I did.

I now have nothing related to the VS or SQL Server CTP's showing in "Add/Remove Programs". So it looks like I have to figure out how to unintall the SQL CTP components "manually". I have no idea how to proceed with this, however.

Any help in removing these CTP components would be greatly appreciated. Thank you.There is a tool under your "setup tools" folder on your beta media made for this purpose. I would try the one for SQL Server september CTP if you have that available.|||Thanks for the suggestion but it did NOT work. When I ran the "build uninstall" from the Sept CTP, it gave me the same error messages when I tried to uninstall the four Apr CTP components it found:

"A component failed to uninistall. The file specified by the link could not be found."

Status: "(13) The data is invalid."

Any other suggestions?|||Too bad.

Well this is a little backwards, but how about reinstalling april (just the prereq and engine) then run the uninstall tool?

This might potentially do more harm then good, but I would try.|||This is a problem for me, too.
You cannot reinstall the April beta version, but you can't remove it either.
For one thing, the beta versions of SQL Server 2005 are impossible to remove manually, and the uninstall beta tool from Microsoft assumes that you do this first. I tried all kinds of different things to remove it, but nothing worked.
In the forums, people have even come up with programs to uninstall the betas, unfortunately, none of them uninstall SQL Server 2005 beta. If Microsoft can come up with all this great software, why can't they come up with a tool that can uninstall one of the old beta versions of SQL Server 2005?
Considering how many other people have had this same problem, could someone at Microsoft please look into this? SQL Server 2005 could be the best database product in the world, but if you can't install it ( without reinstalling your operating system first ), what's the point ?

|||Guys .... If you have problems with Sep CTP you MUST use Sep CTP Build Uninstall Tool ...

If you still have problems start uninstalling things .... Last install first ...

/h|||I believed I have a workaround on how to uninstall Sep CTP. After so many tries, the SQLBUW.exe on the Sep CTP was also not working. This program requires that all the SQL Server 2005 Sep CTP components are there before it would work.

As suggested by the released SQL Server 2005 readme file, I used the Control Panel Add/Remove program tool to remove a bunch of SQL server 2005 Sep CTP components in the order suggested by the readme file. Using Add/Remove, however, does not actually uninstall the SEP CTP and just removed the signature of these components from a list . Then after searching, I found out about SQLBUW.EXE (sql server uninstall wizard), but since I did some manual remove, the sqlbuw.exe was not working for me either.

To get SQLBUW.EXE to work correctly, I reinstalled all these SQLServer 2005 Sep CTP components and to make sure all the SQL Server 2005 services are running. Then run sqlbuw.exe again, and this time the uninstall wizard worked. Several hours of my time is wasted on a problem that MSFT could have easily solved. This makes me worry about the overall quality of this release. It seemed that a simple problem like this was not addressed makes me wonder.
Rgds, Thuyen|||I had the same problem, I ran across a blog that pointed to this utility http://support.microsoft.com/default.aspx?scid=kb;en-us;290301. It appears the VS 2005 uninstall removes SQL 2005 CTP Tools from the add/remove programs but does not really unistall. You can verify which product is causing the problems by going to %programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\%CORE%. You should see the GUID and the program name.

If you run the "WIndows Installer CleanUp Utility" and remove the programs it will work, now I wonder which to install first VS 2005 Pro or SQL Server 2005 Dev?

Michael
|||Thanks, this post helped me clean out the beta registry entries.

I simply searched the registry for all keys containing the offending Guid and wiped them, after which I was able to install the final versions (I went with the SQL Server Express edition this time - the full product boggles down the desktop more than I need it)!

Yours,
Morten

|||I've been on vacation for the past week or so and I just returned to work yesterday to, once again, face my SQL Server 2005 installation problems.

The previous suggestions I had tried did not work so I started over using your suggestion.

First, I ran the "Windows Installer Cleanup Utility" to remove any existing instances of the SQL 2005 beta programs. This actually worked. I was then able to install the released version of SQL 2005 -- except for Analysis Services.

Next, I tried to install the released version of Visual Studio 2005 Pro. Unfortunately, the installer found some instances of the VS 2005 beta programs that had to be removed before continuing. I "should" have checked for this before doing the SQL 2005 install, especially because using the "Installer Cleanup Utility" wanted to remove some SQL 2005 componets that would no doubt "break" my SQL 2005 install. Therefore, I decided to "uninstall" SQL 2005 using "Add/Remove Programs" and then use the "Installer Cleanup Utility" to remove any remaining pieces of VS 2005 beta.

I then reinstalled SQL 2005 without incident (except for "Analysis Service" which would not install because of a "supposedly" existing instance of the same name).

After installing SQL 2005, I was then able to install VS 2005 without receiving any error messages. I did receive one error message when starting VS for the first time (something about an assembly that wouldn't load -- which I bypassed). It seems to be working okay.

SLQ 2005 is also working except for Analysis Services. However, although I can connect to my local version of SQL 2005 and to the SQL 2000 databases on our SQL Server, I "cannot" connect to the SQL 2005 databases on our SQL Server that were created using the SQL 2005 April CTP. I can connect to those databases directly from the Server (which still has the April CTP loaded) but NOT from my workstation using the "released" version of SQL 2005. The error I receive is:
--
An exception occurred by executing a Transact-SQL statement or batch (Microsoft.SqlServer.ConnectionInfo)
Additional Information: Insert Error: Column name or number or number of supplied values does not match table definition. (Microsoft SQL Server, Error: 213)

Shouldn't the "released" version of SQL 2005 be able to connect to a database created by the April CTP?

Thanks very much for everyone's help in solving my install problems.|||Morten,

Thanks for this post it was a simple solution that I didn't think of before and it was able to solve my problem as well.

-Brandon

Saturday, February 25, 2012

Cannot install June CTP on Windows 2003 DC !!!

I am trying to install Sql Server 2005 June CTP on a Windows Server
2003 SP1 primary domain controller with IIS/ASP installed.

I get this error (when Sql Server Database Services is being installed:
"SQL Server Setup was unable add user NT AUTHORITY\NETWORK SERVICE to
local group SQLServer2005MSSQLServerADHelp­erUser".
And I am not alone!
See http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=18788

Any workaround or update to be able to install it on a domain controller, Microsoft?

Thanks!

Anybody?

Our environment requires installation of SQL 2005 on a server with Active Directory... so this is really a big issue.

Please, can somebody from MS look into this?|||We are a few days later now, and still, nowhere on the Internet I can find a solution.

Can somebody from Microsoft please respond?|||

Currently SQL Server 2005 will not install on a Domain Controller or on Windows Small Business Server. There is no known work around at this time other than installing on a machine that is not configured as a domain controller. This is a known issue and we're working on resolving it.

Dan

|||Yikes, this is a huge issue. I have this issue too on a single Win2K3 Server Standard with SP1, AD/DC. Active Directory and DC are required before setting up TFS.Tongue Tied
|||I've been in contact with the TFS team on this issue. As long as you use the April CTP that shipped with TFS Beta 2 you're okay. You just can't use the June CTP.

Thursday, February 16, 2012

Cannot get RDA.Pull to work

[SQL Everywhere CTP],[VS2005]

RDA.Pull method is not doing anything for me from a VSTO 2005 Outlook addin project. I have IIS & SQL Server 2005 running on my develpoment pc. I am using Integrated Windows Auth for vdir. It just stops execution at the line of code that calls RDA.Pull & doesnt return any tables nor throws an error. I have no idea where I am going wrong. I have tried using table names that dont exist in the .sdf too.

SqlCeRemoteDataAccess rda = new SqlCeRemoteDataAccess();

rda.InternetUrl = @."http://localhost/WsRDA/sqlcesa30.dll";

rda.LocalConnectionString = @."Data Source=D:\_fullPahtHere\DBEverywhere.sdf;Password=sdfPwdHere";

rda.InternetLogin = "myLocalUserName";
rda.InternetPassword = "myLocalPassword";

rda.Pull("Class2", "select * from dbo.Class", @."Data Source=MyDesktop\SQL2K5;Initial Catalog=ServerDB;Integrated Security=SSPI");

Without an error msg, I dont know what the problem is. Any ideas?Ok, figured out. My connection string was missing Provider=sqloledb attribute.