System Exception(s) Error 1: Attempted to read or write protected memory. This is often an indication that other memory is corrupt

Hi,

Last night suddenly got an error "System Exception(s) Error 1: Attempted to read or write protected memory. This is often an indication that other memory is corrupt" when was uploading excel report to asp.net application.

No updates or software installed on this server. i disabled firewall and Antivirus and checked but no luck.

Asp.net application is on windows 2008 R2 server, IIS7.0, framework 4.0 and DB is SQL 2008 R2 standard server.

Can anyone tell me what is the issue exactly?
anuboggaramAsked:
Who is Participating?
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.

QuinnDexCommented:
this seems to be a very generic error message and on its own will not point you towards the source of the problem...

please post any other related error messages/stack trace or log entries that may give more information
0
anuboggaramAuthor Commented:
Log file indicates error "The resultSet is empty for a given sql or no records found."
0
anuboggaramAuthor Commented:
SQL error table is showing as :
A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

Rikin ShahMicrosoft Dynamics CRM ConsultantCommented:
Hi,

There is a connectivity problem with a previously opened session in SQL Server.
http://forums.asp.net/p/1433838/3223633.aspx

Try-
SqlConnection.ClearAllPools();

It resets (or empties) the connection pool. If there are connections in use at the time of the call, they are marked appropriately and will be discarded (instead of being returned to the pool) when Close is called on them.
0
anuboggaramAuthor Commented:
No solution found. We had to launch a new server and setup everything.
0

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
anuboggaramAuthor Commented:
solution was to launch new server
0
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
Microsoft SQL Server 2008

From novice to tech pro — start learning today.