Problem Querying a Visual Foxpro DBF

Good day,

Current Setup:

Using:
Visual Web Developer Express
SQL Express
IIS 6.0 with >net 2.0 Installed
Visual Foxpro

I actually have two questions (but am making good progress so will focus on the issue at hand).

1. I setup a Login.aspx / Default.aspx / Register.apsx / Membership.aspx as specified in the examples in MSDN...all is working ok.

2. When I register a new user, I wanted to capture their Customer ID during login to store in their Membership view table. I did this and is working ok....and to make it easy, am storing the value in Comments field.

3. I want to query a Visual Fox free table (DBF) that contains my client's Customer Invoice data...and have the ODBC Connection setup and working properly.

Here's the problem....

I'm having trouble formulating the SELECT string within the asp code to capture the Membership.Comments field.

I need the proper functions to grab the Comments field data and then use it within my select statement.

Presently, the query works if I just hard-code the value i.e.

"SELECT * from [invdata] WHERE cus_no = '1' "

I need to replace the '1' with the comments field data.

Thanks:

On a side issue: it took me days to just to get this all working to where it is...does anyone have a detailed example of how to Login to a site and pass the parms to another page to query the Logged In user's data from a database......a real world example that I have yet to see highlighted anywhere in the Forums or books I've bought.

For example: I am customer ABC123, I log in to my vendor's site and want to see all my orders placed.

Hi JCquaz,

First off, have you considered using the FoxPro and Visual FoxPro OLE DB data provider, downloadable from msdn.microsoft.com/vfoxpro/downloads/updates ? It works with all versions of Fox tables.

I'm a little confused - Is "Cus_No" the name of the Memo field or is it "Comments?"

The comparison of a character value such as '1' to a Varchar value such as what SQL does with the Fox Memo field doesn't work. When I tested against the value of '1' stored in a Memo field I had to use Cast and Like in code like this:

Select * From TestMemo Where Cast(MemoField As Character(10)) Like '1%'

problem or bug in sqlxml 3.0

