Cannot registering external assembly - System.EnterpriseServices.dll

Hi,

I'm trying to register assembly System.EnterpriseServices.dll. I registred several assemblies, that are referenced:
System.DirectoryServices.dll
System.DirectoryServices.Protocolls.dll
System.Drawing.dll

But then, I found a problem:
While registring System.EnterpriseServices.dll I recieve error message with requirement for registration System.Runtime.Remoting.
While registring System.Runtime.Remoting.dll I recieve error message with requirement for registration System.Web.
An finally, when i try to register System.Web, I recieve message requiring registration of System.EnterpriseServices:

Create failed for SqlAssembly 'System.Web'. (Microsoft.SqlServer.Smo)

Assembly 'system.enterpriseservices, version=2.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a.' was not found in the SQL catalog.
Warning: The Microsoft .Net frameworks assembly 'system.web, version=2.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=x86.' you are registering is not fully tested in SQL Server hosted environment. (Microsoft SQL Server, Error: 6503)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1314&EvtSrc=MSSQLServer&EvtID=6503&LinkId=20476

All assemblies were loaded from the same folder c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\*.dll
Version of sqlServer 9.00.1314.06

Thanks

This should work if you from SQL Server Management Studio execute the CREATE ASSEMBLY statement against where the dll is originally located:

create assembly entService
from 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.EnterpriseServices.dll'
with permission_set = UNSAFE

When doing it that way, SQL Server is smart enough to work around the various circular references.

Niels
sql

cannot P/Invoke SQLCEME30.DLL when debugging Pocket PC 2003 SE Emulator

I'm trying to debug an assembly with System.Data.SqlServerCe - and when I deploy to a IPAQ 2210 - I get no errors! Alas, when I try to debug using the Pocket PC 2003 SE Emulator - I get the "cannot P/Invoke SQLCEME30.DLL" exception.

Can anyone offer directions?

best regards,
Walther

wDiechmann wrote:

I'm trying to debug an assembly with System.Data.SqlServerCe - and when I deploy to a IPAQ 2210 - I get no errors! Alas, when I try to debug using the Pocket PC 2003 SE Emulator - I get the "cannot P/Invoke SQLCEME30.DLL" exception.

Can anyone offer directions?

best regards,
Walther

I tried with a SmallTestProject having nothing except statements to create new "test.sdf" and my take on this is: you cannot debug solutions for smart devices aka Pocket PC 2003 in VS2005, if you want to use the emulator!

Please someone prove me wrong!

a nice weekend from sunny Denmark,
Walther|||

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=604751&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=438553&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=220816&SiteID=1

|||So are you meant to install the SQLMobile CAB file on the emulator? How will it know that you unstalled the CAB file the last time you loaded up the emulator?

I don't undertstand this.|||

I'm not sure what exactly you do not understand.

You copy the CAB, you click on it - it's now installed. If you save emulator state, it would remain installed. If you don't save the emulator's state - it's all gone on restart, repeat the installation every time emulator is started (or save state).

|||Ahh, right, get you now :)

I didn't know the Emulator state saved things like that (installation of things) :)

I'm guessing that each device model/version has its own emulator state?|||Ilya Tumanov,

I'm afraid I do not see where you're taking me on this!

I debug my apps perfectly allright on the device - but I'm not able to debug apps using the emulator (where no device is involved - just my desktop)

The links you threw my way all talk about copying CABs to the device - but I'm not debugging on the device. I'm debugging on the emulator!?

Sorry if my english is not fluently enough to present my case properly :(

best regards,
Walther|||OK, Walther, judging by what Ilya as stated, you need to install the SQL CAB's onto the Emulator.

To do this, in VS 2005 go to 'Tools'->'Device Emulator Manager', then in the available Emulators select the Emulator you need then go to 'Actions'->'Connect' (wait for Green tick next to Emulator). Then in the Emulator Window go to 'File'->'Configure', then under the 'General' tab in the 'Shared Folder', click the '...' button. Locate to the Bin/debug directory of your application, and ok that. In this directory you should have placed your SQL CAB files.

Now in the Emulator, click 'Start'->'Programs'->'File Explorer'->'My Device'->'Storage Card' - in here should be your CAB files, click on them to install them. Remember to save the Emulator state.

Ilya, is this the correct way of doing it, or is there an easier way?

Thanks
|||

Normally VS 2005 would install NETCF and SQL Mobile automatically as soon as you hit F5. If for some reason that does not work, then installation via mapped folder should work.

As device vs. emulator, there's no difference in this case. You see, emulator is a device, only simulated. You can even Active Sync it if you want in copy files via AS just like you would do with physical device.

cannot P/Invoke SQLCEME30.DLL when debugging Pocket PC 2003 SE Emulator

I'm trying to debug an assembly with System.Data.SqlServerCe - and when I deploy to a IPAQ 2210 - I get no errors! Alas, when I try to debug using the Pocket PC 2003 SE Emulator - I get the "cannot P/Invoke SQLCEME30.DLL" exception.

Can anyone offer directions?

best regards,
Walther

wDiechmann wrote:

I'm trying to debug an assembly with System.Data.SqlServerCe - and when I deploy to a IPAQ 2210 - I get no errors! Alas, when I try to debug using the Pocket PC 2003 SE Emulator - I get the "cannot P/Invoke SQLCEME30.DLL" exception.

Can anyone offer directions?

best regards,
Walther

I tried with a SmallTestProject havingnothing except statements to create new "test.sdf" and my take on this is: you cannot debug solutions for smart devices aka Pocket PC 2003 in VS2005, if you want to use the emulator!

Please someone prove me wrong!

a nice weekend from sunny Denmark,
Walther
|||

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=604751&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=438553&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=220816&SiteID=1

|||So are you meant to install the SQLMobile CAB file on the emulator? How will it know that you unstalled the CAB file the last time you loaded up the emulator?

I don't undertstand this.|||

I'm not sure what exactly you do not understand.

You copy the CAB, you click on it - it's now installed. If you save emulator state, it would remain installed. If you don't save the emulator's state - it's all gone on restart, repeat the installation every time emulator is started (or save state).

|||Ahh, right, get you now :)

I didn't know the Emulator state saved things like that (installation of things) :)

I'm guessing that each device model/version has its own emulator state?|||Ilya Tumanov,

I'm afraid I do not see where you're taking me on this!

I debug my apps perfectly allright on the device - but I'm not able to debug apps using the emulator (where no device is involved - just my desktop)

The links you threw my way all talk about copying CABs to the device - but I'm not debugging on the device. I'm debugging on the emulator!?

