Error retrieving service instance data

[ligerzerox]

I’ve got two .bps files that were working fine yesterday but both now fail to open. The only change I’m aware of is that I set both of these to run as a service yesterday.

---

Error retrieving service instance data: Error in deserializing body of reply message for operation ‘RetrieveSingleGridCopyAsXMLString’. The maximum string content length quota (8192) has been exceeded while reading XML data. This quota may be increased by changing the MaxStringContentLength property on the XmlDictionaryReaderQuotas object used when creating the XML reader.

---

[doug]

What kind of server are you experiencing this behavior on? Is it a web server? Is it running a non-standard edition of Windows? Is it your WSUS server?

I can confirm that this issue can only occur when the bps file is loaded into the service instance, and then the main BP instance tries to retrieve the data from the service instance in order to present the grid to you in the service instance viewer.

One other user had reported this, but it only occurred on one particular machine he was using, so he ended up using a different one. From our perspective it’s unclear why this is occurring, because we already set the value to be much larger than 8192. Additionally, the actual size of the XML data is generally going to be *much* smaller than that except in cases where the grid contains a *very* large amount of data. So, it’s unclear what causes this. We have so far simply not been able to reproduce the behavior. In theory, based on the error that is occurring, if you were to create just a single row .bps file as a test and then add it to service mode, that .bps file would be so small that it would not trigger the error. However, I suspect that in your case the error will still get triggered, and it’s unclear why. (Feel free to please test this and let me know what happens).

The bps file will continue to run the schedule while in service mode even if this error is occurring. The issue only occurs when BatchPatch tries to display the contents of the grid to you. However, removing the grid from service mode will certainly stop the error from occurring. Also, I suspect that if you run BP as a service on a different computer you will not see this error occur.

We will see what else can be done to prevent this from occurring.

-Doug

[ligerzerox]

Hey Doug, it’s a 2008R2 Standard edition server. It is also our WSUS/Symantec Endpoint Protection server. Removing the files from “service” listings allow me to open them again, but I did initially receive an error when I tried to remove them. Both files were showing under the “BatchPatch Service Instance: Currently active .bps files” section until I hit the “Refresh list” button to the right and then they disappeared. After that, it allowed me to remove them from the instance.

This is the error they kicked out:

Data: System.Collections.ListDictionaryInternal

InnerException:

Message: Index 0 is out of range.

Parameter name: index

Source: System.Windows.Forms

StackTrace: at System.Windows.Forms.Control.ControlCollection.get_Item(Int32 index)

at A.c26adf8ffe8bce34a0573c463e57da544.cfb6687a096644311a04188f21268daed_Encrypted$(c26adf8ffe8bce34a0573c463e57da544 , TabPage , Boolean )

at A.c26adf8ffe8bce34a0573c463e57da544.c3756cf9508a744a5546cdb32c6a2a935_Encrypted$(c26adf8ffe8bce34a0573c463e57da544 , String )

at A.c5324d953fd8f2f15a57ab1f42e74c6e9.c687219d9a81527b6972933d9f8918cb0_Encrypted$(c5324d953fd8f2f15a57ab1f42e74c6e9 , Object , EventArgs )

at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ButtonBase.WndProc(Message& m)

at System.Windows.Forms.Button.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

TargetSite: System.Windows.Forms.Control get_Item(Int32)

[doug]

Thanks. I believe this new/second error occurred only because the first issue was occurring. If/when we are able to fix the first issue, the second one should disappear.

Separately, I’m pretty confident that if you run BP as a service on a different machine that is not your WSUS server, you will not encounter either error, though we will still plan to have another look at this problem before next the version is released. Hopefully we can eliminate it altogether.

-Doug

[Author]

Posts