Showing posts with label beta. Show all posts
Showing posts with label beta. 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 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.

Thursday, March 8, 2012

Cannot integrate SQL Server 2005 with Visual Studio 2005

Hi,

I have a question that I hope someone can help me with.

I' have installed VS2005 Beta 2 on my XP machine. I've also installed SQL Server 2005 and uninstalled SQL Express (though the instance still seems to appear even though it no longer works!)

So basically I'm trying to get VS2005 to work with SQL Server 2005. However when I go into solution explorer, I :-

Right click on the project name
Select ADD
NEW ITEM
SQL Database
<name.mdf>
now from what I've seen in online demo's, it should then fire up some connection wizard. Mine just sits there for about 30 seconds and then tells me it's timed out. I then find the .mdf file added to my project is totally useless and hangs for another 30 seconds everytime I select it until I delete the thing.

In server explorer, I type in the name of my server (my PC's name) and the test connection appears to work fine.

Can anyone tell me why this is happening and how I can fix it?

Many thanks in advance

Jocky.

It sounds like you've got some registry badness going on. De-install all SQL Server, following this link:

http://msdn2.microsoft.com/en-us/library/aa337087.aspx

And then reinstall. That should clear it up for you.

Buck Woody

Cannot integrate SQL Server 2005 with Visual Studio 2005

Hi,

I have a question that I hope someone can help me with.

I' have installed VS2005 Beta 2 on my XP machine. I've also installed SQL Server 2005 and uninstalled SQL Express (though the instance still seems to appear even though it no longer works!)

So basically I'm trying to get VS2005 to work with SQL Server 2005. However when I go into solution explorer, I :-

Right click on the project name
Select ADD
NEW ITEM
SQL Database
<name.mdf>
now from what I've seen in online demo's, it should then fire up some connection wizard. Mine just sits there for about 30 seconds and then tells me it's timed out. I then find the .mdf file added to my project is totally useless and hangs for another 30 seconds everytime I select it until I delete the thing.

In server explorer, I type in the name of my server (my PC's name) and the test connection appears to work fine.

Can anyone tell me why this is happening and how I can fix it?

Many thanks in advance

Jocky.

It sounds like you've got some registry badness going on. De-install all SQL Server, following this link:

http://msdn2.microsoft.com/en-us/library/aa337087.aspx

And then reinstall. That should clear it up for you.

Buck Woody

Cannot Install Toolkit.

Trying to install SQL Everywhere Beta Toolkit. And am getting following error message:

"The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program.

The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade path."

On difference is I'm installing on top of the "recently released" verision of VS2005 SP1, not the beta.

But, other than that, all the prereqs are installed.

Any insight on suggestions would be greatly appreciated.

Thanks

Rob Vettor

It only works on the beta. I have been having trouble with this as well. According to what I have read and been told the new Service pack and the SQL Ce package you download seperate should be enough to allow you to connect to the .sdf files. I have not found this to be true but that is what it says online.

good luck
Ben

Cannot Install SQLServer 2005 Express

When I try to run the install it detects some previous versions components. The remove all previous beta components fails and I have removed everything from the Add/Remove Programs.
Any advice would be helpful
Irina

Hi Irina,

Take a look at your setup logs to find out exactly what pre-release component is being detected. Once you know which component it is, it should be easier to remove.

Regards,

Mike Wachal
SQL Express team

-
Please mark your thread as Answered when you get your solution.

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 Express, keep getting errors

I am trying to install SQL Server 2005 Express, but it fails.
SQL Server Setup has detected incompatible components from Beta version of Visual Studio, .NETFramework or SQL Server 2005. Use Add or Remove to

I had earlier installed Beta 2 Version of Dev Studio 2005 and SQL Server 2005 Beta 2. I also had DevStudio 2003 and SQL Server installed. I have gone through and un-installed everything, but I keep getting this error.

I have also tried
msiexec /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
msiexec /x {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Both of these un-install start, but fail with error messages.

Would appreciate if anyone can help.

Saleem Yusuf
Saleem_Yusuf@.hotmail.com

Try the following.
1. Uninstall all visible Beta components in Add/Remove Programes.

2. Detect the Beta components infromation in the the log file located in %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetupNo_%machinename%_Core(Local).log.

3. Search the whole registry keys, remove those registy keys related to those Beta components. This is time-consuming.

4. Kill all Beta SQL Services (including SQL, OLAP, RS, SQLBROWSER, SQLAGENT, etc.) if they are existing with command sc.

5. Reboot the machine.

6. Start Setup again.

|||I looked at the log and tried to uninstall old version, but it does not exists.
However, in the logs, I saw a version number and seach registry. They are many entries of SQL Server Express. I deleted some of them, but no luck yet. I am quite sure if I get rid of all the old registry setting, it should fix the problem.
Thanks for your help,

Saleem|||Problem fixed. I can now install SQL Server Express. Thanks for you help.
This is what I did.
Looked in file \Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG.
It had referecne to other log files. I opened one of the files, HostName_core.log
(notepad C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_<My_HostName>_Core.log)

This file had multiple reference to older versions of SQL Server Express. Example
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"

First I tried to uninstall, (MsiExec.exe /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}). Un-install failed.

Then I searched for 9.00.1399.06. I found multiple entried. I deleted them all.
After that I was able install SQL Server Express.|||

I tried 3 other fixes on other forums (asp.net,etc.) and this is the only one that worked.

My log file had a similar message. However, I deleted the entries related to the older version (in the case above, that would be 9.00.1116); not the later or "expected at least" version (9.00.1399.06).

With this fix, I did not have to remove .net 1.0 beta or .net 1.1

|||Thanks for posting - that worked for me too - I had just spent my own money buying VS2005 Pro and couldn't install SQL Express because previously installed beta stuff was fouling up the install.

Perhaps the SQL guys at MS could revise the install script in future releases to 'clean up' before installing... Just a suggestion.

Anyway, just re-installed trhe whole .Net DVD and it's running now, so thanks!

Mark

cannot install SQL Server Express, keep getting errors

I am trying to install SQL Server 2005 Express, but it fails.
SQL Server Setup has detected incompatible components from Beta version of Visual Studio, .NETFramework or SQL Server 2005. Use Add or Remove to

I had earlier installed Beta 2 Version of Dev Studio 2005 and SQL Server 2005 Beta 2. I also had DevStudio 2003 and SQL Server installed. I have gone through and un-installed everything, but I keep getting this error.

I have also tried
msiexec /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
msiexec /x {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Both of these un-install start, but fail with error messages.

Would appreciate if anyone can help.

Saleem Yusuf
Saleem_Yusuf@.hotmail.com

Try the following.
1. Uninstall all visible Beta components in Add/Remove Programes.

2. Detect the Beta components infromation in the the log file located in %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetupNo_%machinename%_Core(Local).log.

3. Search the whole registry keys, remove those registy keys related to those Beta components. This is time-consuming.

4. Kill all Beta SQL Services (including SQL, OLAP, RS, SQLBROWSER, SQLAGENT, etc.) if they are existing with command sc.

5. Reboot the machine.

6. Start Setup again.

|||I looked at the log and tried to uninstall old version, but it does not exists.
However, in the logs, I saw a version number and seach registry. They are many entries of SQL Server Express. I deleted some of them, but no luck yet. I am quite sure if I get rid of all the old registry setting, it should fix the problem.
Thanks for your help,

Saleem|||Problem fixed. I can now install SQL Server Express. Thanks for you help.
This is what I did.
Looked in file \Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG.
It had referecne to other log files. I opened one of the files, HostName_core.log
(notepad C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_<My_HostName>_Core.log)

This file had multiple reference to older versions of SQL Server Express. Example
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"

First I tried to uninstall, (MsiExec.exe /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}). Un-install failed.

Then I searched for 9.00.1399.06. I found multiple entried. I deleted them all.
After that I was able install SQL Server Express.|||

I tried 3 other fixes on other forums (asp.net,etc.) and this is the only one that worked.

My log file had a similar message. However, I deleted the entries related to the older version (in the case above, that would be 9.00.1116); not the later or "expected at least" version (9.00.1399.06).

With this fix, I did not have to remove .net 1.0 beta or .net 1.1

|||Thanks for posting - that worked for me too - I had just spent my own money buying VS2005 Pro and couldn't install SQL Express because previously installed beta stuff was fouling up the install.

Perhaps the SQL guys at MS could revise the install script in future releases to 'clean up' before installing... Just a suggestion.

Anyway, just re-installed trhe whole .Net DVD and it's running now, so thanks!

Mark

cannot install SQL Server Express, keep getting errors

I am trying to install SQL Server 2005 Express, but it fails.
SQL Server Setup has detected incompatible components from Beta version of Visual Studio, .NETFramework or SQL Server 2005. Use Add or Remove to

I had earlier installed Beta 2 Version of Dev Studio 2005 and SQL Server 2005 Beta 2. I also had DevStudio 2003 and SQL Server installed. I have gone through and un-installed everything, but I keep getting this error.

I have also tried
msiexec /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
msiexec /x {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Both of these un-install start, but fail with error messages.

Would appreciate if anyone can help.

Saleem Yusuf
Saleem_Yusuf@.hotmail.com

Try the following.
1. Uninstall all visible Beta components in Add/Remove Programes.

2. Detect the Beta components infromation in the the log file located in %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetupNo_%machinename%_Core(Local).log.

3. Search the whole registry keys, remove those registy keys related to those Beta components. This is time-consuming.

4. Kill all Beta SQL Services (including SQL, OLAP, RS, SQLBROWSER, SQLAGENT, etc.) if they are existing with command sc.

5. Reboot the machine.

6. Start Setup again.|||I looked at the log and tried to uninstall old version, but it does not exists.
However, in the logs, I saw a version number and seach registry. They are many entries of SQL Server Express. I deleted some of them, but no luck yet. I am quite sure if I get rid of all the old registry setting, it should fix the problem.
Thanks for your help,

Saleem|||Problem fixed. I can now install SQL Server Express. Thanks for you help.
This is what I did.
Looked in file \Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG.
It had referecne to other log files. I opened one of the files, HostName_core.log
(notepad C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_<My_HostName>_Core.log)

This file had multiple reference to older versions of SQL Server Express. Example
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"

First I tried to uninstall, (MsiExec.exe /x {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}). Un-install failed.

Then I searched for 9.00.1399.06. I found multiple entried. I deleted them all.
After that I was able install SQL Server Express.
|||

I tried 3 other fixes on other forums (asp.net,etc.) and this is the only one that worked.

My log file had a similar message. However, I deleted the entries related to the older version (in the case above, that would be 9.00.1116); not the later or "expected at least" version (9.00.1399.06).

With this fix, I did not have to remove .net 1.0 beta or .net 1.1

|||Thanks for posting - that worked for me too - I had just spent my own money buying VS2005 Pro and couldn't install SQL Express because previously installed beta stuff was fouling up the install.

Perhaps the SQL guys at MS could revise the install script in future releases to 'clean up' before installing... Just a suggestion.

Anyway, just re-installed trhe whole .Net DVD and it's running now, so thanks!

Mark

Cannot install SQL Server Express

My system had a beta version of Visual Studio 2005 Express on it which I uninstalled. Apparently not correctly, as I can not install SQL Server 2005 Express. I have tried to removal procedures which either give me an error message or I cannot find the items in the Add/Remove program list that are requested. That is, it looks like the system should accept SQL Server 2005 Express, but it does not.

I have successfully installed Visual C++ 2005 Express. I have no clue as to what to do next and there is no documentation on what to do. I have looked at the various postings here, tried several of them, to no avail.

When I search the registry there are some 70 entries that have the string “SQLEXPRESS” in the entry. I am unsure if these are related to my previous beta install or related to the system (a475c HP Pavilion) needs. I am reluctant to start removing those entries.

So now what do I do? Is this really that difficult? And what if I decided to buy Visual Studio 2006, whenever it may be introduced? Will I not be able to install it?

Here is the log file that was generated yesterday, my latest attempt.

= = =


Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
Time : Sun Nov 05 17:32:58 2006
HOME-HP-XP : 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.


SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.


Time : Sun Nov 05 17:33:51 2006


List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_HOME-HP-XP_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_HOME-HP-XP_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt

= = =

Thanks

Thomas

Examine the log at C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_HOME-HP-XP_Core.log. This should give you the actual name of the incompatable components that are on your computer. You will need to remove those. If you can't find them in ARP you'll need to manually removing them using msiexec.exe /x <productID>. The product ID is in the log.

Mike

|||

Mike,

Thanks for the information.I am not there yet, but it looks like progress is being made!

I followed your instructions, looked in the file you mentioned and found a product ID and attempted to remove it by using

msiexec.exe /x <productID>

I got a dialog box error.It was entitled "Microsoft SQL Server 2005 Express Edition CTP" with the following contents:

= = =

The setup has encountered an unexpected error in the datastore.The action is RestoreSetupParams.The error is :Failed to read property "Installlds" {"MachineConfiguration", "", "HOME-HP-XP"} from cache

Unable to write property into cache: IsClustered

Unable to write property into cache: "IsClustered"

XmIRW Error: Failure Loading xmlrw.dll

CheckAllProcedures() returned: 2

= = =

What next?

Thanks.

Thomas

|||

The problems I was having have been expertly and enjoyably addressed by two posts on Aaron Stebner's WebLog at

http://blogs.msdn.com/astebner/archive/2005/07/01/434814.aspx

http://blogs.msdn.com/astebner/archive/2005/12/08/501885.aspx

I found these to be absolutely first rate explanations and the installation of SQL Express went through without problems after following these clear instructions.

Since I have been trying to solve this problem on and off for 6 months I have to wonder why this information is not posted on the Visual Studio 2005 Express Support page at

http://msdn.microsoft.com/vstudio/express/support/uninstall/

When those instructions failed there is no clue as to what to do next.

Thomas

Cannot install SQL Server Express

My system had a beta version of Visual Studio 2005 Express on it which I uninstalled. Apparently not correctly, as I can not install SQL Server 2005 Express. I have tried to removal procedures which either give me an error message or I cannot find the items in the Add/Remove program list that are requested. That is, it looks like the system should accept SQL Server 2005 Express, but it does not.

I have successfully installed Visual C++ 2005 Express. I have no clue as to what to do next and there is no documentation on what to do. I have looked at the various postings here, tried several of them, to no avail.

When I search the registry there are some 70 entries that have the string “SQLEXPRESS” in the entry. I am unsure if these are related to my previous beta install or related to the system (a475c HP Pavilion) needs. I am reluctant to start removing those entries.

So now what do I do? Is this really that difficult? And what if I decided to buy Visual Studio 2006, whenever it may be introduced? Will I not be able to install it?

Here is the log file that was generated yesterday, my latest attempt.

= = =


Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
Time : Sun Nov 05 17:32:58 2006
HOME-HP-XP : 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.


SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.


Time : Sun Nov 05 17:33:51 2006


List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_HOME-HP-XP_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_HOME-HP-XP_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt

= = =

Thanks

Thomas

Examine the log at C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_HOME-HP-XP_Core.log. This should give you the actual name of the incompatable components that are on your computer. You will need to remove those. If you can't find them in ARP you'll need to manually removing them using msiexec.exe /x <productID>. The product ID is in the log.

Mike

|||

Mike,

Thanks for the information.I am not there yet, but it looks like progress is being made!

I followed your instructions, looked in the file you mentioned and found a product ID and attempted to remove it by using

msiexec.exe /x <productID>

I got a dialog box error.It was entitled "Microsoft SQL Server 2005 Express Edition CTP" with the following contents:

= = =

The setup has encountered an unexpected error in the datastore.The action is RestoreSetupParams.The error is :Failed to read property "Installlds" {"MachineConfiguration", "", "HOME-HP-XP"} from cache

Unable to write property into cache: IsClustered

Unable to write property into cache: "IsClustered"

XmIRW Error: Failure Loading xmlrw.dll

CheckAllProcedures() returned: 2

= = =

What next?

Thanks.

Thomas

|||

The problems I was having have been expertly and enjoyably addressed by two posts on Aaron Stebner's WebLog at

http://blogs.msdn.com/astebner/archive/2005/07/01/434814.aspx

http://blogs.msdn.com/astebner/archive/2005/12/08/501885.aspx

I found these to be absolutely first rate explanations and the installation of SQL Express went through without problems after following these clear instructions.

Since I have been trying to solve this problem on and off for 6 months I have to wonder why this information is not posted on the Visual Studio 2005 Express Support page at

http://msdn.microsoft.com/vstudio/express/support/uninstall/

When those instructions failed there is no clue as to what to do next.

Thomas

Cannot install SQL Express; peculiar error

SQL Express installation is bombing out with the "A beta version of the .NET Framework 2.0 or SQL Server was detected on the computer...".

From the log file:

Running: PerformSCCAction2 at: 2007/6/26 8:17:27
Loaded DLL:C:\WIN\system32\msi.dll Version:3.1.4000.2435
Product "{7131646D-CD3C-40F4-97B9-CD9E4E6262EF}" versioned 2.0 is not compatible with current builds of SQL Server.Expected at least version: 2.0.50727.42
The Product Name is ".NET Framework"

Now what is peculiar to me is that

1) this machine should have never had the beta software on it;

2) I have seen people with similar issues except their versioned info always said "versioned 2.0.50727" and the product guid is different, this one only says "2.0"; and

3) I thought that product guid was for the RTM 2.0.50727.42 release!