Sorry if my english is not fluently enough to present my case properly :(

best regards,
Walther
|||OK, Walther, judging by whatIlya as stated, you need to install the SQL CAB's onto the Emulator.

To do this, in VS 2005 go to 'Tools'->'Device Emulator Manager', then in the available Emulators select the Emulator you need then go to 'Actions'->'Connect' (wait for Green tick next to Emulator). Then in the Emulator Window go to 'File'->'Configure', then under the 'General' tab in the 'Shared Folder', click the '...' button. Locate to the Bin/debug directory of your application, and ok that. In this directory you should have placed your SQL CAB files.

Now in the Emulator, click 'Start'->'Programs'->'File Explorer'->'My Device'->'Storage Card' - in here should be your CAB files, click on them to install them. Remember to save the Emulator state.

Ilya, is this the correct way of doing it, or is there an easier way?

Thanks
|||

Normally VS 2005 would install NETCF and SQL Mobile automatically as soon as you hit F5. If for some reason that does not work, then installation via mapped folder should work.

As device vs. emulator, there's no difference in this case. You see, emulator is a device, only simulated. You can even Active Sync it if you want in copy files via AS just like you would do with physical device.

Cannot open user default database. Login failed.

Hi,

I got this application system having SQLExpress as database (ABCSystem.mdf). I'm connecting to the database thru connection string specifying database path in App.config.

At the same time, I got two paths for the mdf files. The first one is the path for my database project while the second one is the path to conduct testing. (This means that I got identical ABCSystem.mdf in two paths)

1) C:\Program Files\Company ABC\ABCDatabaseProject\

2) C:\Program Files\Company ABC Limited\ABCSystem\Database\

In my development machine, I can run my application where database path is testing path (number 2).

When I tried to copy the ABCSystem.mdf and ABCSystem_log.LDF and my application program files to another PC to test, I got the subject error message. (note that I copy program files under directory "C:\Program Files\Company ABC Limited\ABCSystem\" and mdf files under "C:\Program Files\Company ABC Limited\ABCSystem\Database\")

I try to edit path from database testing path to database project path in app.config, run the application, and notice that it is running OK.

What seems to cause the problem? Coz I need the database in the testing path which is "C:\Program Files\Company ABC Limited\ABCSystem\Database\" AND NOT "C:\Program Files\Company ABC\ABCDatabaseProject\".

Thanks alot for your kind attention.

Try this first, and then check your string accordingly:

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

Buck Woody

|||I'm having this identical issue with an ODBC connection.
After wasting hours, I realized I only get the error when I try to change database name. (e.g. from a development to a production server). Based upon everything I've tried, I determined you CANNOT change server name in a Crystal report programmatically as in the Crystal sample code. It may be a possible to change servers if using a command based report (explicit SQL query), but our reports all use tables so a trial would be irrelevant.

Cannot open user default database. Login failed.

Hi,

I got this application system having SQLExpress as database (ABCSystem.mdf). I'm connecting to the database thru connection string specifying database path in App.config.

At the same time, I got two paths for the mdf files. The first one is the path for my database project while the second one is the path to conduct testing. (This means that I got identical ABCSystem.mdf in two paths)

1) C:\Program Files\Company ABC\ABCDatabaseProject\

2) C:\Program Files\Company ABC Limited\ABCSystem\Database\

In my development machine, I can run my application where database path is testing path (number 2).

When I tried to copy the ABCSystem.mdf and ABCSystem_log.LDF and my application program files to another PC to test, I got the subject error message. (note that I copy program files under directory "C:\Program Files\Company ABC Limited\ABCSystem\" and mdf files under "C:\Program Files\Company ABC Limited\ABCSystem\Database\")

I try to edit path from database testing path to database project path in app.config, run the application, and notice that it is running OK.

What seems to cause the problem? Coz I need the database in the testing path which is "C:\Program Files\Company ABC Limited\ABCSystem\Database\" AND NOT "C:\Program Files\Company ABC\ABCDatabaseProject\".

Thanks alot for your kind attention.

Try this first, and then check your string accordingly:

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

Buck Woody

|||I'm having this identical issue with an ODBC connection.
After wasting hours, I realized I only get the error when I try to change database name. (e.g. from a development to a production server). Based upon everything I've tried, I determined you CANNOT change server name in a Crystal report programmatically as in the Crystal sample code. It may be a possible to change servers if using a command based report (explicit SQL query), but our reports all use tables so a trial would be irrelevant.

Cannot move quorum after disk replacement

We actually replaced the controller card on one of our clustered
servers (was the system controller not SAN controller). Ever since
then we have been getting these two errors when I try to move the SQL
group to that node. These are the only errors we are getting...
All records are there in DNS (forward and reverse).
Event Type: Warning
Event Source: ClusSvc
Event Category: Network Name Resource
Event ID: 1119
Date: 11/3/2007
Time: 11:11:55 AM
User: N/A
Computer: DB
Description:
The registration of DNS name sql.xxxxxxx.local for resource 'SQL
Network Name (SQL)' over adapter 'Local Area Connection' failed for
the following reason:
DNS bad key.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 39 23 00 00 9#..
Event Type: Warning
Event Source: ClusSvc
Event Category: Network Name Resource
Event ID: 1119
Date: 11/3/2007
Time: 11:11:55 AM
User: N/A
Computer: DB
Description:
The registration of DNS name cluster.xxxxxx.local for resource
'Cluster Name' over adapter 'Local Area Connection' failed for the
following reason:
DNS bad key.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 39 23 00 00 9#..
Try this:
http://support.microsoft.com/kb/871111
Regards,
John
Visit my blog: http://msmvps.com/blogs/jtoner
"Kat99" <katrina.allsup@.gmail.com> wrote in message
news:1194106983.471543.188530@.o38g2000hse.googlegr oups.com...
> We actually replaced the controller card on one of our clustered
> servers (was the system controller not SAN controller). Ever since
> then we have been getting these two errors when I try to move the SQL
> group to that node. These are the only errors we are getting...
> All records are there in DNS (forward and reverse).
> Event Type: Warning
> Event Source: ClusSvc
> Event Category: Network Name Resource
> Event ID: 1119
> Date: 11/3/2007
> Time: 11:11:55 AM
> User: N/A
> Computer: DB
> Description:
> The registration of DNS name sql.xxxxxxx.local for resource 'SQL
> Network Name (SQL)' over adapter 'Local Area Connection' failed for
> the following reason:
> DNS bad key.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 39 23 00 00 9#..
>
> Event Type: Warning
> Event Source: ClusSvc
> Event Category: Network Name Resource
> Event ID: 1119
> Date: 11/3/2007
> Time: 11:11:55 AM
> User: N/A
> Computer: DB
> Description:
> The registration of DNS name cluster.xxxxxx.local for resource
> 'Cluster Name' over adapter 'Local Area Connection' failed for the
> following reason:
> DNS bad key.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 39 23 00 00 9#..
>

Cannot install SQL Server Express

I'm attempting an new installation on an Athlon 64 3300 system running XP Pro using the default install options. Get the message "SQL Server service failed to start..." and the installer starts Rolling Back the installation leaving me with a bunch of log files that mean nothing to me.

I'm not savvy enough to solve this one. Can anyone help?

Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Thu Oct 19 20:09:10 2006
Machine : SR1365CL
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.2047.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_SR1365CL_SQLSupport_1.log
--
Machine : SR1365CL
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_SR1365CL_SQLNCLI_1.log
--
Machine : SR1365CL
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.2047.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_SR1365CL_SqlWriter_1.log
--
Machine : SR1365CL
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_SR1365CL_MSXML6_1.log
--
Machine : SR1365CL
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
--
Machine : SR1365CL
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.1.2047.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_SR1365CL_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.
Error Number : 29503
--

What does the event log tell you ? There should be an entry about the starting service. There might be permission or service account problem.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

My ERRORLOG shows this error:

2006-10-19 20:14:59.51 spid5s Starting up database 'mssqlsystemresource'.
2006-10-19 20:14:59.51 spid5s The resource database build version is 9.00.2047. This is an informational message only. No user action is required.
2006-10-19 20:14:59.65 spid5s Error: 15209, Severity: 16, State: 1.
2006-10-19 20:14:59.65 spid5s An error occurred during encryption.

This KB article gave me the information necessary to complete the install although the .\Protect folder did not yet exist.

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B920114

Problem solved. Thanks for the nudge in the right direction, Jens.

John

|||

I also found this thread VERY helpful, and I would just like to add two comments:

1) This applies to intel 32bit processors as well.

