ERROR: Failure to compile WMI file

I received this error at the end of the "Reporting Services" setup.

I checked WMI process in Services and everything is OK, it's running.

So far I was able to install Designer Tools only (unchecking Report Manager and Report server).

All system components are up to date and SQL Server SP3 is installed.

I would highly appreciate it if somebody could help me out. It's now matter of survival to me.

Thanks in advance,

Confused Virginian

You also need SP3a to install Reporting Services. Hope this helps.|||

Caddre,

Thank you for your help. I already have SP3 installed.

Eventually I found the fix, right there:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/reinstalling_wmi.asp

This article explains how to recreate corrupted WMI repository.

Virginian

Error: 17805, Severity: 20, State: 3 Invalid buffer received from client.

Howdy Folks,
Our site has been experiencing this issue for a couple of months now.. Hopefully someone else can assist, as Ive got to a point where I think issue lies within the application or a Microsoft bug. Web searches have reveled a number installations that have also had this error but its has not revealed an actual fix.

I understand this error code basically means data being returned to the client is getting either corrupted or the data is too large to fit into the buffer on the client side. Client in our case is the terminal server, here after called a application server

As the user base has increased form 5 to 20, I have noticed that the issue is occurring more frequently in comparison to when the company first started using the application /database. Its just about daily now...

The db server also has 8 other db's residing on it - but they are all less than 300 meg.

The attached PowerPoint doc has the trace info & the surrounding code for each process that has suffered a buffer error over a period of a week.

DB Server Environment: Win2000 SP4, SQL2000 SP3a, MDAC 2.7 SP1 refresh.
Application Environment: Written In house in VB.NET Framework 1.1 setup as a published app on a terminal server running windows 2000 SP4

Common features of the issue, that have been omitted from trace output for visibility reasons are:
- Involves 1 particular DB (thats accessed by VB app) & its developement db
- All connections are coming from 1 application server
- Issue does not relate to any particular site connecting to the application server using this application

I have reviewed & fixed several potential server side causes but this error still is occuring with in the environment:

MDAC versions must be common on application & server:
- Removed from equation by updating MDAC version on App server to be the same as DB Server: 2.7 SP1 Refresh

Network related
- Considered unlikely; we are also not experiencing network card errors on either server; also all db's would be experiencing connectivity errors.

Which leaves us with Application related options to review:
- Compilation error of application
- App parameter definitions to stored procedures are the correct data type
- Ensure values being passed do not exceed 4000 characters as that has also been known to create this error message
- I've asked the developer to review MS KB 827366 article, as it may be a valid test
- In regard to MSKB 832977 - I am not using pssdiag & have a later version of the MS Analyzer. But what I thought was interesting, is the statement that this problem occurs more frequently when an application submits a large remote procedure call (RPC) input buffer, especially when the RPC input buffer is greater than or equal to 8 KB. However, this problem may occur even if the input buffer is less than 4 KB
- A is using datatypes varchar & char - not nvarchar & nhar

Any assistance with this issue would be appreicated as server performance is being effected - these processes hang around for 1 - 5 mins before terminating (refer duration times in the powerpoint traces)

Thanks In advance

Suze.I think Reads column referrs to physical reads. If that's the case then the number is pretty high and may be the reason for the client timeout. Sporadic behavior of the same query may be caused by inconsistent execution plan generated. Do you use dynamic SQL a lot?|||Thank you for your question...

The number of reads appears only on the first slide, the other 7 don't have any reads - just the really long duration.
Because of this long duration & the audit logout entry for the same process id directly after the buffer error, I've assumed that the process is timing out. But in saying that users are not reporting that they have been kicked out of the application or receiving any error messages - so maybe way off in that assumption.

We are using SP's passing in parameter's. The developer reckons this means its not being built at runtime. As you might be able to tell, I'm a newbie - so I don't know if this means they are dynamic sql or not... are you able to advise.

Best Regards|||The 4000-limit was revealed in my previous environment when SP3 was applied. The FE code was...of course, JAVA, what else can cause this. And they were parsing the call to the stored procedure without TYPEing the parameters, which resulted in every character-based parameter to be interpreted as NVARCHAR. Now, the article (827366) is also referring to the possibility of data type size misalignment, where the value supplied may be outside of the boundaries allowed for a specific data type (just a hunch).|||I like the sound of your hunch. Unfortunately I can't provide the developer any proof - being a newbie in all. Anyway, I think I've done the next best thing by sending the developer the MSKB article 827366 again & Ant profiler to use so he can see what his code is doing - hopefully this will give him the visibility he needs.

