Is it possible to create a trigger that inserts the @.@.identity (primary key) from Table1 into a field in Table2?
If so, how? Thank you.
-D-yes it's possible. Create a trigger on Table1 for insert and execute an insert-statement using @.@.identity. Are you stuck?
Showing posts with label primary. Show all posts
Showing posts with label primary. Show all posts
Sunday, March 25, 2012
HOW: Auotincrement without using autoincrement
I have a master table which I have been updating in multiple queries to
create a new row. It has a primary key, call it WorkID. I can't make it
autoincrement. And it is more complicated because...
WorkID can also appear in two other tables, as references to the master
record, but I need to provide for the master record being gone, and as
such the records in the other two tables are orphaned. That is fine.
To create a new master record I select MAX(WorkID) unioned on all 3
tables, and increment the result, and this is my new WorkID. However,
even if in a transaction, this query work can result in duplicate WorkID
numbers when new masters are created in extremely rapid succession. I
see the flaw here. Don't think this approach can be salvaged when the
MAX and INSERT queries are done separately.
I have been racking my brain to find a way to deal with this WITHOUT
resorting to auto-increment on the master table. I can think of no
expression for an INSERT value which will take the MAX+1 of WorkID on
the three tables, but it seems there must be a way to do this in a
single statement. Something like:
INSERT WORK (WorkID) VALUES (SELECT MAX(WorkID)+1 FROM ... UNION ... )
Maybe I need a new single row, single column table that arbitrates new
WorkID values? Or maybe someone has a favorite trick?
Thx - Lee>> I have a master table .. <<
I have not heard that term since I moved from navigational DBMS to
RDBMS in thw 1970's. Let's get back to the basics of an RDBMS. Rows
are not records; fields are not columns; tables are not files. The
differences are VITAL!!!
Of course not! An exposed physical locator created inside the hardware
cannot be a relational key by definition.
Well, you need a new brain :) What is the natrual, relational key in
the SPECS YOU NEVER POSTED -- repeated SPECS YOU NEVER POSTED? I
assume that you are not soooooo ignorant that you want to have a
"magical one-size-fits-all" auto numbering.|||Wow.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1123641244.396767.117310@.g14g2000cwa.googlegroups.com...
> I have not heard that term since I moved from navigational DBMS to
> RDBMS in thw 1970's. Let's get back to the basics of an RDBMS. Rows
> are not records; fields are not columns; tables are not files. The
> differences are VITAL!!!
>
> Of course not! An exposed physical locator created inside the hardware
> cannot be a relational key by definition.
>
> Well, you need a new brain :) What is the natrual, relational key in
> the SPECS YOU NEVER POSTED -- repeated SPECS YOU NEVER POSTED? I
> assume that you are not soooooo ignorant that you want to have a
> "magical one-size-fits-all" auto numbering.
>|||On Tue, 09 Aug 2005 12:18:38 -0700, Lee Gillie wrote:
> I have been racking my brain to find a way to deal with this WITHOUT
> resorting to auto-increment on the master table. I can think of no
> expression for an INSERT value which will take the MAX+1 of WorkID on
> the three tables, but it seems there must be a way to do this in a
> single statement. Something like:
> INSERT WORK (WorkID) VALUES (SELECT MAX(WorkID)+1 FROM ... UNION ... )
> Maybe I need a new single row, single column table that arbitrates new
> WorkID values? Or maybe someone has a favorite trick?
> Thx - Lee
As Celko said, you could probably do well with a full redesign that uses a
natural key. Failing that, how about this:
INSERT WORK (WorkID)
SELECT 1+MAX(WorkID)
FROM (
SELECT MAX(WorkID) WorkID FROM WORK
UNION ALL
SELECT MAX(WorkID) WorkID FROM OtherTable1
UNION ALL
SELECT MAX(WorkID) WorkID FROM OtherTable2
)
A better way might be to keep your available unused workIDs in yet another
table. First gather all used WorkIDs in the table:
CREATE TABLE WorkIDs (WorkID int, Used bit)
INSERT INTO WorkIDs (WorkID, Used)
SELECT WorkID, 1 FROM WORK
UNION
SELECT WorkID, 1 FROM OtherTable1
UNION
SELECT WorkID, 1 FROM OtherTable2
Now add some new ones for future use:
DECLARE @.maxworkID int
DECLARE @.x int
SELECT @.maxworkID = MAX(WorkID) FROM WorkIDs
SET @.x = @.maxworkID
WHILE @.x < @.maxworkID + 10000
BEGIN
INSERT INTO WorkIDs (WorkID, Used) VALUES (@.x, 0)
SET @.x = @.x + 1
END
Now here's your procedure for creating a new workID:
BEGIN TRANSACTION
DECLARE @.newWorkID int
SELECT @.newWorkID = MIN(WorkID) FROM WorkIDs WHERE Used=0
INSERT INTO WORK (WorkID) VALUES (@.newWorkID)
UPDATE WorkIDs SET Used=1 WHERE WorkID=@.newWorkID
COMMIT TRANSACTION|||> BEGIN TRANSACTION
> DECLARE @.newWorkID int
> SELECT @.newWorkID = MIN(WorkID) FROM WorkIDs WHERE Used=0
> INSERT INTO WORK (WorkID) VALUES (@.newWorkID)
> UPDATE WorkIDs SET Used=1 WHERE WorkID=@.newWorkID
> COMMIT TRANSACTION
Actually this is the worst case scenario for a busy system unless you use
exclusive locks. Say two users start the select at the same time. Boom,
deadlock. They both have a shared read lock on the workId's, the both
insert into work and then the UPDATE tries to WorkIDs to the same value
requiring exclusive locks. (unless the Unique Key fails them in the Work
table.)
> INSERT WORK (WorkID)
> SELECT 1+MAX(WorkID)
> FROM (
> SELECT MAX(WorkID) WorkID FROM WORK
> UNION ALL
> SELECT MAX(WorkID) WorkID FROM OtherTable1
> UNION ALL
> SELECT MAX(WorkID) WorkID FROM OtherTable2
> )
This would have to single thread over ALL tables! The SELECT by default
would only take shared locks, so any two users could be getting the max
values at the same time.
This gets even worse if this transaction gets called in another transaction.
There is not a good way to do this without single threading.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Ross Presser" <rpresser@.NOSPAMgmail.com.invalid> wrote in message
news:85kyr6seugm6$.dlg@.rosspresser.dyndns.org...
> On Tue, 09 Aug 2005 12:18:38 -0700, Lee Gillie wrote:
>
> As Celko said, you could probably do well with a full redesign that uses a
> natural key. Failing that, how about this:
> INSERT WORK (WorkID)
> SELECT 1+MAX(WorkID)
> FROM (
> SELECT MAX(WorkID) WorkID FROM WORK
> UNION ALL
> SELECT MAX(WorkID) WorkID FROM OtherTable1
> UNION ALL
> SELECT MAX(WorkID) WorkID FROM OtherTable2
> )
> A better way might be to keep your available unused workIDs in yet another
> table. First gather all used WorkIDs in the table:
> CREATE TABLE WorkIDs (WorkID int, Used bit)
> INSERT INTO WorkIDs (WorkID, Used)
> SELECT WorkID, 1 FROM WORK
> UNION
> SELECT WorkID, 1 FROM OtherTable1
> UNION
> SELECT WorkID, 1 FROM OtherTable2
> Now add some new ones for future use:
> DECLARE @.maxworkID int
> DECLARE @.x int
> SELECT @.maxworkID = MAX(WorkID) FROM WorkIDs
> SET @.x = @.maxworkID
> WHILE @.x < @.maxworkID + 10000
> BEGIN
> INSERT INTO WorkIDs (WorkID, Used) VALUES (@.x, 0)
> SET @.x = @.x + 1
> END
> Now here's your procedure for creating a new workID:
> BEGIN TRANSACTION
> DECLARE @.newWorkID int
> SELECT @.newWorkID = MIN(WorkID) FROM WorkIDs WHERE Used=0
> INSERT INTO WORK (WorkID) VALUES (@.newWorkID)
> UPDATE WorkIDs SET Used=1 WHERE WorkID=@.newWorkID
> COMMIT TRANSACTION|||On Thu, 11 Aug 2005 21:39:02 -0500, Louis Davidson wrote:
[snip]
> This gets even worse if this transaction gets called in another transactio
n.
> There is not a good way to do this without single threading.
Thanks for your comments. So, is there any decent answer to the problem of
generating new WorkIDs without using IDENTITY?
create a new row. It has a primary key, call it WorkID. I can't make it
autoincrement. And it is more complicated because...
WorkID can also appear in two other tables, as references to the master
record, but I need to provide for the master record being gone, and as
such the records in the other two tables are orphaned. That is fine.
To create a new master record I select MAX(WorkID) unioned on all 3
tables, and increment the result, and this is my new WorkID. However,
even if in a transaction, this query work can result in duplicate WorkID
numbers when new masters are created in extremely rapid succession. I
see the flaw here. Don't think this approach can be salvaged when the
MAX and INSERT queries are done separately.
I have been racking my brain to find a way to deal with this WITHOUT
resorting to auto-increment on the master table. I can think of no
expression for an INSERT value which will take the MAX+1 of WorkID on
the three tables, but it seems there must be a way to do this in a
single statement. Something like:
INSERT WORK (WorkID) VALUES (SELECT MAX(WorkID)+1 FROM ... UNION ... )
Maybe I need a new single row, single column table that arbitrates new
WorkID values? Or maybe someone has a favorite trick?
Thx - Lee>> I have a master table .. <<
I have not heard that term since I moved from navigational DBMS to
RDBMS in thw 1970's. Let's get back to the basics of an RDBMS. Rows
are not records; fields are not columns; tables are not files. The
differences are VITAL!!!
Of course not! An exposed physical locator created inside the hardware
cannot be a relational key by definition.
Well, you need a new brain :) What is the natrual, relational key in
the SPECS YOU NEVER POSTED -- repeated SPECS YOU NEVER POSTED? I
assume that you are not soooooo ignorant that you want to have a
"magical one-size-fits-all" auto numbering.|||Wow.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1123641244.396767.117310@.g14g2000cwa.googlegroups.com...
> I have not heard that term since I moved from navigational DBMS to
> RDBMS in thw 1970's. Let's get back to the basics of an RDBMS. Rows
> are not records; fields are not columns; tables are not files. The
> differences are VITAL!!!
>
> Of course not! An exposed physical locator created inside the hardware
> cannot be a relational key by definition.
>
> Well, you need a new brain :) What is the natrual, relational key in
> the SPECS YOU NEVER POSTED -- repeated SPECS YOU NEVER POSTED? I
> assume that you are not soooooo ignorant that you want to have a
> "magical one-size-fits-all" auto numbering.
>|||On Tue, 09 Aug 2005 12:18:38 -0700, Lee Gillie wrote:
> I have been racking my brain to find a way to deal with this WITHOUT
> resorting to auto-increment on the master table. I can think of no
> expression for an INSERT value which will take the MAX+1 of WorkID on
> the three tables, but it seems there must be a way to do this in a
> single statement. Something like:
> INSERT WORK (WorkID) VALUES (SELECT MAX(WorkID)+1 FROM ... UNION ... )
> Maybe I need a new single row, single column table that arbitrates new
> WorkID values? Or maybe someone has a favorite trick?
> Thx - Lee
As Celko said, you could probably do well with a full redesign that uses a
natural key. Failing that, how about this:
INSERT WORK (WorkID)
SELECT 1+MAX(WorkID)
FROM (
SELECT MAX(WorkID) WorkID FROM WORK
UNION ALL
SELECT MAX(WorkID) WorkID FROM OtherTable1
UNION ALL
SELECT MAX(WorkID) WorkID FROM OtherTable2
)
A better way might be to keep your available unused workIDs in yet another
table. First gather all used WorkIDs in the table:
CREATE TABLE WorkIDs (WorkID int, Used bit)
INSERT INTO WorkIDs (WorkID, Used)
SELECT WorkID, 1 FROM WORK
UNION
SELECT WorkID, 1 FROM OtherTable1
UNION
SELECT WorkID, 1 FROM OtherTable2
Now add some new ones for future use:
DECLARE @.maxworkID int
DECLARE @.x int
SELECT @.maxworkID = MAX(WorkID) FROM WorkIDs
SET @.x = @.maxworkID
WHILE @.x < @.maxworkID + 10000
BEGIN
INSERT INTO WorkIDs (WorkID, Used) VALUES (@.x, 0)
SET @.x = @.x + 1
END
Now here's your procedure for creating a new workID:
BEGIN TRANSACTION
DECLARE @.newWorkID int
SELECT @.newWorkID = MIN(WorkID) FROM WorkIDs WHERE Used=0
INSERT INTO WORK (WorkID) VALUES (@.newWorkID)
UPDATE WorkIDs SET Used=1 WHERE WorkID=@.newWorkID
COMMIT TRANSACTION|||> BEGIN TRANSACTION
> DECLARE @.newWorkID int
> SELECT @.newWorkID = MIN(WorkID) FROM WorkIDs WHERE Used=0
> INSERT INTO WORK (WorkID) VALUES (@.newWorkID)
> UPDATE WorkIDs SET Used=1 WHERE WorkID=@.newWorkID
> COMMIT TRANSACTION
Actually this is the worst case scenario for a busy system unless you use
exclusive locks. Say two users start the select at the same time. Boom,
deadlock. They both have a shared read lock on the workId's, the both
insert into work and then the UPDATE tries to WorkIDs to the same value
requiring exclusive locks. (unless the Unique Key fails them in the Work
table.)
> INSERT WORK (WorkID)
> SELECT 1+MAX(WorkID)
> FROM (
> SELECT MAX(WorkID) WorkID FROM WORK
> UNION ALL
> SELECT MAX(WorkID) WorkID FROM OtherTable1
> UNION ALL
> SELECT MAX(WorkID) WorkID FROM OtherTable2
> )
This would have to single thread over ALL tables! The SELECT by default
would only take shared locks, so any two users could be getting the max
values at the same time.
This gets even worse if this transaction gets called in another transaction.
There is not a good way to do this without single threading.
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Ross Presser" <rpresser@.NOSPAMgmail.com.invalid> wrote in message
news:85kyr6seugm6$.dlg@.rosspresser.dyndns.org...
> On Tue, 09 Aug 2005 12:18:38 -0700, Lee Gillie wrote:
>
> As Celko said, you could probably do well with a full redesign that uses a
> natural key. Failing that, how about this:
> INSERT WORK (WorkID)
> SELECT 1+MAX(WorkID)
> FROM (
> SELECT MAX(WorkID) WorkID FROM WORK
> UNION ALL
> SELECT MAX(WorkID) WorkID FROM OtherTable1
> UNION ALL
> SELECT MAX(WorkID) WorkID FROM OtherTable2
> )
> A better way might be to keep your available unused workIDs in yet another
> table. First gather all used WorkIDs in the table:
> CREATE TABLE WorkIDs (WorkID int, Used bit)
> INSERT INTO WorkIDs (WorkID, Used)
> SELECT WorkID, 1 FROM WORK
> UNION
> SELECT WorkID, 1 FROM OtherTable1
> UNION
> SELECT WorkID, 1 FROM OtherTable2
> Now add some new ones for future use:
> DECLARE @.maxworkID int
> DECLARE @.x int
> SELECT @.maxworkID = MAX(WorkID) FROM WorkIDs
> SET @.x = @.maxworkID
> WHILE @.x < @.maxworkID + 10000
> BEGIN
> INSERT INTO WorkIDs (WorkID, Used) VALUES (@.x, 0)
> SET @.x = @.x + 1
> END
> Now here's your procedure for creating a new workID:
> BEGIN TRANSACTION
> DECLARE @.newWorkID int
> SELECT @.newWorkID = MIN(WorkID) FROM WorkIDs WHERE Used=0
> INSERT INTO WORK (WorkID) VALUES (@.newWorkID)
> UPDATE WorkIDs SET Used=1 WHERE WorkID=@.newWorkID
> COMMIT TRANSACTION|||On Thu, 11 Aug 2005 21:39:02 -0500, Louis Davidson wrote:
[snip]
> This gets even worse if this transaction gets called in another transactio
n.
> There is not a good way to do this without single threading.
Thanks for your comments. So, is there any decent answer to the problem of
generating new WorkIDs without using IDENTITY?
Sunday, March 11, 2012
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help
|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards
|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help
|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards
|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help
|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards
|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help
|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards
|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help
|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards
|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help
|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards
|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help
|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards
|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
.NET Runtime Optimization error on SQL Server 2005
I posted this on the .NET Framework inside Sql Server forum as well. Sorry if the cross-post offends anybody.
I upgraded my primary production server this morning to SQL 2005. Everything went fairly smoothly, but a couple of hours after my installation was complete, I found the following error in my event log:
Source: .NET Runtime Optimization Service
EventID: 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I am a little stumped since we did not install Reporting Services. We only installed Database Services, Integration Services and Workstation Components. I'm open to any suggestions on this. This does not seem to be negatively affecting our server, but I do want to resolve it as soon as possible.
Thanks,
Kevin
I'm getting the same message. Now I'm unable to modify or create tables.|||Hi,
try to restart the .NET RuntimeOptimization service. If this does not help you can also work without the service temporary. If you have a maintainance windows and can make a reboot of your server, that would be my next step.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
Hi
I have just installed Reporting Services 2005, SP1, and Rollup fix 2153. Also I have rebooted the machine and I am still getting the event log message which was posted at the beginning of this thread. Do we have a status or resolution for this.
Thanks
Steve
|||Have you try to stop/start ".Net Runtime Optimization Server v2.0.50727_X86" yet? This service usually set to "manual" and not started.|||I have the same problem and none of the above works. Any other ideas from anyone?|||Hello,
I am running my Asp.Net website on IIS5.1 and Sql Server 2005 for about 6 months now, and it works fine on 3 machines.
I recently installed another machine with identical configuration and created the project from VSS. I get the above error whenever I try to debug. As soon as I start debugging, the .NET Runtime Optimization Service enters stopped state with above error. The following is the exact error in Application Event Viewer:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
Any help would be greatly appreciated!!!
|||
We just applied SP1 for SQL Server 2005 on our production server after a successful installation on our test servers and started to get the same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile
We haven't attempted any type of fix yet, waiting to see if anyone else has fixed it yet.
|||The problem was fixed when I reinstalled Sql Server. Apparently some error during installation, couldnt figure it out.
I think the sequence of installation matters. When I install an XP machine, I stick to the following installation sequence:
Xp->SP2->IIS->MSOffice->OfficeSP->MS Sql Server 2000->Visual Studio->MSDN->VSS->Enterprise Library
Probably This sequence doesnt work for Sql Server 2005
|||Hihow do you have reinstalled the SQL Server?
Do you have deinstalled/installed the server or how?
We have 3 Instances with diffrent DB′s and i don′t want to crash them.
Thanks for help|||
Best bet is to identify the instance has to be un-installed. In add-remove programs the instances are shown separately. What I did was to stop the sql server in question and save all the LDF and MDF files in a separate folder.
After uninstalling I made sure that corresponding directories and registry entries were completely removed. Then I verified that I am in the correct order, and initiated the installation. I have mentioned the order of installation in my previous message. No need to uninstall .Net framework 2.0 incase already installed. Also, verify that the latest OS service pack is in place before initiate the install.
Once complete, I copied the LDF and MDF files back into the data folder and re-attached the databases. That worked for me.
Hope I have answered your question
|||thanks. but i see that doesn′t work for SQL2k5? We have it :(regards|||Looks like I am getting this error message after installing service pack 1 on SQL 2005. So uninstall and re-install is the answer? I tried to repair the .NET 2.0 framework, but still get the error. Not sure if this is a show stopper, but this is a new server with fresh install of everything. I would hate to have an error like this cause problems in the future.|||
Hi,
Just come across this after seeing the same error in my event log during standard system reviews. I don't have any noticeable effects, but when reviewing the full sequence of .Net optimisations there are two distinct groupings of compilations, one where the version is clr_optimization_v2.0.50727_32 and one where the version is clr_optimization_v2.0.50727_64 . As I'm running an x64 box might it be that this error is not a problem as it seems to be occuring on the 32bit version of the optimisation and not on the 64bit version?
Would be interesting to know what systems people are running that this error is occuring on, 32bit or 64 bit.
HTH someone else.
Regards
Nick
DBA - United Co-op Ltd
MCDBA
|||I have the same problem, after Installing SQL 2005 SP1 on Clustermachines.
However my SQL-Cluster has a problem moving groups, which I hold responsible for failing to install the SP1 on the Database Engines.
I have 32 Bit Machines.
I find interesting though that my BTS 2006 Machines that use the SQL Servers have the same Problem too, even they don't have any SQL Server on it themselves.
Is it feasable to believe that the Problem is maybe in some other Patch we installed that affects the SQL Client Components?
I have also installed the Hotfix NDP20-KB918642-X86_bugfix.exe which is supposed to fix the annoying Shim Database Error Message (you know it?).
Any new suggestions, workarounds, patches?
Subscribe to:
Posts (Atom)