2) When you attempt to check the security tab for folder C:\Documents and Settings\NetworkService\Application Data\Microsoft\Protect, you may notice that there is no security tab. In that case you are using "simple file sharing", which will need to be disabled. Disable by: control panel-> folder options->view and uncheck "use simple file sharing (Recommended)" at bottom. Then, follow KB920114.

Jim

|||I am getting exactly the same error as above. I followed the directions in KB920114, but the Network Service already had full authority. So there is nothing for me to change. Needless to say, it doesn't work. Any other ideas?

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 Server Express

I'm attempting an new installation on an Athlon 64 3300 system running XP Pro using the default install options. Get the message "SQL Server service failed to start..." and the installer starts Rolling Back the installation leaving me with a bunch of log files that mean nothing to me.

I'm not savvy enough to solve this one. Can anyone help?

Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Thu Oct 19 20:09:10 2006
Machine : SR1365CL
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.2047.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_SR1365CL_SQLSupport_1.log
--
Machine : SR1365CL
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_SR1365CL_SQLNCLI_1.log
--
Machine : SR1365CL
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.2047.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_SR1365CL_SqlWriter_1.log
--
Machine : SR1365CL
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_SR1365CL_MSXML6_1.log
--
Machine : SR1365CL
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
--
Machine : SR1365CL
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.1.2047.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_SR1365CL_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.
Error Number : 29503
--

What does the event log tell you ? There should be an entry about the starting service. There might be permission or service account problem.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

My ERRORLOG shows this error:

2006-10-19 20:14:59.51 spid5s Starting up database 'mssqlsystemresource'.
2006-10-19 20:14:59.51 spid5s The resource database build version is 9.00.2047. This is an informational message only. No user action is required.
2006-10-19 20:14:59.65 spid5s Error: 15209, Severity: 16, State: 1.
2006-10-19 20:14:59.65 spid5s An error occurred during encryption.

This KB article gave me the information necessary to complete the install although the .\Protect folder did not yet exist.

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B920114

Problem solved. Thanks for the nudge in the right direction, Jens.

John

|||

I also found this thread VERY helpful, and I would just like to add two comments:

1) This applies to intel 32bit processors as well.

2) When you attempt to check the security tab for folder C:\Documents and Settings\NetworkService\Application Data\Microsoft\Protect, you may notice that there is no security tab. In that case you are using "simple file sharing", which will need to be disabled. Disable by: control panel-> folder options->view and uncheck "use simple file sharing (Recommended)" at bottom. Then, follow KB920114.

Jim

|||I am getting exactly the same error as above. I followed the directions in KB920114, but the Network Service already had full authority. So there is nothing for me to change. Needless to say, it doesn't work. Any other ideas?

Cannot insert duplicate key row in object MSmerge_tombstone

MSMerge_tombstone is a System Table used for Replication
information. It would appear as though you arent getting
rid of Replication totally after the first time you run
it. Are you dropping the Publication after the first run?

>--Original Message--
>I am working with a VB.Net Windows app that creates a
>publication/subscription on the fly. Essentially, it
takes a database backup
>in a zip file, unzips it, restores the database to the
same server as the
>other database in the setup, creates a publication to the
first database,
>then a subscription from the first database to the new
one, and attempts to
>run it.
>The first time this runs, on a fresh setup of all
databases involved, the
>process works fine. On subsequent runs, however, when we
get to the data
>synchronization part, the following error message comes
up in the agent's
>session detail:
>The schema script \\ROSTERDEV\C$\Program Files\Microsoft
SQL
>Server\MSSQL\ReplData\unc\ROSTERDEV_Case_mgt_HQ_c ase_mgt_H
Q\20040924000502\O
>ffice_78.sch could not be propagated to the subscriber.
>(Source: Merge Replication Provider (Agent); Error
number: -2147201001)
>----
--
>--
>Cannot insert duplicate key row in object
MSmerge_tombstone with unique
>index uc1MSmerge_tombstone.
>(Source: ROSTERDEV (Data source); Error number: 2601)
>----
--
>--
>The schema script file might be different, but the
message itself is the
>same. We're currently testing, so the exact same zip file
is getting reused
>on both first and subsequent attempts. I wouldn't think
this would cause a
>data conflict, but it appears to be.
>Any assistance would be welcome. Thanks.
>--
>Kenneth S. McAndrew
>Software Developer, Information Concepts
>kmcandrew@.infoconcepts.com
>
>.
>
The pull subscription, publication, and database published from are all
being removed, in that order, by the vb.net code. I don't see any left-over
tendrils.
Kenneth S. McAndrew
Software Developer, Information Concepts
kmcandrew@.infoconcepts.com
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:239d01c4a241$308282d0$a401280a@.phx.gbl...[vbcol=seagreen]
> MSMerge_tombstone is a System Table used for Replication
> information. It would appear as though you arent getting
> rid of Replication totally after the first time you run
> it. Are you dropping the Publication after the first run?
>
> takes a database backup
> same server as the
> first database,
> one, and attempts to
> databases involved, the
> get to the data
> up in the agent's
> SQL
> Q\20040924000502\O
> number: -2147201001)
> --
> MSmerge_tombstone with unique
> --
> message itself is the
> is getting reused
> this would cause a

