Framework ocx on Virtual Machines/Citrix

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   All,

We have a VB6 app which calls a .NET app. On our desktop workstations it works fine and both are skinned properly. However on Virtual Machines and Citrix environments the call to the .NET app sometimes (but not always) throws an error in the skin framework:

.NET Runtime 2.0 error
Event ID: 1000
Faulting application vb6caller.exe, version 1.0.0.0, stamp 4dffd44e, faulting module codejock.skinframework.v13.4.0.ocx, version 13.4.0.0, stamp 4c053575, debug? 0, fault address 0x00037e2b.

System Info:
Microsoft Windows Server 2003
Standard Edition
Service Pack 2
Intel Xeon 2.80 GHz
768 MB Ram

I’ve tried excluding .dlls from the skinning object and I don’t think it’s a memory issue as a desktop system with the same amount of RAM does not generate the error. I note that the PC’s CPU gets’ pegged at 100% when this happens. But I am not sure why. Memory allocation is not out of whack.
Thanks!

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
mnordmeyer Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 21 June 2011 Status: Offline Points: 1	Post Options Post Reply Quote mnordmeyer Report Post Thanks(0) Quote Reply Topic: Framework ocx on Virtual Machines/Citrix Posted: 21 June 2011 at 3:54pm
	All, We have a VB6 app which calls a .NET app. On our desktop workstations it works fine and both are skinned properly. However on Virtual Machines and Citrix environments the call to the .NET app sometimes (but not always) throws an error in the skin framework: .NET Runtime 2.0 error Event ID: 1000 Faulting application vb6caller.exe, version 1.0.0.0, stamp 4dffd44e, faulting module codejock.skinframework.v13.4.0.ocx, version 13.4.0.0, stamp 4c053575, debug? 0, fault address 0x00037e2b. System Info: Microsoft Windows Server 2003 Standard Edition Service Pack 2 Intel Xeon 2.80 GHz 768 MB Ram I’ve tried excluding .dlls from the skinning object and I don’t think it’s a memory issue as a desktop system with the same amount of RAM does not generate the error. I note that the PC’s CPU gets’ pegged at 100% when this happens. But I am not sure why. Memory allocation is not out of whack. Thanks!