Im using Sqlxml 30 with sql 2000 and Visual studio 2003.
if I generate my xmldata file manaually it works fine, However if i
generate it using VisualStudio
using dataset.writexml with ignoreSchema method i get an invalid xml
file.The result is that sql xml creates an empty sql table !
The only difference in the xml file is the following :
<ds xmlns="http://www.tempuri.org/Ds.xsd">
..
</ds>
I presume the xmlns is the namespace stuff but why should its presence
break SQLXML.
Any ideas how to generate the file from the dataset object without this
attribute ?Obviously i am new to this stuff, im trying to get used to using Bulkload
Colin|||You might be able to solve the problem by specifying an annotated schema
that includes the same namespace in the Execute method. If you post your
XML, schema, and code maybe someone can help you out.
Cheers,
Graeme
_____________________
Graeme Malcolm
Principal Technologist
Content Master
- a member of CM Group
www.contentmaster.com
"Colin Robinson" <colin@.rem_doubleclicksystems.co.uk> wrote in message
news:%23ZNMx1q8FHA.3804@.TK2MSFTNGP12.phx.gbl...
> Obviously i am new to this stuff, im trying to get used to using Bulkload
> Colin
>|||my actual files are two large to post here; but find below the code in
dotnet that should be self explanatory. as i say it works if I edit these
files to look like the Sqlxml samples:
Any assistance would be appreciated here:
'This creates my XML AND XSD files from a dataset dspos
'Me.DsPOS.WriteXml(SaveFileDialog.FileName,
XmlWriteMode.WriteSchema) 'writes with inline schema
'DsPOS.WriteXml("C:\Documents and
Settings\Administrator\Desktop\Updateser
ver.xml", XmlWriteMode.IgnoreSchema)
'writes without inline schema
'Me.DsPOS.WriteXmlSchema(SaveFileDialog.FileName.Replace("xml",
"xsd")) ' Creates the xsd file
'should now have everything i need for sqlxml so ...
'This should bulk load into an existing db named testdb creating the
tables as required
Dim objbl As New Object
objBL = CreateObject("SQLXMLBulkLoad.SQLXMLBulkload.3.0")
objbl.ConnectionString = "Provider=SQLOLEDB;Data
Source=(local);Persist Security Info=True;User ID=sa;Initial Catalog=Testdb"
objbl.ErrorLogFile = "C:\Documents and
Settings\Administrator\Desktop\error.log"
objbl.ErrorLogFile = "C:\Documents and
Settings\Administrator\Desktop\Tposerror
.txt"
objbl.CheckConstraints = False
objbl.XMLFragment = False
objbl.SchemaGen = True
objbl.SGDropTables = True
Try
'test with hardcoded filenames
objbl.Execute("C:\Documents and
Settings\Administrator\Desktop\TposSchem
a.xsd", "C:\Documents and
Settings\Administrator\Desktop\Updateser
ver.xml")
Catch ex As Exception
MsgBox(ex.Message)
End Try
objbl = Nothing
MsgBox("Complete")|||Hi Colin
Do you still have a problem? If so let me know and I will get somebody to
look into it.
Best regards
Michael
"Colin Robinson" <z@.x.com> wrote in message
news:%23it6zn28FHA.1188@.TK2MSFTNGP12.phx.gbl...
> my actual files are two large to post here; but find below the code in
> dotnet that should be self explanatory. as i say it works if I edit these
> files to look like the Sqlxml samples:
> Any assistance would be appreciated here:
>
> 'This creates my XML AND XSD files from a dataset dspos
> 'Me.DsPOS.WriteXml(SaveFileDialog.FileName,
> XmlWriteMode.WriteSchema) 'writes with inline schema
> 'DsPOS.WriteXml("C:\Documents and
> Settings\Administrator\Desktop\Updateser
ver.xml",
> XmlWriteMode.IgnoreSchema) 'writes without inline schema
> 'Me.DsPOS.WriteXmlSchema(SaveFileDialog.FileName.Replace("xml",
> "xsd")) ' Creates the xsd file
> 'should now have everything i need for sqlxml so ...
> 'This should bulk load into an existing db named testdb creating
> the tables as required
> Dim objbl As New Object
> objBL = CreateObject("SQLXMLBulkLoad.SQLXMLBulkload.3.0")
> objbl.ConnectionString = "Provider=SQLOLEDB;Data
> Source=(local);Persist Security Info=True;User ID=sa;Initial
> Catalog=Testdb"
> objbl.ErrorLogFile = "C:\Documents and
> Settings\Administrator\Desktop\error.log"
> objbl.ErrorLogFile = "C:\Documents and
> Settings\Administrator\Desktop\Tposerror
.txt"
> objbl.CheckConstraints = False
> objbl.XMLFragment = False
> objbl.SchemaGen = True
> objbl.SGDropTables = True
> Try
> 'test with hardcoded filenames
> objbl.Execute("C:\Documents and
> Settings\Administrator\Desktop\TposSchem
a.xsd", "C:\Documents and
> Settings\Administrator\Desktop\Updateser
ver.xml")
> Catch ex As Exception
> MsgBox(ex.Message)
> End Try
> objbl = Nothing
> MsgBox("Complete")
>
>|||thanks its still a problem.
must be something to do with the namespaces in the file headers. when i
execute it it does not error. i think its just not finding valid data to
create even though the xml is well formed.
Colin
"Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
news:uItNInQAGHA.1124@.TK2MSFTNGP10.phx.gbl...
> Hi Colin
> Do you still have a problem? If so let me know and I will get somebody to
> look into it.
> Best regards
> Michael
> "Colin Robinson" <z@.x.com> wrote in message
> news:%23it6zn28FHA.1188@.TK2MSFTNGP12.phx.gbl...
>|||The problem was in the headers, I trashed the dotnet headers and replace
with the example header for bulkinsert schema. Did an edit replace to change
the xs: attributes to XSD: and it worked fine inserting 20,000 records in 7
seconds into a new table. Beating dts on the same box
Someone should get the ado net team to talk to the Sqlxml team to export the
xsd in a standard way across microsoft products! Especially relevant with
dotnet and sql being so closely coupled.
"Colin Robinson" <colin@.Doubleclicksystems.co.uk.nospam> wrote in message
news:%23zBglxFDGHA.812@.TK2MSFTNGP10.phx.gbl...
> thanks its still a problem.
> must be something to do with the namespaces in the file headers. when i
> execute it it does not error. i think its just not finding valid data to
> create even though the xml is well formed.
> Colin
> "Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
> news:uItNInQAGHA.1124@.TK2MSFTNGP10.phx.gbl...
>|||Hi Colin
Ahh, good. The problem is that the prefixes should have a namespace uri
associated. The semantics is carried with the namespace URI and not the
prefix (ie xs, xsd).
Thanks for getting back to us with what your problem was though.
Best regards
Michael
"Colin Robinson" <colin@.Doubleclicksystems.co.uk.nospam> wrote in message
news:%235BWvIKDGHA.3748@.TK2MSFTNGP10.phx.gbl...
> The problem was in the headers, I trashed the dotnet headers and replace
> with the example header for bulkinsert schema. Did an edit replace to
> change the xs: attributes to XSD: and it worked fine inserting 20,000
> records in 7 seconds into a new table. Beating dts on the same box
> Someone should get the ado net team to talk to the Sqlxml team to export
> the xsd in a standard way across microsoft products! Especially relevant
> with dotnet and sql being so closely coupled.
> "Colin Robinson" <colin@.Doubleclicksystems.co.uk.nospam> wrote in message
> news:%23zBglxFDGHA.812@.TK2MSFTNGP10.phx.gbl...
>|||Michael.
Can you explain that in more detail then i could probably understad why i
had to make these changes manually. and may be able to overload writeXML
method to generate myself a valid XSD
if i read what you are saying correctly as long as dotnet produces a valid
url/Prefix pair you have a valid xsd. but not one that is compliant with
SQLXML !!!
next questions become
Is there a published resourse of these schemes.
Are there any conversion utils to convert one to the other.
why doesnt MS use the same one for all its products even if its not industry
standard.
and finally It would still be better if some sort of error message pointed
to the problem.
"Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
news:uy4VN3ODGHA.1816@.TK2MSFTNGP11.phx.gbl...
> Hi Colin
> Ahh, good. The problem is that the prefixes should have a namespace uri
> associated. The semantics is carried with the namespace URI and not the
> prefix (ie xs, xsd).
> Thanks for getting back to us with what your problem was though.
> Best regards
> Michael
> "Colin Robinson" <colin@.Doubleclicksystems.co.uk.nospam> wrote in message
> news:%235BWvIKDGHA.3748@.TK2MSFTNGP10.phx.gbl...
>|||Hi Colin
You said yourself that you

That means that the generated XSD was fine, but then you changed it. By
doing so you seem to have lost some namespace prefix declarations...
An XML document <mynick:foo xmlns:mynick="uri"/> is the same as
<yournick:foo xmlns:yournick="foo"/> since the namespace prefix only servers
as an alias to the URI.
Every XML Schema however should work to some extend with SQLXML Bulkload
(especially once you have added your annotations).
Best regards
Michael
"Colin Robinson" <colin@.Doubleclicksystems.co.uk.nospam> wrote in message
news:%23Exe0FsDGHA.2956@.TK2MSFTNGP14.phx.gbl...
> Michael.
> Can you explain that in more detail then i could probably understad why i
> had to make these changes manually. and may be able to overload writeXML
> method to generate myself a valid XSD
> if i read what you are saying correctly as long as dotnet produces a valid
> url/Prefix pair you have a valid xsd. but not one that is compliant with
> SQLXML !!!
> next questions become
> Is there a published resourse of these schemes.
> Are there any conversion utils to convert one to the other.
> why doesnt MS use the same one for all its products even if its not
> industry standard.
> and finally It would still be better if some sort of error message
> pointed to the problem.
>
>
> "Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
> news:uy4VN3ODGHA.1816@.TK2MSFTNGP11.phx.gbl...
>

problem or bug in sqlxml 3.0

Im using Sqlxml 30 with sql 2000 and Visual studio 2003.
if I generate my xmldata file manaually it works fine, However if i
generate it using VisualStudio
using dataset.writexml with ignoreSchema method i get an invalid xml
file.The result is that sql xml creates an empty sql table !
The only difference in the xml file is the following :
<ds xmlns="http://www.tempuri.org/Ds.xsd">
...
</ds>
I presume the xmlns is the namespace stuff but why should its presence
break SQLXML.
Any ideas how to generate the file from the dataset object without this
attribute ?
Obviously i am new to this stuff, im trying to get used to using Bulkload
Colin
|||You might be able to solve the problem by specifying an annotated schema
that includes the same namespace in the Execute method. If you post your
XML, schema, and code maybe someone can help you out.
Cheers,
Graeme
_____________________
Graeme Malcolm
Principal Technologist
Content Master
- a member of CM Group
www.contentmaster.com
"Colin Robinson" <colin@.rem_doubleclicksystems.co.uk> wrote in message
news:%23ZNMx1q8FHA.3804@.TK2MSFTNGP12.phx.gbl...
> Obviously i am new to this stuff, im trying to get used to using Bulkload
> Colin
>
|||my actual files are two large to post here; but find below the code in
dotnet that should be self explanatory. as i say it works if I edit these
files to look like the Sqlxml samples:
Any assistance would be appreciated here:
'This creates my XML AND XSD files from a dataset dspos
'Me.DsPOS.WriteXml(SaveFileDialog.FileName,
XmlWriteMode.WriteSchema) 'writes with inline schema
'DsPOS.WriteXml("C:\Documents and
Settings\Administrator\Desktop\Updateserver.xml", XmlWriteMode.IgnoreSchema)
'writes without inline schema
'Me.DsPOS.WriteXmlSchema(SaveFileDialog.FileName.R eplace("xml",
"xsd")) ' Creates the xsd file
'should now have everything i need for sqlxml so ...
'This should bulk load into an existing db named testdb creating the
tables as required
Dim objbl As New Object
objBL = CreateObject("SQLXMLBulkLoad.SQLXMLBulkload.3.0")
objbl.ConnectionString = "Provider=SQLOLEDB;Data
Source=(local);Persist Security Info=True;User ID=sa;Initial Catalog=Testdb"
objbl.ErrorLogFile = "C:\Documents and
Settings\Administrator\Desktop\error.log"
objbl.ErrorLogFile = "C:\Documents and
Settings\Administrator\Desktop\Tposerror.txt"
objbl.CheckConstraints = False
objbl.XMLFragment = False
objbl.SchemaGen = True
objbl.SGDropTables = True
Try
'test with hardcoded filenames
objbl.Execute("C:\Documents and
Settings\Administrator\Desktop\TposSchema.xsd", "C:\Documents and
Settings\Administrator\Desktop\Updateserver.xml")
Catch ex As Exception
MsgBox(ex.Message)
End Try
objbl = Nothing
MsgBox("Complete")
|||Hi Colin
Do you still have a problem? If so let me know and I will get somebody to
look into it.
Best regards
Michael
"Colin Robinson" <z@.x.com> wrote in message
news:%23it6zn28FHA.1188@.TK2MSFTNGP12.phx.gbl...
> my actual files are two large to post here; but find below the code in
> dotnet that should be self explanatory. as i say it works if I edit these
> files to look like the Sqlxml samples:
> Any assistance would be appreciated here:
>
> 'This creates my XML AND XSD files from a dataset dspos
> 'Me.DsPOS.WriteXml(SaveFileDialog.FileName,
> XmlWriteMode.WriteSchema) 'writes with inline schema
> 'DsPOS.WriteXml("C:\Documents and
> Settings\Administrator\Desktop\Updateserver.xml",
> XmlWriteMode.IgnoreSchema) 'writes without inline schema
> 'Me.DsPOS.WriteXmlSchema(SaveFileDialog.FileName.R eplace("xml",
> "xsd")) ' Creates the xsd file
> 'should now have everything i need for sqlxml so ...
> 'This should bulk load into an existing db named testdb creating
> the tables as required
> Dim objbl As New Object
> objBL = CreateObject("SQLXMLBulkLoad.SQLXMLBulkload.3.0")
> objbl.ConnectionString = "Provider=SQLOLEDB;Data
> Source=(local);Persist Security Info=True;User ID=sa;Initial
> Catalog=Testdb"
> objbl.ErrorLogFile = "C:\Documents and
> Settings\Administrator\Desktop\error.log"
> objbl.ErrorLogFile = "C:\Documents and
> Settings\Administrator\Desktop\Tposerror.txt"
> objbl.CheckConstraints = False
> objbl.XMLFragment = False
> objbl.SchemaGen = True
> objbl.SGDropTables = True
> Try
> 'test with hardcoded filenames
> objbl.Execute("C:\Documents and
> Settings\Administrator\Desktop\TposSchema.xsd", "C:\Documents and
> Settings\Administrator\Desktop\Updateserver.xml")
> Catch ex As Exception
> MsgBox(ex.Message)
> End Try
> objbl = Nothing
> MsgBox("Complete")
>
>
|||thanks its still a problem.
must be something to do with the namespaces in the file headers. when i
execute it it does not error. i think its just not finding valid data to
create even though the xml is well formed.
Colin
"Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
news:uItNInQAGHA.1124@.TK2MSFTNGP10.phx.gbl...
> Hi Colin
> Do you still have a problem? If so let me know and I will get somebody to
> look into it.
> Best regards
> Michael
> "Colin Robinson" <z@.x.com> wrote in message
> news:%23it6zn28FHA.1188@.TK2MSFTNGP12.phx.gbl...
>
|||The problem was in the headers, I trashed the dotnet headers and replace
with the example header for bulkinsert schema. Did an edit replace to change
the xs: attributes to XSD: and it worked fine inserting 20,000 records in 7
seconds into a new table. Beating dts on the same box
Someone should get the ado net team to talk to the Sqlxml team to export the
xsd in a standard way across microsoft products! Especially relevant with
dotnet and sql being so closely coupled.
"Colin Robinson" <colin@.Doubleclicksystems.co.uk.nospam> wrote in message
news:%23zBglxFDGHA.812@.TK2MSFTNGP10.phx.gbl...
> thanks its still a problem.
> must be something to do with the namespaces in the file headers. when i
> execute it it does not error. i think its just not finding valid data to
> create even though the xml is well formed.
> Colin
> "Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
> news:uItNInQAGHA.1124@.TK2MSFTNGP10.phx.gbl...
>
|||Hi Colin
Ahh, good. The problem is that the prefixes should have a namespace uri
associated. The semantics is carried with the namespace URI and not the
prefix (ie xs, xsd).
Thanks for getting back to us with what your problem was though.
Best regards
Michael
"Colin Robinson" <colin@.Doubleclicksystems.co.uk.nospam> wrote in message
news:%235BWvIKDGHA.3748@.TK2MSFTNGP10.phx.gbl...
> The problem was in the headers, I trashed the dotnet headers and replace
> with the example header for bulkinsert schema. Did an edit replace to
> change the xs: attributes to XSD: and it worked fine inserting 20,000
> records in 7 seconds into a new table. Beating dts on the same box
> Someone should get the ado net team to talk to the Sqlxml team to export
> the xsd in a standard way across microsoft products! Especially relevant
> with dotnet and sql being so closely coupled.
> "Colin Robinson" <colin@.Doubleclicksystems.co.uk.nospam> wrote in message
> news:%23zBglxFDGHA.812@.TK2MSFTNGP10.phx.gbl...
>
|||Michael.
Can you explain that in more detail then i could probably understad why i
had to make these changes manually. and may be able to overload writeXML
method to generate myself a valid XSD
if i read what you are saying correctly as long as dotnet produces a valid
url/Prefix pair you have a valid xsd. but not one that is compliant with
SQLXML !!!
next questions become
Is there a published resourse of these schemes.
Are there any conversion utils to convert one to the other.
why doesnt MS use the same one for all its products even if its not industry
standard.
and finally It would still be better if some sort of error message pointed
to the problem.
"Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
news:uy4VN3ODGHA.1816@.TK2MSFTNGP11.phx.gbl...
> Hi Colin
> Ahh, good. The problem is that the prefixes should have a namespace uri
> associated. The semantics is carried with the namespace URI and not the
> prefix (ie xs, xsd).
> Thanks for getting back to us with what your problem was though.
> Best regards
> Michael
> "Colin Robinson" <colin@.Doubleclicksystems.co.uk.nospam> wrote in message
> news:%235BWvIKDGHA.3748@.TK2MSFTNGP10.phx.gbl...
>
|||Hi Colin
You said yourself that you
[vbcol=seagreen]
That means that the generated XSD was fine, but then you changed it. By
doing so you seem to have lost some namespace prefix declarations...
An XML document <mynick:foo xmlns:mynick="uri"/> is the same as
<yournick:foo xmlns:yournick="foo"/> since the namespace prefix only servers
as an alias to the URI.
Every XML Schema however should work to some extend with SQLXML Bulkload
(especially once you have added your annotations).
Best regards
Michael
"Colin Robinson" <colin@.Doubleclicksystems.co.uk.nospam> wrote in message
news:%23Exe0FsDGHA.2956@.TK2MSFTNGP14.phx.gbl...
> Michael.
> Can you explain that in more detail then i could probably understad why i
> had to make these changes manually. and may be able to overload writeXML
> method to generate myself a valid XSD
> if i read what you are saying correctly as long as dotnet produces a valid
> url/Prefix pair you have a valid xsd. but not one that is compliant with
> SQLXML !!!
> next questions become
> Is there a published resourse of these schemes.
> Are there any conversion utils to convert one to the other.
> why doesnt MS use the same one for all its products even if its not
> industry standard.
> and finally It would still be better if some sort of error message
> pointed to the problem.
>
>
> "Michael Rys [MSFT]" <mrys@.online.microsoft.com> wrote in message
> news:uy4VN3ODGHA.1816@.TK2MSFTNGP11.phx.gbl...
>

problem of creating database

I am using Visula Studio 2005. When i try to create database from the visual studio Tools option-> careate database and press ok then following error occur......

Failed to generate a user instance of SQL Server due to a failure in copying database files. The connection will be closed.

how can i fix the problem?

first of all you must have a clear picture what is this User intance and do u really want to create user instance. if the answer is yes refer this link the problem is discussed here

http://forums.microsoft.com/msdn/showpost.aspx?postid=98346&siteid=1

If you don't need user instance then go to SQL Server man agement studio and create database

Madhu

|||

i have told that when i am creating database in SQL SERVER 2005, it shows that it can't create instance of sql server. it clearly explains that the user instance is Sql Server instance. See my problem again.......

Here is the error

........

Failed to generate a user instance of SQL Server due to a failure in copying database files. The connection will be closed.

.........

|||

But...do you want to create user instance, or do you want to create a database on a server instance ? If the latter, you will have to use the server explorer, not the Add New Item > Database.

If you want to create a user instance, you will need to have SQLExpress installed on the machine and configured in the database option of Visual Studio.

Jens K. Suessmeyer

http://www.sqlserver2005.de

Problem Making Sql database Connection in Deployed Site

VWD 2005 Express. Visual Basic. Sql Server 2005. I am trying to establish a connection to a SQL database. The connection (and all other database reads and writes) work fine in debug and in "view in browser" from VWD. I am running the VWD on the same server that hosts the site. When on my server (Windows 2003 Server) under IIS, the connection attempt times out.

Below is the code that is failing (only on the server when deployed):

PrivateSharedSub OpenConn(ByVal cmdAs SqlCommand,ByVal SuccessAsBoolean)

Dim connAsNew SqlConnection(System.Configuration.ConfigurationManager.ConnectionStrings("GoodNews_IntranetConnectionString").ToString)

'The connection string resolves to ("Data Source=HQSERVER\HQSERVER;Initial Catalog=GoodNews_Intranet;Integrated Security=True"

Try

conn.Open()

cmd.Connection = conn

Success =True

Catch exAs Exception

Success =False

EndTry

EndSub

It would be great if you could post the error message that you are getting.

And in a hosted environment, it is advisable to protect your database by providing a username and password.

|||

That may be the ticket. The database does require windows authentication, so how may I make the connection (in vb code) providing a username and password? Perhaps when I am in debug, the sql calls use my windows login, however, when on the server, there is not password being passed?

|||

Please visitwww.connectionstrings.com to know the syntax for creating a connection string for your backend with user name and password.

If you think, this resolves your problem, please mark the post as "Answer". by this way we all know your issue is resolved

|||

Thank you. I found the answer on the page. I put the User Id and Password in the web.config file where the connection is defined. How can I ensure that this will not be readable when the web site is deployed?

|||

It won't be readable to a normal user, but for added security, if its not already in web.confing, then put it there. You can then use encryption to encrypt the connectionstring section (which is much easier than it sounds).

This might help:

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

|||

WEB.CONFIG file is a secure one. No one can read that file outside of your application. In other words, web.config can only be read by the pages within application.

every body uses the web.config to store connection strings and is safe so far.

read the following article to know more about web.config.

http://www.aspdev.org/articles/web.config/

also, please do not forget to mark my post as answer so that we will know for sure that your issue has been resolved.

PROBLEM INSTALLING SQL SERVER EXPRESS

Hi,

I successfully installed Visual Basic 2005 express edition and but the SQL Server component did not get installed.

12:37:11 AM Sunday, April 09, 2006: [Fail] ConfigSamplesDll_DoTasks:: [Fail] Config_SSE_INST_Install: SQL Express service install (failed). The process did not return a success value. ExitCode: 1282 Command: 'C:\Documents and Settings\Oluwaseyi Awoga\Local Settings\Temp\SQLEXPR32.exe -q /norebootchk /qn reboot=ReallySuppress addlocal=all SCCCHECKLEVEL=IncompatibleComponents:1 instancename=SQLEXPRESS'.

I keep getting this error. Can anybody help me? I have uninstalled and installed ALL versions of the .NET framework etc several times. Thanks

This is also the error signature. Thanks for your help.

Error Signature:
EventType : BEX P1 : setup.exe P2 : 2005.90.1399.0 P3 : 434f6403
P4 : msdtcprx.dll P5 : 2001.12.4414.258 P6 : 41109703 P7 : 0000a2c9
P8 : c0000409 P9 : 00000000

|||

This is the content of the C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

Microsoft SQL Server 2005 Setup beginning at Sun Apr 09 01:46:18 2006
Process ID : 952
c:\e37376beb65a16277a8441b9\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2006/3/9 1:46:17
Complete: LoadResourcesAction at: 2006/3/9 1:46:18, returned true
Running: ParseBootstrapOptionsAction at: 2006/3/9 1:46:18
Loaded DLL:c:\e37376beb65a16277a8441b9\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2006/3/9 1:46:18, returned true
Running: ValidateWinNTAction at: 2006/3/9 1:46:18
Complete: ValidateWinNTAction at: 2006/3/9 1:46:18, returned true
Running: ValidateMinOSAction at: 2006/3/9 1:46:18
Complete: ValidateMinOSAction at: 2006/3/9 1:46:18, returned true
Running: PerformSCCAction at: 2006/3/9 1:46:18
Complete: PerformSCCAction at: 2006/3/9 1:46:18, returned true
Running: ActivateLoggingAction at: 2006/3/9 1:46:18
Complete: ActivateLoggingAction at: 2006/3/9 1:46:18, returned true
Running: DetectPatchedBootstrapAction at: 2006/3/9 1:46:18
Complete: DetectPatchedBootstrapAction at: 2006/3/9 1:46:18, returned true
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__952" returned false.
Running: PerformSCCAction2 at: 2006/3/9 1:46:18
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Complete: PerformSCCAction2 at: 2006/3/9 1:46:18, returned true
Running: PerformDotNetCheck at: 2006/3/9 1:46:18
Complete: PerformDotNetCheck at: 2006/3/9 1:46:18, returned true
Running: ComponentUpdateAction at: 2006/3/9 1:46:18
Complete: ComponentUpdateAction at: 2006/3/9 1:46:23, returned true
Running: DetectLocalBootstrapAction at: 2006/3/9 1:46:23
Complete: DetectLocalBootstrapAction at: 2006/3/9 1:46:23, returned true
Running: LaunchLocalBootstrapAction at: 2006/3/9 1:46:23
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 1282
Aborting queue processing as nested installer has completed
Message pump returning: 1282

Thanks!!

|||

I'm going to move this to the SQL Setup forum.

- Mike

|||

I don't believe 1282 is a Setup error code; it's probably a Windows error code. 1282 translates to stack buffer overflow. We did fix one or two such issues a long time back. If the version of Express you're trying to install is pre-RTM then please download the RTM version or the remastered Express SP1 which should be available soon, and try again. If you're already trying with RTM then I suspect we're going to need to see the complete SQL Install logs to debug your problem.

Paul

Problem installing SQL Express

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 the run SQL Server 2005 Setup again.
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
I used Add/Remove Progs and used the list in the order suggested to remove all beta versions of VB, SQL, .NET and etc. Nothing is listed. I do have VB6 PRO. I have looked for directories and removed all. I have searched for SQLexpress in the registry and eliminated all I could find. I reinstalled .Net 2.0 and I'm still finding this problem.
Microsoft SQL Server 2005 Setup beginning at Thu Jun 08 17:37:43 2006
Process ID : 164
c:\90b92fd6a1de42b9ee\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/5/8 17:37:43
Complete: LoadResourcesAction at: 2006/5/8 17:37:43, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43
Loaded DLL:c:\90b92fd6a1de42b9ee\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43, returned true
Running: ValidateWinNTAction at: 2006/5/8 17:37:43
Complete: ValidateWinNTAction at: 2006/5/8 17:37:43, returned true
Running: ValidateMinOSAction at: 2006/5/8 17:37:43
Complete: ValidateMinOSAction at: 2006/5/8 17:37:43, returned true
Running: PerformSCCAction at: 2006/5/8 17:37:43
Complete: PerformSCCAction at: 2006/5/8 17:37:43, returned true
Running: ActivateLoggingAction at: 2006/5/8 17:37:43
Complete: ActivateLoggingAction at: 2006/5/8 17:37:43, 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__164" returned false.
Running: PerformSCCAction2 at: 2006/5/8 17:37:43
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools 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

Thank you for your assistance.

Hi Gary,

If you can't find the product listed in the Add/Remove Program listing (they would be listed under Microsoft SQL Server 2005), then you can try manually removing the offending products using the Product ID. The two problem commonents are identified as

Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"

You can manually remove them by typing the following into the Run dialog:

msiexec /x <product id>

Where <product id> is the GUID referenced from your log file.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

|||

I am having a similar problem.

Microsoft SQL Server 2005 Setup beginning at Thu Aug 10 14:33:57 2006
Process ID : 1604
d:\51b5dbc1449baa0bbd43\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/7/10 14:33:57
Complete: LoadResourcesAction at: 2006/7/10 14:33:57, returned true
Running: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57
Loaded DLL:d:\51b5dbc1449baa0bbd43\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57, returned true
Running: ValidateWinNTAction at: 2006/7/10 14:33:57
Complete: ValidateWinNTAction at: 2006/7/10 14:33:57, returned true
Running: ValidateMinOSAction at: 2006/7/10 14:33:57
Complete: ValidateMinOSAction at: 2006/7/10 14:33:57, returned true
Running: PerformSCCAction at: 2006/7/10 14:33:57
Complete: PerformSCCAction at: 2006/7/10 14:33:57, returned true
Running: ActivateLoggingAction at: 2006/7/10 14:33:57
Complete: ActivateLoggingAction at: 2006/7/10 14:33:57, 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__1604" returned false.
Running: PerformSCCAction2 at: 2006/7/10 14:33:58
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools 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.

there are no items in add/remove programs.

when i attempt to run

msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD

i recieve an error message

"this instilation package could not be opened. verify

that the package exists and that you can access it, or

contact the application vendoe to verify that this is a

valid windows installer package"

any one help me?

thanks

Drance

|||

lost my post can not be bothered to re type it

|||

Me too.

We had the CTP version installed. Now it finds various CTP "Products" even though I removed the CTP versions using Add-Remove Programs.

Of course, if these things were vital to my operation, the slightest breeze would erase them forever.

Good Luck,

Mike

|||

Drance wrote:

I am having a similar problem.

...

Class not registered.

there are no items in add/remove programs.

when i attempt to run

msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD

i recieve an error message

"any one help me?

thanks

Drance

Try:

msiexec /x "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}"

|||

I have a problem that when I try to uninstall the offending package I get this Error Message:

The setup has encountered an unexpected error in datastore. The action is SetInstanceProperty. The Error is

:Failed to read property "InstallIds" {"MachineConfiguration".""."SAM"} from Cache

Unable to write poperty into cache: IsClustered

Unable to write poperty into cache: "IsClustered"

XmlRWError: failure loading xmlrw.dll

CheckAllProcedures() returned: 2

|||omg!!! this issue has been such a pain since im planning to use sql server express to advance my DB and programming skills (from access+vba to sql+c++,#).
turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb

Problem installing SQL Express

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 the run SQL

Server 2005 Setup again.

Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435

Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07

is not compatible with current builds of SQL Server.Expected at least

version: 9.00.1399.00

I used Add/Remove Progs and used the list in the order suggested to

remove all beta versions of VB, SQL, .NET and etc. Nothing is

listed. I do have VB6 PRO. I have looked for directories

and removed all. I have searched for SQLexpress in the registry

and eliminated all I could find. I reinstalled .Net 2.0 and I'm still

finding this problem.

Microsoft SQL Server 2005 Setup beginning at Thu Jun 08 17:37:43 2006

Process ID : 164

c:\90b92fd6a1de42b9ee\setup.exe Version: 2005.90.2047.0

Running: LoadResourcesAction at: 2006/5/8 17:37:43

Complete: LoadResourcesAction at: 2006/5/8 17:37:43, returned true

Running: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43

Loaded DLL:c:\90b92fd6a1de42b9ee\xmlrw.dll Version:2.0.3609.0

Complete: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43, returned true

Running: ValidateWinNTAction at: 2006/5/8 17:37:43

Complete: ValidateWinNTAction at: 2006/5/8 17:37:43, returned true

Running: ValidateMinOSAction at: 2006/5/8 17:37:43

Complete: ValidateMinOSAction at: 2006/5/8 17:37:43, returned true

Running: PerformSCCAction at: 2006/5/8 17:37:43

Complete: PerformSCCAction at: 2006/5/8 17:37:43, returned true

Running: ActivateLoggingAction at: 2006/5/8 17:37:43

Complete: ActivateLoggingAction at: 2006/5/8 17:37:43, 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__164" returned false.

Running: PerformSCCAction2 at: 2006/5/8 17:37:43

Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435

Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07

is not compatible with current builds of SQL Server.Expected at least

version: 9.00.1399.00

The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"

Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07

is not compatible with current builds of SQL Server.Expected at least

version: 9.00.1399.00

The Product Name is "Microsoft SQL Server 2005 Tools 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
Thank you for your assistance.

Hi Gary,

If you can't find the product listed in the Add/Remove Program listing (they would be listed under Microsoft SQL Server 2005), then you can try manually removing the offending products using the Product ID. The two problem commonents are identified as

Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"

You can manually remove them by typing the following into the Run dialog:

msiexec /x <product id>

Where <product id> is the GUID referenced from your log file.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

|||

I am having a similar problem.

Microsoft SQL Server 2005 Setup beginning at Thu Aug 10 14:33:57 2006
Process ID : 1604
d:\51b5dbc1449baa0bbd43\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/7/10 14:33:57
Complete: LoadResourcesAction at: 2006/7/10 14:33:57, returned true
Running: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57
Loaded DLL:d:\51b5dbc1449baa0bbd43\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57, returned true
Running: ValidateWinNTAction at: 2006/7/10 14:33:57
Complete: ValidateWinNTAction at: 2006/7/10 14:33:57, returned true
Running: ValidateMinOSAction at: 2006/7/10 14:33:57
Complete: ValidateMinOSAction at: 2006/7/10 14:33:57, returned true
Running: PerformSCCAction at: 2006/7/10 14:33:57
Complete: PerformSCCAction at: 2006/7/10 14:33:57, returned true
Running: ActivateLoggingAction at: 2006/7/10 14:33:57
Complete: ActivateLoggingAction at: 2006/7/10 14:33:57, 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__1604" returned false.
Running: PerformSCCAction2 at: 2006/7/10 14:33:58
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools 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.

there are no items in add/remove programs.

when i attempt to run

msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD

i recieve an error message

"this instilation package could not be opened. verify

that the package exists and that you can access it, or

contact the application vendoe to verify that this is a

valid windows installer package"

any one help me?

thanks

Drance

|||

lost my post can not be bothered to re type it

|||

Me too.

We had the CTP version installed. Now it finds various CTP "Products" even though I removed the CTP versions using Add-Remove Programs.

Of course, if these things were vital to my operation, the slightest breeze would erase them forever.

Good Luck,

Mike

|||

Drance wrote:

I am having a similar problem.

...

Class not registered.

there are no items in add/remove programs.

when i attempt to run

msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD

i recieve an error message

"any one help me?

thanks

Drance

Try:

msiexec /x "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}"

|||

I have a problem that when I try to uninstall the offending package I get this Error Message:

The setup has encountered an unexpected error in datastore. The action is SetInstanceProperty. The Error is

:Failed to read property "InstallIds" {"MachineConfiguration".""."SAM"} from Cache

Unable to write poperty into cache: IsClustered

Unable to write poperty into cache: "IsClustered"

XmlRWError: failure loading xmlrw.dll

CheckAllProcedures() returned: 2

|||omg!!! this issue has been such a pain since im planning to use sql server express to advance my DB and programming skills (from access+vba to sql+c++,#).
turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb

Problem installing SQL Express

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 the run SQL

Server 2005 Setup again.

Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435

Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07

is not compatible with current builds of SQL Server.Expected at least

version: 9.00.1399.00

I used Add/Remove Progs and used the list in the order suggested to

remove all beta versions of VB, SQL, .NET and etc. Nothing is

listed. I do have VB6 PRO. I have looked for directories

and removed all. I have searched for SQLexpress in the registry

and eliminated all I could find. I reinstalled .Net 2.0 and I'm still

finding this problem.

Microsoft SQL Server 2005 Setup beginning at Thu Jun 08 17:37:43 2006

Process ID : 164

c:\90b92fd6a1de42b9ee\setup.exe Version: 2005.90.2047.0

Running: LoadResourcesAction at: 2006/5/8 17:37:43

Complete: LoadResourcesAction at: 2006/5/8 17:37:43, returned true

Running: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43

Loaded DLL:c:\90b92fd6a1de42b9ee\xmlrw.dll Version:2.0.3609.0

Complete: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43, returned true

Running: ValidateWinNTAction at: 2006/5/8 17:37:43

Complete: ValidateWinNTAction at: 2006/5/8 17:37:43, returned true

Running: ValidateMinOSAction at: 2006/5/8 17:37:43

Complete: ValidateMinOSAction at: 2006/5/8 17:37:43, returned true

Running: PerformSCCAction at: 2006/5/8 17:37:43

Complete: PerformSCCAction at: 2006/5/8 17:37:43, returned true

Running: ActivateLoggingAction at: 2006/5/8 17:37:43

Complete: ActivateLoggingAction at: 2006/5/8 17:37:43, 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__164" returned false.

Running: PerformSCCAction2 at: 2006/5/8 17:37:43

Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435

Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07

is not compatible with current builds of SQL Server.Expected at least

version: 9.00.1399.00

The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"

Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07

is not compatible with current builds of SQL Server.Expected at least

version: 9.00.1399.00

The Product Name is "Microsoft SQL Server 2005 Tools 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
Thank you for your assistance.

Hi Gary,

If you can't find the product listed in the Add/Remove Program listing (they would be listed under Microsoft SQL Server 2005), then you can try manually removing the offending products using the Product ID. The two problem commonents are identified as

Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"

You can manually remove them by typing the following into the Run dialog:

msiexec /x <product id>

Where <product id> is the GUID referenced from your log file.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

|||

I am having a similar problem.

Microsoft SQL Server 2005 Setup beginning at Thu Aug 10 14:33:57 2006
Process ID : 1604
d:\51b5dbc1449baa0bbd43\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/7/10 14:33:57
Complete: LoadResourcesAction at: 2006/7/10 14:33:57, returned true
Running: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57
Loaded DLL:d:\51b5dbc1449baa0bbd43\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57, returned true
Running: ValidateWinNTAction at: 2006/7/10 14:33:57
Complete: ValidateWinNTAction at: 2006/7/10 14:33:57, returned true
Running: ValidateMinOSAction at: 2006/7/10 14:33:57
Complete: ValidateMinOSAction at: 2006/7/10 14:33:57, returned true
Running: PerformSCCAction at: 2006/7/10 14:33:57
Complete: PerformSCCAction at: 2006/7/10 14:33:57, returned true
Running: ActivateLoggingAction at: 2006/7/10 14:33:57
Complete: ActivateLoggingAction at: 2006/7/10 14:33:57, 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__1604" returned false.
Running: PerformSCCAction2 at: 2006/7/10 14:33:58
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools 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.

there are no items in add/remove programs.

when i attempt to run

msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD

i recieve an error message

"this instilation package could not be opened. verify

that the package exists and that you can access it, or

contact the application vendoe to verify that this is a

valid windows installer package"

any one help me?

thanks

Drance

|||

lost my post can not be bothered to re type it

|||

Me too.

We had the CTP version installed. Now it finds various CTP "Products" even though I removed the CTP versions using Add-Remove Programs.

Of course, if these things were vital to my operation, the slightest breeze would erase them forever.

Good Luck,

Mike

|||

Drance wrote:

I am having a similar problem.

...

Class not registered.

there are no items in add/remove programs.

when i attempt to run

msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD

i recieve an error message

"any one help me?

thanks

Drance

Try:

msiexec /x "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}"

|||

I have a problem that when I try to uninstall the offending package I get this Error Message:

The setup has encountered an unexpected error in datastore. The action is SetInstanceProperty. The Error is

:Failed to read property "InstallIds" {"MachineConfiguration".""."SAM"} from Cache

Unable to write poperty into cache: IsClustered

Unable to write poperty into cache: "IsClustered"

XmlRWError: failure loading xmlrw.dll

CheckAllProcedures() returned: 2

|||omg!!! this issue has been such a pain since im planning to use sql server express to advance my DB and programming skills (from access+vba to sql+c++,#).
turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb

Problem installing SQL Express

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 the run SQL Server 2005 Setup again.
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
I used Add/Remove Progs and used the list in the order suggested to remove all beta versions of VB, SQL, .NET and etc. Nothing is listed. I do have VB6 PRO. I have looked for directories and removed all. I have searched for SQLexpress in the registry and eliminated all I could find. I reinstalled .Net 2.0 and I'm still finding this problem.
Microsoft SQL Server 2005 Setup beginning at Thu Jun 08 17:37:43 2006
Process ID : 164
c:\90b92fd6a1de42b9ee\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/5/8 17:37:43
Complete: LoadResourcesAction at: 2006/5/8 17:37:43, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43
Loaded DLL:c:\90b92fd6a1de42b9ee\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43, returned true
Running: ValidateWinNTAction at: 2006/5/8 17:37:43
Complete: ValidateWinNTAction at: 2006/5/8 17:37:43, returned true
Running: ValidateMinOSAction at: 2006/5/8 17:37:43
Complete: ValidateMinOSAction at: 2006/5/8 17:37:43, returned true
Running: PerformSCCAction at: 2006/5/8 17:37:43
Complete: PerformSCCAction at: 2006/5/8 17:37:43, returned true
Running: ActivateLoggingAction at: 2006/5/8 17:37:43
Complete: ActivateLoggingAction at: 2006/5/8 17:37:43, 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__164" returned false.
Running: PerformSCCAction2 at: 2006/5/8 17:37:43
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools 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

Thank you for your assistance.

Hi Gary,

If you can't find the product listed in the Add/Remove Program listing (they would be listed under Microsoft SQL Server 2005), then you can try manually removing the offending products using the Product ID. The two problem commonents are identified as

Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"

You can manually remove them by typing the following into the Run dialog:

msiexec /x <product id>

Where <product id> is the GUID referenced from your log file.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

|||

I am having a similar problem.

Microsoft SQL Server 2005 Setup beginning at Thu Aug 10 14:33:57 2006
Process ID : 1604
d:\51b5dbc1449baa0bbd43\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/7/10 14:33:57
Complete: LoadResourcesAction at: 2006/7/10 14:33:57, returned true
Running: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57
Loaded DLL:d:\51b5dbc1449baa0bbd43\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57, returned true
Running: ValidateWinNTAction at: 2006/7/10 14:33:57
Complete: ValidateWinNTAction at: 2006/7/10 14:33:57, returned true
Running: ValidateMinOSAction at: 2006/7/10 14:33:57
Complete: ValidateMinOSAction at: 2006/7/10 14:33:57, returned true
Running: PerformSCCAction at: 2006/7/10 14:33:57
Complete: PerformSCCAction at: 2006/7/10 14:33:57, returned true
Running: ActivateLoggingAction at: 2006/7/10 14:33:57
Complete: ActivateLoggingAction at: 2006/7/10 14:33:57, 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__1604" returned false.
Running: PerformSCCAction2 at: 2006/7/10 14:33:58
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools 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.

there are no items in add/remove programs.

when i attempt to run

msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD

i recieve an error message

"this instilation package could not be opened. verify

that the package exists and that you can access it, or

contact the application vendoe to verify that this is a

valid windows installer package"

any one help me?

thanks

Drance

|||

lost my post can not be bothered to re type it

|||

Me too.

We had the CTP version installed. Now it finds various CTP "Products" even though I removed the CTP versions using Add-Remove Programs.

Of course, if these things were vital to my operation, the slightest breeze would erase them forever.

Good Luck,

Mike

|||

Drance wrote:

I am having a similar problem.

...

Class not registered.

there are no items in add/remove programs.

when i attempt to run

msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD

i recieve an error message

"any one help me?

thanks

Drance

Try:

msiexec /x "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}"

|||

I have a problem that when I try to uninstall the offending package I get this Error Message:

The setup has encountered an unexpected error in datastore. The action is SetInstanceProperty. The Error is

:Failed to read property "InstallIds" {"MachineConfiguration".""."SAM"} from Cache

Unable to write poperty into cache: IsClustered

Unable to write poperty into cache: "IsClustered"

XmlRWError: failure loading xmlrw.dll

CheckAllProcedures() returned: 2

|||omg!!! this issue has been such a pain since im planning to use sql server express to advance my DB and programming skills (from access+vba to sql+c++,#).
turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb

Problem installing SQL Express

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 the run SQL Server 2005 Setup again.
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
I used Add/Remove Progs and used the list in the order suggested to remove all beta versions of VB, SQL, .NET and etc. Nothing is listed. I do have VB6 PRO. I have looked for directories and removed all. I have searched for SQLexpress in the registry and eliminated all I could find. I reinstalled .Net 2.0 and I'm still finding this problem.
Microsoft SQL Server 2005 Setup beginning at Thu Jun 08 17:37:43 2006
Process ID : 164
c:\90b92fd6a1de42b9ee\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/5/8 17:37:43
Complete: LoadResourcesAction at: 2006/5/8 17:37:43, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43
Loaded DLL:c:\90b92fd6a1de42b9ee\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43, returned true
Running: ValidateWinNTAction at: 2006/5/8 17:37:43
Complete: ValidateWinNTAction at: 2006/5/8 17:37:43, returned true
Running: ValidateMinOSAction at: 2006/5/8 17:37:43
Complete: ValidateMinOSAction at: 2006/5/8 17:37:43, returned true
Running: PerformSCCAction at: 2006/5/8 17:37:43
Complete: PerformSCCAction at: 2006/5/8 17:37:43, returned true
Running: ActivateLoggingAction at: 2006/5/8 17:37:43
Complete: ActivateLoggingAction at: 2006/5/8 17:37:43, 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__164" returned false.
Running: PerformSCCAction2 at: 2006/5/8 17:37:43
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools 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

Thank you for your assistance.

Hi Gary,

If you can't find the product listed in the Add/Remove Program listing (they would be listed under Microsoft SQL Server 2005), then you can try manually removing the offending products using the Product ID. The two problem commonents are identified as

Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"

You can manually remove them by typing the following into the Run dialog:

msiexec /x <product id>

Where <product id> is the GUID referenced from your log file.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

|||

I am having a similar problem.

Microsoft SQL Server 2005 Setup beginning at Thu Aug 10 14:33:57 2006
Process ID : 1604
d:\51b5dbc1449baa0bbd43\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/7/10 14:33:57
Complete: LoadResourcesAction at: 2006/7/10 14:33:57, returned true
Running: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57
Loaded DLL:d:\51b5dbc1449baa0bbd43\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57, returned true
Running: ValidateWinNTAction at: 2006/7/10 14:33:57
Complete: ValidateWinNTAction at: 2006/7/10 14:33:57, returned true
Running: ValidateMinOSAction at: 2006/7/10 14:33:57
Complete: ValidateMinOSAction at: 2006/7/10 14:33:57, returned true
Running: PerformSCCAction at: 2006/7/10 14:33:57
Complete: PerformSCCAction at: 2006/7/10 14:33:57, returned true
Running: ActivateLoggingAction at: 2006/7/10 14:33:57
Complete: ActivateLoggingAction at: 2006/7/10 14:33:57, 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__1604" returned false.
Running: PerformSCCAction2 at: 2006/7/10 14:33:58
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools 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.

there are no items in add/remove programs.

when i attempt to run

msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD

i recieve an error message

"this instilation package could not be opened. verify

that the package exists and that you can access it, or

contact the application vendoe to verify that this is a

valid windows installer package"

any one help me?

thanks

Drance

|||

lost my post can not be bothered to re type it

|||

Me too.

We had the CTP version installed. Now it finds various CTP "Products" even though I removed the CTP versions using Add-Remove Programs.

Of course, if these things were vital to my operation, the slightest breeze would erase them forever.

Good Luck,

Mike

|||

Drance wrote:

I am having a similar problem.

...

Class not registered.

there are no items in add/remove programs.

when i attempt to run

msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD

i recieve an error message

"any one help me?

thanks

Drance

Try:

msiexec /x "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}"

|||

I have a problem that when I try to uninstall the offending package I get this Error Message:

The setup has encountered an unexpected error in datastore. The action is SetInstanceProperty. The Error is

:Failed to read property "InstallIds" {"MachineConfiguration".""."SAM"} from Cache

Unable to write poperty into cache: IsClustered

Unable to write poperty into cache: "IsClustered"

XmlRWError: failure loading xmlrw.dll

CheckAllProcedures() returned: 2

|||omg!!! this issue has been such a pain since im planning to use sql server express to advance my DB and programming skills (from access+vba to sql+c++,#).
turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb

Problem inserting into SQL database

I am using visual devloper express, and i have been following allow in the "starter videos". for lesson 8, the example worked fine, but when i try to replicate the example with a SQL database (external one) when I am configuring the formView, and i try to click the advanced tab under 'Advanced SQL Generation Options", I do not have the abilty to check the 2 boxes for generate insert, update, delete statements, etc (they are greyed out).

i have an asp page that has the same connection as this page and i am able to insert a record, so i am sure it's not a permission thing...

I don't understand what I am doing wrong here... a plain old asp coded page inserts records into this table in the same database, but I am unable to check the boxes for "generate insert" etrc, and the error I get on the page itself is

Inserting is not supported by data source 'SqlDataSource1' unless InsertCommand is specified.

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.NotSupportedException: Inserting is not supported by data source 'SqlDataSource1' unless InsertCommand is specified.

Hi,

According to your question, you say that you don't have the abilty to check the 2 boxes for generate insert,update,delete statements.(they are greyed out). There are two reasons:

1. Be sure that there's primary key field in your data table because you must have all primary key fields selected for this option to be enabled.

2. Be sure that the data table you selected is not read-only. (Note: Sample tables just like Northwind,pubs and etc. are read-only.)

Hope it helps.

Thanks.

Problem in Visual Basic

When I run Visual Basic Application With Back hand Is SQL SERVER DataBAse I Had Connect database with ODBC
But its very Slow What can i do
As there are many ways of doing the same thing, I would recommend that you
encapsulate your data manipulation language into a stored procedure and
make calls to that SP through your VB application. In programming, I can
assure you that short cuts kill the performance.
You can always embed the manipulation language in your VB code itself, but
to enhance performance, the recommended way (from experience) would be to
do so through Stored Procedures. However, this is not a generic statement
but should be evaluated in the light of your own application's
architecture. Have a look at this great article
http://www.sql-server-performance.co...erformance.asp
Kindly review it and analyse the same with respect to your application and
database design.
Hope this helps.
Sanchan [MSFT]
sanchans@.online.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.