What is going on here and where is it getting this version information?

brian

Try running the removal tool from here: http://go.microsoft.com/fwlink/?LinkId=47598

Jens K. Suessmeyer

http://www.sqlserver2005.de

Saturday, February 25, 2012

Cannot install server components

I have the beta version of RS running fine on Windows 2000 Server (SP4), IIS 5, and SQL Server 2000 Enterprise (SP3a). No issues at all.
However, when trying to install the RS release candidate, for some reason I am not presented with the server components option - I can only see the client tools option.
Can anyone assist?Did you receive any prereq warnings?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ravinder" <Ravinder@.discussions.microsoft.com> wrote in message
news:0E870307-157B-4509-9003-B6CC934C4DDB@.microsoft.com...
> I have the beta version of RS running fine on Windows 2000 Server (SP4),
IIS 5, and SQL Server 2000 Enterprise (SP3a). No issues at all.
> However, when trying to install the RS release candidate, for some reason
I am not presented with the server components option - I can only see the
client tools option.
> Can anyone assist?|||I finally got the install working properly. As a last resort I re-installed Win2k SP4 and low and behold I am now able to install RS Server Components without any issues at all.
Microsoft might want to add this "known issue" to the install notes.
"Daniel Reib [MSFT]" wrote:
> Did you receive any prereq warnings?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Ravinder" <Ravinder@.discussions.microsoft.com> wrote in message
> news:0E870307-157B-4509-9003-B6CC934C4DDB@.microsoft.com...
> > I have the beta version of RS running fine on Windows 2000 Server (SP4),
> IIS 5, and SQL Server 2000 Enterprise (SP3a). No issues at all.
> >
> > However, when trying to install the RS release candidate, for some reason
> I am not presented with the server components option - I can only see the
> client tools option.
> >
> > Can anyone assist?
>
>

