Showing posts with label Errors. Show all posts
Showing posts with label Errors. Show all posts

Wednesday, July 28, 2010

'standardEndpoints' cannot be read because it is missing a section declaration

I just tried to publish my first WCF RESTful service to our 2k8 box, and hit the wall with the following error:

The configuration section 'standardEndpoints' cannot be read because it is missing a section declaration


Well, after much searching, trying different options, reconfiguring, reading documentation, I finally found a post that should clear it out:

NET 4.0 Beta1/Beta2 Web Application Configuration section missing declaration error

http://support.microsoft.com/kb/958854/en-us

Appearently, on a windows server 2008 box, most .net 40 stuff works (well stuff that I've tried), but a couple of the items were missed. I didn't see an sp2 for win2k8 in the updates, so I downloaded and ran the HotFix. And what do you know? That worked. I've seen a bunch of posts on how to fix this error. This might just be the solution you're looking for.

Thursday, February 14, 2008

objectdisposedexception Fixed!

I found the problem, and posted the solution on a comment field in one of the previous posts. But here it is. Our server was running the latest fixes, however, my client access was not updated to the latest service pack. Our Operations manager, gave me this link to IBMs site to install the service pack on my local windows machine, and it works.

ftp://ftp.software.ibm.com/as400/products/clientaccess/win32/

Then select v5r4m0 (or what ever version you are running), servicepack, and si29771.

Download si29771.exe and run it on your system. Poof! Now you no longer get the objectdisposedexception, and no more errors with ThreadPool.RegisterWaitForSingleObject

Hope this helps!

Friday, December 28, 2007

objectdisposedexception - Safe handle has been closed

It's been a while since I've posted, and here is my current issue. I'm writting a call from an asp.net webservice to an IBM as/400 storedproc via IBM's "IBM DB2 UDB for iSeries .NET Provider"

It works great! I have a stored procedure on the iSeries system that calls an internal program. I can make the call. However, when my project stops or closes down, I get an ObjectDisposedException, "Safe handle has been closed" I've seen a few posts here and there about it, and finally stumbled across this bit from IBM:

SE22506 - CA400EXP-IDB2DATA .NET PROVIDER WITH .NET FRAMEWORK 2.0
At least they have a patch. Though, I don't know how long it will take our team to get the patch installed, tested and move to production. Well, hopefully it won't take long.

But in any case, at least now I have a path to go down. And according to their records it will work on V5R2M0, V5R3M0, and V5R4M0. We'll see I guess.

If anyone has some other method for working around this error, I'd love to hear about it.