Cannot insert duplicate key into ...... EXTREME problem

Hi All
Really need your urgent help on this!
Created a system that uses an SQL database as the data store. Clients have
been using this same DDL since SQL 6.5 and I've got lots of users running
SQL 6.5, 7, 2000 and MSDE with the same DDL and they don't have a problem.
However, one user, who has been running the system on SQL 6.5 for years now,
keeps getting cannot insert duplicate key into PK_ blah blah. This error is
being generated on SQL 6.5's own auto-generated ID so I'm sure it is a
problem that their SQL 6.5 has created in the db. The problem is after
running the usual CHECKDB, CHECKALLOC, NEWALLOC, CHECKTABLE and UPDATEUSAGE
DBCC commands none of these have corrected the fault.
I'm sure I've had this problem crop up once before and doing the CHECKDB
fixed it, but I've run the CHECKDB 3 times now and it doesn't correct it.
Can you give me any pointers on how I can check and more importantly resolve
this issue?
Thanks Robbie
I cannot remember. Is DBCC CHECKIDENT included with 6.5? If it is try using
it.
Keith
"Astra" <info@.noemail.com> wrote in message
news:OQdxVA1GFHA.3128@.TK2MSFTNGP10.phx.gbl...
> Hi All
> Really need your urgent help on this!
> Created a system that uses an SQL database as the data store. Clients
have
> been using this same DDL since SQL 6.5 and I've got lots of users running
> SQL 6.5, 7, 2000 and MSDE with the same DDL and they don't have a problem.
> However, one user, who has been running the system on SQL 6.5 for years
now,
> keeps getting cannot insert duplicate key into PK_ blah blah. This error
is
> being generated on SQL 6.5's own auto-generated ID so I'm sure it is a
> problem that their SQL 6.5 has created in the db. The problem is after
> running the usual CHECKDB, CHECKALLOC, NEWALLOC, CHECKTABLE and
UPDATEUSAGE
> DBCC commands none of these have corrected the fault.
> I'm sure I've had this problem crop up once before and doing the CHECKDB
> fixed it, but I've run the CHECKDB 3 times now and it doesn't correct it.
> Can you give me any pointers on how I can check and more importantly
resolve
> this issue?
> Thanks Robbie
>
|||Yes, it was.
SQL Server 6.5 has a few issues with Identity columns. Those issues went
away with SQL server 7.0.
DBCC CHECKIDENT
( 'table_name'
[ , { NORESEED
| { RESEED [ , new_reseed_value ] }
}
]
)
Checks the current identity value for the specified table and, if needed,
corrects the identity value.
As an aside, SQL Server 6.5 is no longer supported by Microsoft, so those
clients would be well advised to move to SQL Server 2000.
Regards
Mike
"Keith Kratochvil" wrote:

> I cannot remember. Is DBCC CHECKIDENT included with 6.5? If it is try using
> it.
> --
> Keith
>
> "Astra" <info@.noemail.com> wrote in message
> news:OQdxVA1GFHA.3128@.TK2MSFTNGP10.phx.gbl...
> have
> now,
> is
> UPDATEUSAGE
> resolve
>

Cannot insert duplicate key into ...... EXTREME problem

Hi All
Really need your urgent help on this!
Created a system that uses an SQL database as the data store. Clients have
been using this same DDL since SQL 6.5 and I've got lots of users running
SQL 6.5, 7, 2000 and MSDE with the same DDL and they don't have a problem.
However, one user, who has been running the system on SQL 6.5 for years now,
keeps getting cannot insert duplicate key into PK_ blah blah. This error is
being generated on SQL 6.5's own auto-generated ID so I'm sure it is a
problem that their SQL 6.5 has created in the db. The problem is after
running the usual CHECKDB, CHECKALLOC, NEWALLOC, CHECKTABLE and UPDATEUSAGE
DBCC commands none of these have corrected the fault.
I'm sure I've had this problem crop up once before and doing the CHECKDB
fixed it, but I've run the CHECKDB 3 times now and it doesn't correct it.
Can you give me any pointers on how I can check and more importantly resolve
this issue?
Thanks RobbieI cannot remember. Is DBCC CHECKIDENT included with 6.5? If it is try using
it.
Keith
"Astra" <info@.noemail.com> wrote in message
news:ex1KtA1GFHA.3088@.tk2msftngp13.phx.gbl...
> Hi All
> Really need your urgent help on this!
> Created a system that uses an SQL database as the data store. Clients
have
> been using this same DDL since SQL 6.5 and I've got lots of users running
> SQL 6.5, 7, 2000 and MSDE with the same DDL and they don't have a problem.
> However, one user, who has been running the system on SQL 6.5 for years
now,
> keeps getting cannot insert duplicate key into PK_ blah blah. This error
is
> being generated on SQL 6.5's own auto-generated ID so I'm sure it is a
> problem that their SQL 6.5 has created in the db. The problem is after
> running the usual CHECKDB, CHECKALLOC, NEWALLOC, CHECKTABLE and
UPDATEUSAGE
> DBCC commands none of these have corrected the fault.
> I'm sure I've had this problem crop up once before and doing the CHECKDB
> fixed it, but I've run the CHECKDB 3 times now and it doesn't correct it.
> Can you give me any pointers on how I can check and more importantly
resolve
> this issue?
> Thanks Robbie
>
>|||Yes, it was.
SQL Server 6.5 has a few issues with Identity columns. Those issues went
away with SQL server 7.0.
DBCC CHECKIDENT
( 'table_name'
[ , { NORESEED
| { RESEED [ , new_reseed_value ] }
}
]
)
Checks the current identity value for the specified table and, if needed,
corrects the identity value.
As an aside, SQL Server 6.5 is no longer supported by Microsoft, so those
clients would be well advised to move to SQL Server 2000.
Regards
Mike
"Keith Kratochvil" wrote:

> I cannot remember. Is DBCC CHECKIDENT included with 6.5? If it is try usi
ng
> it.
> --
> Keith
>
> "Astra" <info@.noemail.com> wrote in message
> news:ex1KtA1GFHA.3088@.tk2msftngp13.phx.gbl...
> have
> now,
> is
> UPDATEUSAGE
> resolve
>

Cannot insert duplicate key into ...... EXTREME problem

Hi All
Really need your urgent help on this!
Created a system that uses an SQL database as the data store. Clients have
been using this same DDL since SQL 6.5 and I've got lots of users running
SQL 6.5, 7, 2000 and MSDE with the same DDL and they don't have a problem.
However, one user, who has been running the system on SQL 6.5 for years now,
keeps getting cannot insert duplicate key into PK_ blah blah. This error is
being generated on SQL 6.5's own auto-generated ID so I'm sure it is a
problem that their SQL 6.5 has created in the db. The problem is after
running the usual CHECKDB, CHECKALLOC, NEWALLOC, CHECKTABLE and UPDATEUSAGE
DBCC commands none of these have corrected the fault.
I'm sure I've had this problem crop up once before and doing the CHECKDB
fixed it, but I've run the CHECKDB 3 times now and it doesn't correct it.
Can you give me any pointers on how I can check and more importantly resolve
this issue?
Thanks RobbieI cannot remember. Is DBCC CHECKIDENT included with 6.5? If it is try using
it.
--
Keith
"Astra" <info@.noemail.com> wrote in message
news:OQdxVA1GFHA.3128@.TK2MSFTNGP10.phx.gbl...
> Hi All
> Really need your urgent help on this!
> Created a system that uses an SQL database as the data store. Clients
have
> been using this same DDL since SQL 6.5 and I've got lots of users running
> SQL 6.5, 7, 2000 and MSDE with the same DDL and they don't have a problem.
> However, one user, who has been running the system on SQL 6.5 for years
now,
> keeps getting cannot insert duplicate key into PK_ blah blah. This error
is
> being generated on SQL 6.5's own auto-generated ID so I'm sure it is a
> problem that their SQL 6.5 has created in the db. The problem is after
> running the usual CHECKDB, CHECKALLOC, NEWALLOC, CHECKTABLE and
UPDATEUSAGE
> DBCC commands none of these have corrected the fault.
> I'm sure I've had this problem crop up once before and doing the CHECKDB
> fixed it, but I've run the CHECKDB 3 times now and it doesn't correct it.
> Can you give me any pointers on how I can check and more importantly
resolve
> this issue?
> Thanks Robbie
>|||Hi Astra,
I do not have any 6.5 experience however I have seen this
problem on 2000.
Within 2000 if you run the command
SELECT TOP 100 PERCENT name, IDENT_SEED(name) AS [ID
Start], IDENT_INCR(name) AS [ID Increment], IDENT_CURRENT
(name) AS [Current ID]
FROM dbo.sysobjects
WHERE xtype = 'U'
ORDER BY IDENT_SEED(name)
You will get the current identity values for the user
tables in your database.
I think that somehow one on your 6.5 has got out of
sequence i.e. the current identity is 4, but internally it
thinks it 3, so it trys to insert 4 in again.
How we solved this in 2000 was with the DBCC CHECKIDENT
command.
Peter
"Although prepared for martyrdom, I preferred that it be
postponed."
Winston Churchill
>--Original Message--
>Hi All
>Really need your urgent help on this!
>Created a system that uses an SQL database as the data
store. Clients have
>been using this same DDL since SQL 6.5 and I've got lots
of users running
>SQL 6.5, 7, 2000 and MSDE with the same DDL and they
don't have a problem.
>However, one user, who has been running the system on SQL
6.5 for years now,
>keeps getting cannot insert duplicate key into PK_ blah
blah. This error is
>being generated on SQL 6.5's own auto-generated ID so I'm
sure it is a
>problem that their SQL 6.5 has created in the db. The
problem is after
>running the usual CHECKDB, CHECKALLOC, NEWALLOC,
CHECKTABLE and UPDATEUSAGE
>DBCC commands none of these have corrected the fault.
>I'm sure I've had this problem crop up once before and
doing the CHECKDB
>fixed it, but I've run the CHECKDB 3 times now and it
doesn't correct it.
>Can you give me any pointers on how I can check and more
importantly resolve
>this issue?
>Thanks Robbie
>
>.
>|||Yes, it was.
SQL Server 6.5 has a few issues with Identity columns. Those issues went
away with SQL server 7.0.
DBCC CHECKIDENT
( 'table_name'
[ , { NORESEED
| { RESEED [ , new_reseed_value ] }
}
]
)
Checks the current identity value for the specified table and, if needed,
corrects the identity value.
As an aside, SQL Server 6.5 is no longer supported by Microsoft, so those
clients would be well advised to move to SQL Server 2000.
Regards
Mike
"Keith Kratochvil" wrote:
> I cannot remember. Is DBCC CHECKIDENT included with 6.5? If it is try using
> it.
> --
> Keith
>
> "Astra" <info@.noemail.com> wrote in message
> news:OQdxVA1GFHA.3128@.TK2MSFTNGP10.phx.gbl...
> > Hi All
> >
> > Really need your urgent help on this!
> >
> > Created a system that uses an SQL database as the data store. Clients
> have
> > been using this same DDL since SQL 6.5 and I've got lots of users running
> > SQL 6.5, 7, 2000 and MSDE with the same DDL and they don't have a problem.
> >
> > However, one user, who has been running the system on SQL 6.5 for years
> now,
> > keeps getting cannot insert duplicate key into PK_ blah blah. This error
> is
> > being generated on SQL 6.5's own auto-generated ID so I'm sure it is a
> > problem that their SQL 6.5 has created in the db. The problem is after
> > running the usual CHECKDB, CHECKALLOC, NEWALLOC, CHECKTABLE and
> UPDATEUSAGE
> > DBCC commands none of these have corrected the fault.
> >
> > I'm sure I've had this problem crop up once before and doing the CHECKDB
> > fixed it, but I've run the CHECKDB 3 times now and it doesn't correct it.
> >
> > Can you give me any pointers on how I can check and more importantly
> resolve
> > this issue?
> >
> > Thanks Robbie
> >
> >
>|||Guys
You've made my weekend!!!
Many thanks.
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:1ad701c51b53$2a8f0a20$a601280a@.phx.gbl...
Hi Astra,
I do not have any 6.5 experience however I have seen this
problem on 2000.
Within 2000 if you run the command
SELECT TOP 100 PERCENT name, IDENT_SEED(name) AS [ID
Start], IDENT_INCR(name) AS [ID Increment], IDENT_CURRENT
(name) AS [Current ID]
FROM dbo.sysobjects
WHERE xtype = 'U'
ORDER BY IDENT_SEED(name)
You will get the current identity values for the user
tables in your database.
I think that somehow one on your 6.5 has got out of
sequence i.e. the current identity is 4, but internally it
thinks it 3, so it trys to insert 4 in again.
How we solved this in 2000 was with the DBCC CHECKIDENT
command.
Peter
"Although prepared for martyrdom, I preferred that it be
postponed."
Winston Churchill
>--Original Message--
>Hi All
>Really need your urgent help on this!
>Created a system that uses an SQL database as the data
store. Clients have
>been using this same DDL since SQL 6.5 and I've got lots
of users running
>SQL 6.5, 7, 2000 and MSDE with the same DDL and they
don't have a problem.
>However, one user, who has been running the system on SQL
6.5 for years now,
>keeps getting cannot insert duplicate key into PK_ blah
blah. This error is
>being generated on SQL 6.5's own auto-generated ID so I'm
sure it is a
>problem that their SQL 6.5 has created in the db. The
problem is after
>running the usual CHECKDB, CHECKALLOC, NEWALLOC,
CHECKTABLE and UPDATEUSAGE
>DBCC commands none of these have corrected the fault.
>I'm sure I've had this problem crop up once before and
doing the CHECKDB
>fixed it, but I've run the CHECKDB 3 times now and it
doesn't correct it.
>Can you give me any pointers on how I can check and more
importantly resolve
>this issue?
>Thanks Robbie
>
>.
>