Thanks again & Best Regards
Suze.

Error: 17805, Severity: 20, State: 3

We are getting the following messages sporadically in the Event Viewer:
Error: 17805, Severity: 20, State: 3
Invalid buffer received from client.
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
without AWE enabled; however, we do have the -g256 startup parameter.
Any help would be greatly appreciated,
James
Have a look here:
http://support.microsoft.com/kb/891719
Andrew J. Kelly SQL MVP
"James" <James@.discussions.microsoft.com> wrote in message
news:75855665-46E4-4429-9B11-0B5C92773451@.microsoft.com...
> We are getting the following messages sporadically in the Event Viewer:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Error: 17803, Severity: 20, State: 12
> Insufficient memory available.
> We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
> without AWE enabled; however, we do have the -g256 startup parameter.
> Any help would be greatly appreciated,
> James
|||Refer
http://support.microsoft.com/default...b;en-us;896373
http://support.microsoft.com/kb/891719
Thanks & Rate the Postings.
-Ravi-
"James" wrote:

> We are getting the following messages sporadically in the Event Viewer:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Error: 17803, Severity: 20, State: 12
> Insufficient memory available.
> We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
> without AWE enabled; however, we do have the -g256 startup parameter.
> Any help would be greatly appreciated,
> James

Error: 17805, Severity: 20, State: 3

We are getting the following messages sporadically in the Event Viewer:
Error: 17805, Severity: 20, State: 3
Invalid buffer received from client.
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
without AWE enabled; however, we do have the -g256 startup parameter.
Any help would be greatly appreciated,
JamesHave a look here:
http://support.microsoft.com/kb/891719
Andrew J. Kelly SQL MVP
"James" <James@.discussions.microsoft.com> wrote in message
news:75855665-46E4-4429-9B11-0B5C92773451@.microsoft.com...
> We are getting the following messages sporadically in the Event Viewer:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Error: 17803, Severity: 20, State: 12
> Insufficient memory available.
> We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
> without AWE enabled; however, we do have the -g256 startup parameter.
> Any help would be greatly appreciated,
> James|||Refer
http://support.microsoft.com/defaul...kb;en-us;896373
http://support.microsoft.com/kb/891719
Thanks & Rate the Postings.
-Ravi-
"James" wrote:

> We are getting the following messages sporadically in the Event Viewer:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Error: 17803, Severity: 20, State: 12
> Insufficient memory available.
> We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
> without AWE enabled; however, we do have the -g256 startup parameter.
> Any help would be greatly appreciated,
> James

Error: 17805, Severity: 20, State: 3

We are getting the following messages sporadically in the Event Viewer:
Error: 17805, Severity: 20, State: 3
Invalid buffer received from client.
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
without AWE enabled; however, we do have the -g256 startup parameter.
Any help would be greatly appreciated,
JamesHave a look here:
http://support.microsoft.com/kb/891719
Andrew J. Kelly SQL MVP
"James" <James@.discussions.microsoft.com> wrote in message
news:75855665-46E4-4429-9B11-0B5C92773451@.microsoft.com...
> We are getting the following messages sporadically in the Event Viewer:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Error: 17803, Severity: 20, State: 12
> Insufficient memory available.
> We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
> without AWE enabled; however, we do have the -g256 startup parameter.
> Any help would be greatly appreciated,
> James|||Refer
http://support.microsoft.com/default.aspx?scid=kb;en-us;896373
http://support.microsoft.com/kb/891719
--
Thanks & Rate the Postings.
-Ravi-
"James" wrote:
> We are getting the following messages sporadically in the Event Viewer:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Error: 17803, Severity: 20, State: 12
> Insufficient memory available.
> We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
> without AWE enabled; however, we do have the -g256 startup parameter.
> Any help would be greatly appreciated,
> James

Error: "Invalid buffer received from client"

