After updating to Enterprise Library 6: Transient Fault Handling I am getting a System.Security.VerificationException when my console application attempts to start up.
After doing some research I came across this similar issue on the CodePlex site for the Patterns and Practices group related to the Enterprise Library.
There seems to be a known issue at release time:
If you are using the Transient Fault Handling Application Block, you should ensure that you are using version 4.0.30319.18003 or later of mscorlib.dll, otherwise you may see a VerificationException exception at run time. For more information, see http://support.microsoft.com/kb/2748646.
The solution to the problem seems to indicate that this is an issue with the mscorlib version that is currently in use and there is a hotfix that will resolve the issue.
There is another KB, 2748645, for Windows 7, Windows 7 SP1, Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Server 2008 SP2, and Windows Vista SP2:
Related
I am running and supporting a PowerBuilder 11.2 application running in windows 7 64bit environment. The previous version of this program ran without a problem, and 99% of this new program runs without a problem. However, when I run a specific bit of functionality, at times the program throws an exception "Sybase PowerBuilder 11.0 has stopped working" Problem event name APPCRASH Application Name PB110.EXE, Fault Module Name PBSHR110.dll, Exception code c0000005 in the dev environment. In the compiled version running on the client machine the error "A breakpoint in an application indicates a program error. After this dialog is dismissed, the application will continue to run, but it may be in an unstable state" and the program closes
There are shared PBL files throughout this whole application. It is a framework that supports 6 MDI programs. I have performed a full build on the main objects and it compiles without error. The other programs that in the framework that use these common objects to not have this problem. I have tried to step through the code doing a debug, but when I step through the code, it does not crash.
I have re-installed PB 11.0 and the PB 11.2 upgrade again and of course rebooted numerous times. I am at a loss here. I have tried everything that worked before and have spent over a week trying to find something online, so I am now appealing to the group. Any help at all will be so very much appreciated. Until then, I'll keep trying.
Thanks.
John
It could be that PB 11.2 is not listed as being supported on Windows 7. A lot of times you can get lucky, and most applications will still work on unsupported OS's. Yet, an update may be released that breaks something. You may want to try downloading the latest release of PB which is 12.6 and migrate a copy of your application to that version. You will at least be able to rule out if that is the issue or not.
Enclosed is Sybase PowerBuilder Enterprise version 11.2, which is
compatible with the following platform and operating system
configurations:
Microsoft Windows XP with Service Pack 2
Microsoft Windows XP Tablet PC Edition with Service Pack 2
Microsoft Windows Server 2003 with Service Pack 1
Microsoft Windows Vista Business Edition
PowerBuilder 11.2 builds 32-bit applications, but supports deployed
applications in both 32-bit and 64-bit environments on the Vista
operating system. For more information about using PowerBuilder on the
Vista operating system, see “Vista Support” in the online Help. For a
list of issues that have been found on the Vista operating system, see
“Vista issues”.
Microsoft Windows 2000 with Service Pack 4 is supported for deployment
only. All support for this platform will be discontinued in future
releases of PowerBuilder.
Physical Hard Drive is shown "uninitialized" in windows server 2008 even after reboot and I am not able to initialize the disk using Disk Manager or DiskPart.
Any solution for windows server 2008. There is a hotfix 840781 addresses the issue specifically for windows server 2003. Is there a similar hotfix available for windows server 2008?
Thanks
Abhishek
I could not find any hotfix addressing this issue for windows 2008. However, I have jut updated my windows (Control Panel >> Windows Updates >> Install Updates) and issue is resolved for now.. I am not sure if this will arise in future...
I've been reading about the GUIDs changing for ADO/MDAC in Windows 7 service pack1 for VB6 apps. I need to recopile my compontents and replace the deprecated ones with the new one. My question is if my VB6 app is only going to be installed on windows 7 with service pack 1 or windows 2008 with the latest service pack will my VB6 app still work or do I still need to install something else too?
The updates you need to fix this problem are here.
This blog post explains a bit more about what happened and how they DRASTICALLY (Microsoft's emphasis) underestimated the number of developers that would be re-compiling ADO applications on Win7 SP1.
I have a Visual Studio 2010 Windows Forms application in which I start a transaction using the TransactionScope class. I then Receive a message from a Sql Server Broker Services message queue, which works fine. I next try to call a stored procedure from the same database with a call to my data access layer which is a Visual Studio dataset (xsd file). When I make this second call to the database I get the following error message:
The MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers. (Exception from HRESULT: 0x8004D02B).
I've seen several posts on the web that talk about Enabling DTC access through dcomcnfg.exe, and allowing DTC to communicate through Windows Firewall. I've done those things, and am still having this problem. I know our remote database server is setup to Enable DTC access, because we are using similar transactions in other projects built with Visual Studio 2008 on Windows XP and Vista. I think there is something specific about Windows 7 and Visual Studio 2010 causing this problem, but haven't been able to find out what it is. Can anyone help with this problem?
I just saw a post on the web from another programmer having this problem (http://www.pcreview.co.uk/forums/thread-3977150.php), he says it works fine on Windows 7 - x86, but gets this error on Windows 7 - x64. I'm running the x64 version of Windows 7, does anyone know if there are problems with MSDTC on Windows 7 - 64 bit version?
It turned out that I was leaving a database connection open in my Receive call to the SQL Server Service Broker, then trying to make a new connection to my data access layer. That was causing the problem, the fix turned out to be to close the first connection before opening the second one.
I have a Windows 2008 R2 server running on a VM machine.
My .NET service is running on this server periodically querying WMI, for example:
SELECT ProcessId FROM Win32_Service WHERE ...
After a day or two WMIprvse takes up to 500M memory and WMI queries start getting out of memory exceptions.
This article seems to be talking about this issue:
"http://support.microsoft.com/kb/958124"
I've seen other articles saying that Microsoft is aware of the problem and not going to issue a fix until the next major release.
http://social.msdn.microsoft.com/Forums/en/netfxbcl/thread/256eb40c-d050-4278-a3d8-863e30db02a0
I'd appreciate any suggestions and insights on this.
Check out both the following KB articles,
KB981314 - The "Win32_Service" WMI class leaks memory in Windows
Server 2008 R2 and in Windows 7 -
http://support.microsoft.com/kb/981314/en-us?p=1
KB977357 - A memory leak issue occurs in the Windows Management
Instrumentation service on a computer that is running Windows Server
2008 R2 or Windows 7 - http://support.microsoft.com/kb/977357
...but also worth noting we are on Windows 2008 R2 with SP1 (file versions higher than those provided by both hotfixes) and we are still seeing some slow memory leak issues possibly from either WMIAPSRV.exe and/or TRUSTEDINSTALLER.exe.
We are going to open a support call, if we find anything relevant will post the answer.
There is a hotfix available, but you have to request it by clicking on the link to request the hotfix at the top of the page.
Hotfix