Cannot insert duplicate key into ...... EXTREME problem

Hi All
Really need your urgent help on this!
Created a system that uses an SQL database as the data store. Clients have
been using this same DDL since SQL 6.5 and I've got lots of users running
SQL 6.5, 7, 2000 and MSDE with the same DDL and they don't have a problem.
However, one user, who has been running the system on SQL 6.5 for years now,
keeps getting cannot insert duplicate key into PK_ blah blah. This error is
being generated on SQL 6.5's own auto-generated ID so I'm sure it is a
problem that their SQL 6.5 has created in the db. The problem is after
running the usual CHECKDB, CHECKALLOC, NEWALLOC, CHECKTABLE and UPDATEUSAGE
DBCC commands none of these have corrected the fault.
I'm sure I've had this problem crop up once before and doing the CHECKDB
fixed it, but I've run the CHECKDB 3 times now and it doesn't correct it.
Can you give me any pointers on how I can check and more importantly resolve
this issue?
Thanks RobbieI cannot remember. Is DBCC CHECKIDENT included with 6.5? If it is try using
it.
Keith
"Astra" <info@.noemail.com> wrote in message
news:OQdxVA1GFHA.3128@.TK2MSFTNGP10.phx.gbl...
> Hi All
> Really need your urgent help on this!
> Created a system that uses an SQL database as the data store. Clients
have
> been using this same DDL since SQL 6.5 and I've got lots of users running
> SQL 6.5, 7, 2000 and MSDE with the same DDL and they don't have a problem.
> However, one user, who has been running the system on SQL 6.5 for years
now,
> keeps getting cannot insert duplicate key into PK_ blah blah. This error
is
> being generated on SQL 6.5's own auto-generated ID so I'm sure it is a
> problem that their SQL 6.5 has created in the db. The problem is after
> running the usual CHECKDB, CHECKALLOC, NEWALLOC, CHECKTABLE and
UPDATEUSAGE
> DBCC commands none of these have corrected the fault.
> I'm sure I've had this problem crop up once before and doing the CHECKDB
> fixed it, but I've run the CHECKDB 3 times now and it doesn't correct it.
> Can you give me any pointers on how I can check and more importantly
resolve
> this issue?
> Thanks Robbie
>|||Yes, it was.
SQL Server 6.5 has a few issues with Identity columns. Those issues went
away with SQL server 7.0.
DBCC CHECKIDENT
( 'table_name'
[ , { NORESEED
| { RESEED [ , new_reseed_value ] }
}
]
)
Checks the current identity value for the specified table and, if needed,
corrects the identity value.
As an aside, SQL Server 6.5 is no longer supported by Microsoft, so those
clients would be well advised to move to SQL Server 2000.
Regards
Mike
"Keith Kratochvil" wrote:

> I cannot remember. Is DBCC CHECKIDENT included with 6.5? If it is try usi
ng
> it.
> --
> Keith
>
> "Astra" <info@.noemail.com> wrote in message
> news:OQdxVA1GFHA.3128@.TK2MSFTNGP10.phx.gbl...
> have
> now,
> is
> UPDATEUSAGE
> resolve
>

Cannot import Oracle data with OLE DB

I have a column in an Oracle source system with data type NUMBER(38,2). The value "-0.01" is causing problems when trying to import into a SSIS data-flow.

The only way I can import this into my data-flow is by using a Datareader connection manager using the ODBC Data Provider. My DSN is using the Oracle ODBC driver.

If I try and use the "Native OLE DB\Microsoft OLE DB Provider for Oracle" I get an error: "The data value cannot be converted for reasons other than sign mismatch or data overflow"

Judging by this post: http://microsoftdw.blogspot.com/2005/11/final-storyhow-to-get-data-out-of.html there aren't really any other combinations to try that will bring my data in as I want it.

I don't want to use ODBC though as:

Its an old technology Its slow I have to deploy an additional DSN.

Can anyone tell me why the other options don't work? Why does Microsoft OLE DB Provider for Oracle have a problem with "-0.01"?

-Jamie

When I tried to reproduce the issue reported by you, I encountered different set of problems. I tried to copy data from a Oracle table with NUMBER(38,2) column to a SQL Server 2005 table with a NUMERIC (38,2) column using OraOLEDB (and later using MSDORA) OLE DB connection manager at the source. I dont get any error messages when I execute the package. However, no data is transferred and I do not see any data when I preview the data at the source. May be I am missing something that you did that produced the error message you got.|||

Well I can't even preview the data so I think my problem is more deep seated. My errors occur in the source adapter and hence I think I have a problem in the middleware.

-Jamie

cannot get data from syscomments

Hi!
My user cannot retreive data from syscomments system view., but can do
it from sysobjects. What can be done wrong when upgrading from ms sql
7 to ms sql 5k5? The same upgrade process was done on 400 servers and
problem is known only on seveal
Syscomments is no more an available view: to view stored procedures and
triggers definition you should query the cataloged view sys.sql_modules, or
use OBJECT DEFINITION or the sp_helptext system stored procedure.
See the related topics on the Books on Line.
Gilberto Zampatti
"Jacek.Piechucki@.gmail.com" wrote:

> Hi!
> My user cannot retreive data from syscomments system view., but can do
> it from sysobjects. What can be done wrong when upgrading from ms sql
> 7 to ms sql 5k5? The same upgrade process was done on 400 servers and
> problem is known only on seveal
>
|||<Jacek.Piechucki@.gmail.com> wrote in message
news:1180006384.209339.161890@.q75g2000hsh.googlegr oups.com...
> Hi!
> My user cannot retreive data from syscomments system view., but can do
> it from sysobjects. What can be done wrong when upgrading from ms sql
> 7 to ms sql 5k5? The same upgrade process was done on 400 servers and
> problem is known only on seveal
>
Since these are 'undocumented' views I believe, their functionality changes
from version to version.
SQL 2005 has changed a lot of this and has some views for backwards
compatibility,
But most likely the code needs to be updated for 2005.
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||If so, why do I have problems only on several from whole 400 servers?
On more tahn 380 others everything works well.
What can be valuable: all of our databses (except of master) work with
compatibility level of SQL Server 7.0.
On 24 Maj, 15:36, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> Syscomments is no more an available view: to view stored procedures and
> triggers definition you should query the cataloged view sys.sql_modules, or
> use OBJECT DEFINITION or the sp_helptext system stored procedure.
> See the related topics on the Books on Line.
> Gilberto Zampatti
>
> "Jacek.Piechu...@.gmail.com" wrote:
> - Poka cytowany tekst -
|||<Jacek.Piechucki@.gmail.com> wrote in message
news:1180018413.412996.83620@.w5g2000hsg.googlegrou ps.com...
> If so, why do I have problems only on several from whole 400 servers?
It wasn't clear from your send that all 400 had been upgraded to SQL 2005.
It sounded like it was only breaking on the one.
In any event, most likely a permissions problem.

> On more tahn 380 others everything works well.
> What can be valuable: all of our databses (except of master) work with
> compatibility level of SQL Server 7.0.
That really doesn't matter here.
I'd check to see if the permissions are the same across all 400 servers.

>
> On 24 Maj, 15:36, Gilberto Zampatti
> <GilbertoZampa...@.discussions.microsoft.com> wrote:
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Anything related to permissions is identical on all servers.
On 24 Maj, 17:21, "Greg D. Moore \(Strider\)"
<mooregr_deletet...@.greenms.com> wrote:
> <Jacek.Piechu...@.gmail.com> wrote in message
> news:1180018413.412996.83620@.w5g2000hsg.googlegrou ps.com...
>
> It wasn't clear from your send that all 400 had been upgraded to SQL 2005.
> It sounded like it was only breaking on the one.
> In any event, most likely a permissions problem.
>
> That really doesn't matter here.
> I'd check to see if the permissions are the same across all 400 servers.
>
>
>
>
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html- Ukryj cytowany tekst -
> - Poka cytowany tekst -

cannot get data from syscomments