Hi,
We have a Java application with SQL 2000 db. Our
application was tested on MS SQL Server 2000 with SP3
installed (security patch MS03-031 was not installed). But
once the security patch(MS03-031) was installed, it
started giving the following error.
"2003-10-03 09:16:44.19 spid61 Error: 17805,
Severity: 20, State: 3
2003-10-03 09:35:04.46 spid68 Invalid buffer received
from client.."
on the SQL Server environment. This error is not
consistent. Now and then it is happening.
DB Server : SQL Server 2000 SP3 + MS03-031OS : :
Windows 2000 (Build 2195: Service Pack 2)We are using
JRUN/Tomcat as application server and using Microsoft JDBC
Driver Type 4 for connecting to the SQL Server. Our whole
application is on J2EE Architecture.
Please let me know if any of you have any solution for
this.
Thanks in advance.
Regards,
JPI had a quick search on Microsoft and found this :-
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q236447
not sure it will help as it was written for SQL 6.5. Worth a read though.
HTH
Ryan Waight, MCDBA, MCSE
"JP" <jobtechie@.yahoo.com> wrote in message
news:0faf01c38cd5$3282a010$a301280a@.phx.gbl...
> Hi,
> We have a Java application with SQL 2000 db. Our
> application was tested on MS SQL Server 2000 with SP3
> installed (security patch MS03-031 was not installed). But
> once the security patch(MS03-031) was installed, it
> started giving the following error.
> "2003-10-03 09:16:44.19 spid61 Error: 17805,
> Severity: 20, State: 3
> 2003-10-03 09:35:04.46 spid68 Invalid buffer received
> from client.."
> on the SQL Server environment. This error is not
> consistent. Now and then it is happening.
> DB Server : SQL Server 2000 SP3 + MS03-031OS : :
> Windows 2000 (Build 2195: Service Pack 2)We are using
> JRUN/Tomcat as application server and using Microsoft JDBC
> Driver Type 4 for connecting to the SQL Server. Our whole
> application is on J2EE Architecture.
> Please let me know if any of you have any solution for
> this.
> Thanks in advance.
> Regards,
> JP

Error with ole db

I created a view refer to a visual foxpro with ole db for visual foxpro which was working fine before. But now, I received an error while select the view

Msg 7302, Level 16, State 1, Line 1
Cannot create an instance of OLE DB provider "VFPOLEDB" for linked server "ORST3".

Please advise. Thanks in advance

Can you provide us with sample repro code for this issue?

Thanks

Error while upgrading SQL2005 Standard To SQL 2005 Enterprise

Hello,
I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
Enterprise. I received the following error message during the upgrade of
the database components.
Product: Microsoft SQL Server 2005 -- Error 29550. The
setup has encountered an error while Upgrading Components.
The error: -2147019873
Error message: The group or resource is not in the correct
state to perform the requested operation.
My customers ASPState Database is in simple recovery mode. I was not
sure if this is what could have caused this error. Also will i have to
start with a fresh install of SQL 2005 to resolve this issue?
Thanks for the help.I doubt that is it. Are any of the files, filegroups or dbs read only or in
other than OnLine mode? Do any of the dbs have a computability level of
less than 80?
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> Hello,
> I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
> Enterprise. I received the following error message during the upgrade of
> the database components.
>
> Product: Microsoft SQL Server 2005 -- Error 29550. The
> setup has encountered an error while Upgrading Components.
> The error: -2147019873
> Error message: The group or resource is not in the correct
> state to perform the requested operation.
> My customers ASPState Database is in simple recovery mode. I was not sure
> if this is what could have caused this error. Also will i have to start
> with a fresh install of SQL 2005 to resolve this issue?
> Thanks for the help.|||As far as i am aware all the files, filegroups are not in a read only
mode and all DB files are Online. As far as DB computability level i
will have to look into that.
Andrew J. Kelly wrote:
> I doubt that is it. Are any of the files, filegroups or dbs read only or i
n
> other than OnLine mode? Do any of the dbs have a computability level of
> less than 80?
>
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...[vbcol=seagreen]
SQL2005[vbcol=seagreen]
upgrade of[vbcol=seagreen]
not sure[vbcol=seagreen]
start[vbcol=seagreen]|||Also all DB files are currently set at compatibility level of 90.
Noah wrote:
> As far as i am aware all the files, filegroups are not in a read only
> mode and all DB files are Online. As far as DB computability level i
> will have to look into that.
> Andrew J. Kelly wrote:
> "Noah" <noah@.carpathiahost.com> wrote in message
> news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> SQL2005
> upgrade of
> not sure
> start
>|||I just reread your original post. You said "2 node". Is this a cluster? If
so the error is probably talking about the cluster resource group not SQL
Server. Try posting this in the Cluster newsgroup for a better answer.
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:et98dKD2HHA.3760@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Also all DB files are currently set at compatibility level of 90.
>
> Noah wrote:|||Andrew J. Kelly wrote:
> I just reread your original post. You said "2 node". Is this a cluster? I
f
> so the error is probably talking about the cluster resource group not SQL
> Server. Try posting this in the Cluster newsgroup for a better answer.
>
Will Do thanks.

