ASP.Net pages returning blank page on postback

Several of the webpages in my asp.net web application have started returning a blank page after postback. Either it happens when clicking a button to run a procedure (save), or by selecting a value from a dropdown list. This is new behavior. The only change to code that has happened lately is implementing PKI. It does not happen all of the time but it happens often enough that users are really complaining. One avenue I thought of is sessions. I noticed on one page that if I work thorough it and submit, it seems to work. If I step away or do something else for just a few minutes, when I come back and make a change to the form like select something from the dropdown list, I get the blank page. I've asked this question here before but have not gotten any responses. I've also asked several developers I know but still no go. Any help is appreciated.
dodgerfanAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
when you say you've implemented PKI infastructure and it broke your webpage, could you elaborate on what you mean as PKI in itself doesn't affect IIS or the operation of websites.
dodgerfanAuthor Commented:
The website has been up and running well for about 2 years now. I had to implement PKI on it this month. It's been PKI enabled for almost 2 weeks now. This behavior started shortly after the implementation. I have a function within the master page that takes in certificate information for each user (serial #, date of expiration) which is put into the user table and used for validation so users will no longer have to use a username and password. I'm not 100% sure it's because of PKI, but it is the only code change I've made recently. When it happens, if you refresh the page the page comes back but the changes you just made are gone and you have to start over.
dodgerfanAuthor Commented:
Found it finally: http://www.experts-exchange.com/Networking/Protocols/SSL/Q_24461827.html

It turns out that we needed to issue the following 2 statements from
the c:\inetpub\adminscripts directory to solve the problem:

cscript adsutil.vbs set w3svc/site#/uploadreadaheadsize 200000

and set the SSLAlwaysNegoClientCert value by issuing the following
command:

cscript adsutil.vbs set w3svc/site#/SSLAlwaysNegoClientCert true

where site# is the identifier number associated with the website.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dodgerfanAuthor Commented:
I found it here on experts exchange
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP.NET

From novice to tech pro — start learning today.