Hi!
My user cannot retreive data from syscomments system view., but can do
it from sysobjects. What can be done wrong when upgrading from ms sql
7 to ms sql 5k5? The same upgrade process was done on 400 servers and
problem is known only on seveal:(Syscomments is no more an available view: to view stored procedures and
triggers definition you should query the cataloged view sys.sql_modules, or
use OBJECT DEFINITION or the sp_helptext system stored procedure.
See the related topics on the Books on Line.
Gilberto Zampatti
"Jacek.Piechucki@.gmail.com" wrote:
> Hi!
> My user cannot retreive data from syscomments system view., but can do
> it from sysobjects. What can be done wrong when upgrading from ms sql
> 7 to ms sql 5k5? The same upgrade process was done on 400 servers and
> problem is known only on seveal:(
>|||<Jacek.Piechucki@.gmail.com> wrote in message
news:1180006384.209339.161890@.q75g2000hsh.googlegroups.com...
> Hi!
> My user cannot retreive data from syscomments system view., but can do
> it from sysobjects. What can be done wrong when upgrading from ms sql
> 7 to ms sql 5k5? The same upgrade process was done on 400 servers and
> problem is known only on seveal:(
>
Since these are 'undocumented' views I believe, their functionality changes
from version to version.
SQL 2005 has changed a lot of this and has some views for backwards
compatibility,
But most likely the code needs to be updated for 2005.
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||If so, why do I have problems only on several from whole 400 servers?
On more tahn 380 others everything works well.
What can be valuable: all of our databses (except of master) work with
compatibility level of SQL Server 7.0.
On 24 Maj, 15:36, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> Syscomments is no more an available view: to view stored procedures and
> triggers definition you should query the cataloged view sys.sql_modules, or
> use OBJECT DEFINITION or the sp_helptext system stored procedure.
> See the related topics on the Books on Line.
> Gilberto Zampatti
>
> "Jacek.Piechu...@.gmail.com" wrote:
> > Hi!
> > My user cannot retreive data from syscomments system view., but can do
> > it from sysobjects. What can be done wrong when upgrading from ms sql
> > 7 to ms sql 5k5? The same upgrade process was done on 400 servers and
> > problem is known only on seveal:(- Ukryj cytowany tekst -
> - Poka cytowany tekst -|||<Jacek.Piechucki@.gmail.com> wrote in message
news:1180018413.412996.83620@.w5g2000hsg.googlegroups.com...
> If so, why do I have problems only on several from whole 400 servers?
It wasn't clear from your send that all 400 had been upgraded to SQL 2005.
It sounded like it was only breaking on the one.
In any event, most likely a permissions problem.
> On more tahn 380 others everything works well.
> What can be valuable: all of our databses (except of master) work with
> compatibility level of SQL Server 7.0.
That really doesn't matter here.
I'd check to see if the permissions are the same across all 400 servers.
>
> On 24 Maj, 15:36, Gilberto Zampatti
> <GilbertoZampa...@.discussions.microsoft.com> wrote:
>> Syscomments is no more an available view: to view stored procedures and
>> triggers definition you should query the cataloged view sys.sql_modules,
>> or
>> use OBJECT DEFINITION or the sp_helptext system stored procedure.
>> See the related topics on the Books on Line.
>> Gilberto Zampatti
>>
>> "Jacek.Piechu...@.gmail.com" wrote:
>> > Hi!
>> > My user cannot retreive data from syscomments system view., but can do
>> > it from sysobjects. What can be done wrong when upgrading from ms sql
>> > 7 to ms sql 5k5? The same upgrade process was done on 400 servers and
>> > problem is known only on seveal:(- Ukryj cytowany tekst -
>> - Poka cytowany tekst -
>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Anything related to permissions is identical on all servers.
On 24 Maj, 17:21, "Greg D. Moore \(Strider\)"
<mooregr_deletet...@.greenms.com> wrote:
> <Jacek.Piechu...@.gmail.com> wrote in message
> news:1180018413.412996.83620@.w5g2000hsg.googlegroups.com...
> > If so, why do I have problems only on several from whole 400 servers?
> It wasn't clear from your send that all 400 had been upgraded to SQL 2005.
> It sounded like it was only breaking on the one.
> In any event, most likely a permissions problem.
> > On more tahn 380 others everything works well.
> > What can be valuable: all of our databses (except of master) work with
> > compatibility level of SQL Server 7.0.
> That really doesn't matter here.
> I'd check to see if the permissions are the same across all 400 servers.
>
>
>
> > On 24 Maj, 15:36, Gilberto Zampatti
> > <GilbertoZampa...@.discussions.microsoft.com> wrote:
> >> Syscomments is no more an available view: to view stored procedures and
> >> triggers definition you should query the cataloged view sys.sql_modules,
> >> or
> >> use OBJECT DEFINITION or the sp_helptext system stored procedure.
> >> See the related topics on the Books on Line.
> >> Gilberto Zampatti
> >> "Jacek.Piechu...@.gmail.com" wrote:
> >> > Hi!
> >> > My user cannot retreive data from syscomments system view., but can do
> >> > it from sysobjects. What can be done wrong when upgrading from ms sql
> >> > 7 to ms sql 5k5? The same upgrade process was done on 400 servers and
> >> > problem is known only on seveal:(- Ukryj cytowany tekst -
> >> - Poka cytowany tekst -
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html- Ukryj cytowany tekst -
> - Poka cytowany tekst -

cannot get data from syscomments

Hi!
My user cannot retreive data from syscomments system view., but can do
it from sysobjects. What can be done wrong when upgrading from ms sql
7 to ms sql 5k5? The same upgrade process was done on 400 servers and
problem is known only on sevealSyscomments is no more an available view: to view stored procedures and
triggers definition you should query the cataloged view sys.sql_modules, or
use OBJECT DEFINITION or the sp_helptext system stored procedure.
See the related topics on the Books on Line.
Gilberto Zampatti
"Jacek.Piechucki@.gmail.com" wrote:

> Hi!
> My user cannot retreive data from syscomments system view., but can do
> it from sysobjects. What can be done wrong when upgrading from ms sql
> 7 to ms sql 5k5? The same upgrade process was done on 400 servers and
> problem is known only on seveal
>|||<Jacek.Piechucki@.gmail.com> wrote in message
news:1180006384.209339.161890@.q75g2000hsh.googlegroups.com...
> Hi!
> My user cannot retreive data from syscomments system view., but can do
> it from sysobjects. What can be done wrong when upgrading from ms sql
> 7 to ms sql 5k5? The same upgrade process was done on 400 servers and
> problem is known only on seveal
>
Since these are 'undocumented' views I believe, their functionality changes
from version to version.
SQL 2005 has changed a lot of this and has some views for backwards
compatibility,
But most likely the code needs to be updated for 2005.
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||If so, why do I have problems only on several from whole 400 servers?
On more tahn 380 others everything works well.
What can be valuable: all of our databses (except of master) work with
compatibility level of SQL Server 7.0.
On 24 Maj, 15:36, Gilberto Zampatti
<GilbertoZampa...@.discussions.microsoft.com> wrote:
> Syscomments is no more an available view: to view stored procedures and
> triggers definition you should query the cataloged view sys.sql_modules, o
r
> use OBJECT DEFINITION or the sp_helptext system stored procedure.
> See the related topics on the Books on Line.
> Gilberto Zampatti
>
> "Jacek.Piechu...@.gmail.com" wrote:
> - Poka cytowany tekst -|||<Jacek.Piechucki@.gmail.com> wrote in message
news:1180018413.412996.83620@.w5g2000hsg.googlegroups.com...
> If so, why do I have problems only on several from whole 400 servers?
It wasn't clear from your send that all 400 had been upgraded to SQL 2005.
It sounded like it was only breaking on the one.
In any event, most likely a permissions problem.

> On more tahn 380 others everything works well.
> What can be valuable: all of our databses (except of master) work with
> compatibility level of SQL Server 7.0.
That really doesn't matter here.
I'd check to see if the permissions are the same across all 400 servers.

>
> On 24 Maj, 15:36, Gilberto Zampatti
> <GilbertoZampa...@.discussions.microsoft.com> wrote:
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Anything related to permissions is identical on all servers.
On 24 Maj, 17:21, "Greg D. Moore \(Strider\)"
<mooregr_deletet...@.greenms.com> wrote:
> <Jacek.Piechu...@.gmail.com> wrote in message
> news:1180018413.412996.83620@.w5g2000hsg.googlegroups.com...
>
> It wasn't clear from your send that all 400 had been upgraded to SQL 2005.
> It sounded like it was only breaking on the one.
> In any event, most likely a permissions problem.
>
> That really doesn't matter here.
> I'd check to see if the permissions are the same across all 400 servers.
>
>
>
>
>
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com [url]http://www.greenms.com/sqlserver.html-[/u
rl] Ukryj cytowany tekst -
> - Poka cytowany tekst -

cannot generate sspi context

SQL server 2000 SP4 has been running for several years. We added a new
Client PC, our first with the XP operating system. Microsoft Access 2000 is
the front end, and all tables and views on the server are connected thru an
ODBC connection. Everyone else in the office works fine, but the new XP
machine, after several minutes of inactivity, seems to lose its connection.
The Access app reports an ODBC error, and we see the "Cannot generate SSPI
context" message. We actually have to reboot the client PC, since even
testing the ODBC connection in the Control Panel fails.
Any ideas?Try the following article:
How to troubleshoot the "Cannot generate SSPI context" error
message
http://support.microsoft.com/?id=811889
-Sue
On Tue, 23 Aug 2005 12:03:03 -0700, "menacher"
<menacher@.discussions.microsoft.com> wrote:

>SQL server 2000 SP4 has been running for several years. We added a new
>Client PC, our first with the XP operating system. Microsoft Access 2000 i
s
>the front end, and all tables and views on the server are connected thru an
>ODBC connection. Everyone else in the office works fine, but the new XP
>machine, after several minutes of inactivity, seems to lose its connection.
>The Access app reports an ODBC error, and we see the "Cannot generate SSPI
>context" message. We actually have to reboot the client PC, since even
>testing the ODBC connection in the Control Panel fails.
>Any ideas?