Error while upgrading SQL2005 Standard To SQL 2005 Enterprise

Hello,
I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
Enterprise. I received the following error message during the upgrade of
the database components.
Product: Microsoft SQL Server 2005 -- Error 29550. The
setup has encountered an error while Upgrading Components.
The error: -2147019873
Error message: The group or resource is not in the correct
state to perform the requested operation.
My customers ASPState Database is in simple recovery mode. I was not
sure if this is what could have caused this error. Also will i have to
start with a fresh install of SQL 2005 to resolve this issue?
Thanks for the help.I doubt that is it. Are any of the files, filegroups or dbs read only or in
other than OnLine mode? Do any of the dbs have a computability level of
less than 80?
--
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> Hello,
> I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
> Enterprise. I received the following error message during the upgrade of
> the database components.
>
> Product: Microsoft SQL Server 2005 -- Error 29550. The
> setup has encountered an error while Upgrading Components.
> The error: -2147019873
> Error message: The group or resource is not in the correct
> state to perform the requested operation.
> My customers ASPState Database is in simple recovery mode. I was not sure
> if this is what could have caused this error. Also will i have to start
> with a fresh install of SQL 2005 to resolve this issue?
> Thanks for the help.|||As far as i am aware all the files, filegroups are not in a read only
mode and all DB files are Online. As far as DB computability level i
will have to look into that.
Andrew J. Kelly wrote:
> I doubt that is it. Are any of the files, filegroups or dbs read only or in
> other than OnLine mode? Do any of the dbs have a computability level of
> less than 80?
>
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> > Hello,
> >
> > I just recently tried to upgrade a two node SQL2005 Standard to
SQL2005
> > Enterprise. I received the following error message during the
upgrade of
> > the database components.
> >
> >
> >
> > Product: Microsoft SQL Server 2005 -- Error 29550. The
> > setup has encountered an error while Upgrading Components.
> > The error: -2147019873
> > Error message: The group or resource is not in the correct
> > state to perform the requested operation.
> >
> > My customers ASPState Database is in simple recovery mode. I was
not sure
> > if this is what could have caused this error. Also will i have to
start
> > with a fresh install of SQL 2005 to resolve this issue?
> >
> > Thanks for the help.|||Also all DB files are currently set at compatibility level of 90.
Noah wrote:
> As far as i am aware all the files, filegroups are not in a read only
> mode and all DB files are Online. As far as DB computability level i
> will have to look into that.
> Andrew J. Kelly wrote:
>> I doubt that is it. Are any of the files, filegroups or dbs read only
>> or in other than OnLine mode? Do any of the dbs have a computability
>> level of less than 80?
> "Noah" <noah@.carpathiahost.com> wrote in message
> news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> > > Hello,
> > >
> > > I just recently tried to upgrade a two node SQL2005 Standard to
> SQL2005
> > > Enterprise. I received the following error message during the
> upgrade of
> > > the database components.
> > >
> > >
> > >
> > > Product: Microsoft SQL Server 2005 -- Error 29550. The
> > > setup has encountered an error while Upgrading Components.
> > > The error: -2147019873
> > > Error message: The group or resource is not in the correct
> > > state to perform the requested operation.
> > >
> > > My customers ASPState Database is in simple recovery mode. I was
> not sure
> > > if this is what could have caused this error. Also will i have to
> start
> > > with a fresh install of SQL 2005 to resolve this issue?
> > >
> > > Thanks for the help.
>|||I just reread your original post. You said "2 node". Is this a cluster? If
so the error is probably talking about the cluster resource group not SQL
Server. Try posting this in the Cluster newsgroup for a better answer.
--
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:et98dKD2HHA.3760@.TK2MSFTNGP03.phx.gbl...
> Also all DB files are currently set at compatibility level of 90.
>
> Noah wrote:
>> As far as i am aware all the files, filegroups are not in a read only
>> mode and all DB files are Online. As far as DB computability level i will
>> have to look into that.
>> Andrew J. Kelly wrote:
>> I doubt that is it. Are any of the files, filegroups or dbs read only or
>> in other than OnLine mode? Do any of the dbs have a computability level
>> of less than 80?
>> "Noah" <noah@.carpathiahost.com> wrote in message
>> news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
>> > > Hello,
>> > >
>> > > I just recently tried to upgrade a two node SQL2005 Standard to
>> SQL2005
>> > > Enterprise. I received the following error message during the
>> upgrade of
>> > > the database components.
>> > >
>> > >
>> > >
>> > > Product: Microsoft SQL Server 2005 -- Error 29550. The
>> > > setup has encountered an error while Upgrading Components.
>> > > The error: -2147019873
>> > > Error message: The group or resource is not in the correct
>> > > state to perform the requested operation.
>> > >
>> > > My customers ASPState Database is in simple recovery mode. I was not
>> sure
>> > > if this is what could have caused this error. Also will i have to
>> start
>> > > with a fresh install of SQL 2005 to resolve this issue?
>> > >
>> > > Thanks for the help.|||Andrew J. Kelly wrote:
> I just reread your original post. You said "2 node". Is this a cluster? If
> so the error is probably talking about the cluster resource group not SQL
> Server. Try posting this in the Cluster newsgroup for a better answer.
>
Will Do thanks.