Thursday, February 16, 2012

Cannot get SSCE 3.5 beta 2 to work

I'm running VS2008 beta2. I've succefully added a SDF database file to my project and created a couple of tables in it from VS. I added a reference to the System.Data.SqlCeConnection. When I try to create a new instance of the SqlCeConnection class I get a nasty error that states I'm missing the 'sqlceme35.dll' file. I copy all of the files .dll into by bin folder. Now I'm getting a BadImageFormat error when I create an instance. Does anyone know what that means? or why I had to copy those files to begin with? This is very odd. Any help would be appreciated. I am new to SqlCe.

Hi

I can't help - having the same problem but getting this error

Unable to load DLL 'sqlceme35.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)

when I try and add

C:\Program Files (x86)\Microsoft SQL Server Compact Edition\v3.5\sqlceme35.dll

as a reference then I get another error

Microsoft Visual Studio

A reference to 'C:\Program Files (x86)\Microsoft SQL Server Compact Edition\v3.5\sqlceme35.dll' could not be added. Please make sure that the file is accessible, and that it is a valid assembly or COM component.

OK

Hoping for an answer as well

Mike
|||

Mike,

I'm starting to think it has something to do with x64. I'm only getting this error Windows Server 2003 x64 and on Vista x64. However, when I install VS2008 on Vista x86, I have not seen the issue (at least not so far). What platform are you running on?

Jon

|||

This DLL is not a COM object or .NET assembly so it can't be added as reference and it should not be. It should be simply located in your %WINDIR%\System32 or in your application folder.

Also make sure to mark your application as x86 (platform target in project properties or you won't be able to use SQL CE in 64 bit OS.

|||Arg.. That sucks no SQL CE for 64-bit.. Why does VS install all of the tools and SDKs for SQL CE on 64-bit if you can't use it ?

|||

You can - in 32 bit mode. That's the way most applications work on 64 bit OS today.

|||

Jon

Looks like it - I am running Vista 64

All seeems fine ov XP 32

Hope there is a work round

Mike

|||

Hi Ilya

Thanks - I can get a compile and successfull run once I switch to x86 in Orcas Beta 2

but I still can't run SQLMetal in Vista64 either the 32bit version of sqlmetal

Any advice ?

Thanks again

Mike

|||

Go ahead and file a bug here.