No IO code

[simplecontrol]

Getting the following error as of the last reboot:

3/23/2012 5:18:52 PM - Plug-In - Initializing Plug-in: Current Cost on COM port 10
3/23/2012 5:18:52 PM - Current Cost - Warning, could not get an IO Code (0): Insufficient system resources exist to complete the requested service.
3/23/2012 5:18:52 PM - Current Cost - Warning: Could not configure plugin: Insufficient system resources exist to complete the requested service.
3/23/2012 5:18:52 PM - Error - Initializing interface: Current Cost->Insufficient system resources exist to complete the requested service.
3/23/2012 5:18:52 PM - Plug-In - Finished initializing plug-in Current Cost

Using the Current Cost terminal program everything looks fine. XML comes through with no issues on Com10.

I've unistalled/reinstalled the USB/Serial driver, updated HS, unistalled and reinstalled the plugin with no luck.

Any ideas on where to go next?

[Rupp]

What version of HS are you running? What hardware are you running HS on? How much ram? How much free drive space?

[simplecontrol]

Been running 2.5.0.23, upgraded to 2.5.0.52 (no change), back to 2.5.0.23.
MB is D510MO dual core 1.6Ghz
2Gig of ram with usually 1.3 available memory,
130G of available HD space.
HS handles never rise above 1650

I've also run a mem test and everything looks good there.

[Rupp]

This can also be caused by your USB drivers becoming corrupted. Try re-installing the drivers for the device. You did shut down the Current Cost terminal program that may have a connection to port 10. Have you loaded any new software on this pc lately. I've seen some reported issues like this in the past that boiled down to a trojan/virus so you may need to check that as well. Lastly search google for "Insufficient system resources exist to complete the requested service" and you will get a lot of information. Also try:
site:board.homeseer.com Insufficient system resources exist to complete the requested service

[simplecontrol]

The terminal program was shut down. I tried reinstalling the USB/Serial drivers, no luck. Don't understand if the USB drivers were corrupted how the terminal program could connect with no problem.

I did find this entry in the Event Viewer right before the problem started with the Current Cost plugin

User: N/A
Computer: SERVER
Description:
EventType clr20r3, P1 homeseer.exe, P2 2.5.0.23, P3 4dd6a119, P4 mscorlib, P5 2.0.0.0, P6 4333ab80, P7 32f8, P8 26d, P9 system.io.ioexception, P10 NIL.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 68 00 6f 00 6d 00 .h.o.m.
0018: 65 00 73 00 65 00 65 00 e.s.e.e.
0020: 72 00 2e 00 65 00 78 00 r...e.x.
0028: 65 00 2c 00 20 00 32 00 e.,. .2.
0030: 2e 00 35 00 2e 00 30 00 ..5...0.
0038: 2e 00 32 00 33 00 2c 00 ..2.3.,.
0040: 20 00 34 00 64 00 64 00 .4.d.d.
0048: 36 00 61 00 31 00 31 00 6.a.1.1.
0050: 39 00 2c 00 20 00 6d 00 9.,. .m.
0058: 73 00 63 00 6f 00 72 00 s.c.o.r.
0060: 6c 00 69 00 62 00 2c 00 l.i.b.,.
0068: 20 00 32 00 2e 00 30 00 .2...0.
0070: 2e 00 30 00 2e 00 30 00 ..0...0.
0078: 2c 00 20 00 34 00 33 00 ,. .4.3.
0080: 33 00 33 00 61 00 62 00 3.3.a.b.
0088: 38 00 30 00 2c 00 20 00 8.0.,. .
0090: 33 00 32 00 66 00 38 00 3.2.f.8.
0098: 2c 00 20 00 32 00 36 00 ,. .2.6.
00a0: 64 00 2c 00 20 00 73 00 d.,. .s.
00a8: 79 00 73 00 74 00 65 00 y.s.t.e.
00b0: 6d 00 2e 00 69 00 6f 00 m...i.o.
00b8: 2e 00 69 00 6f 00 65 00 ..i.o.e.
00c0: 78 00 63 00 65 00 70 00 x.c.e.p.
00c8: 74 00 69 00 6f 00 6e 00 t.i.o.n.
00d0: 20 00 4e 00 49 00 4c 00 .N.I.L.
00d8: 0d 00 0a 00 ....

I'll run a virus scan.

[Rupp]

Good point on the drivers. That error from the event viewer indicates that your 2.0 .net configuration has become corrupt. Try doing a repair on your Microsoft 2.0 .net framework.

[simplecontrol]

Virus scan can back clean. Repaired the Net 2.0 framework, still have the resource error. As another test I installed the 3P Current Cost plugin. It's working with no problem. I've redownloaded from the updater three times and repaired, removed, installed and rebooted with the same error message.