Error while upgrading SQL2005 Standard To SQL 2005 Enterprise

Hello,
I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
Enterprise. I received the following error message during the upgrade of
the database components.
Product: Microsoft SQL Server 2005 -- Error 29550. The
setup has encountered an error while Upgrading Components.
The error: -2147019873
Error message: The group or resource is not in the correct
state to perform the requested operation.
My customers ASPState Database is in simple recovery mode. I was not
sure if this is what could have caused this error. Also will i have to
start with a fresh install of SQL 2005 to resolve this issue?
Thanks for the help.
I doubt that is it. Are any of the files, filegroups or dbs read only or in
other than OnLine mode? Do any of the dbs have a computability level of
less than 80?
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> Hello,
> I just recently tried to upgrade a two node SQL2005 Standard to SQL2005
> Enterprise. I received the following error message during the upgrade of
> the database components.
>
> Product: Microsoft SQL Server 2005 -- Error 29550. The
> setup has encountered an error while Upgrading Components.
> The error: -2147019873
> Error message: The group or resource is not in the correct
> state to perform the requested operation.
> My customers ASPState Database is in simple recovery mode. I was not sure
> if this is what could have caused this error. Also will i have to start
> with a fresh install of SQL 2005 to resolve this issue?
> Thanks for the help.
|||As far as i am aware all the files, filegroups are not in a read only
mode and all DB files are Online. As far as DB computability level i
will have to look into that.
Andrew J. Kelly wrote:
> I doubt that is it. Are any of the files, filegroups or dbs read only or in
> other than OnLine mode? Do any of the dbs have a computability level of
> less than 80?
>
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...[vbcol=seagreen]
SQL2005[vbcol=seagreen]
upgrade of[vbcol=seagreen]
not sure[vbcol=seagreen]
start[vbcol=seagreen]
|||Also all DB files are currently set at compatibility level of 90.
Noah wrote:
> As far as i am aware all the files, filegroups are not in a read only
> mode and all DB files are Online. As far as DB computability level i
> will have to look into that.
> Andrew J. Kelly wrote:
> "Noah" <noah@.carpathiahost.com> wrote in message
> news:%23CP4Q2C2HHA.4004@.TK2MSFTNGP05.phx.gbl...
> SQL2005
> upgrade of
> not sure
> start
>
|||I just reread your original post. You said "2 node". Is this a cluster? If
so the error is probably talking about the cluster resource group not SQL
Server. Try posting this in the Cluster newsgroup for a better answer.
Andrew J. Kelly SQL MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:et98dKD2HHA.3760@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Also all DB files are currently set at compatibility level of 90.
>
> Noah wrote:
|||Andrew J. Kelly wrote:
> I just reread your original post. You said "2 node". Is this a cluster? If
> so the error is probably talking about the cluster resource group not SQL
> Server. Try posting this in the Cluster newsgroup for a better answer.
>
Will Do thanks.