Answered by:
.NET Runtime version 4.0.30319.18444 - There was a failure initializing profiling API.

-
Hello,
I have a Windows Server 2008 R2 SP1 Standard edition and this 1022 error shows up in the event logs:
.NET Runtime version 4.0.30319.18444 - There was a failure initializing profiling API attach infrastructure. This process will not allow a profiler to attach. HRESULT: 0x80004005. Process ID (decimal): 6384. Message ID: [0x2509].
This server is a SharePoint 2010 server with about 10-15 concurrent users. Most users experience a credential pop-up message asking them for account information. Some users can’t login even if they enter in correct account information. Some users enter in their account information, and they can access SharePoint sites. Some users see this message more than others. For some users, they can access SharePoint resources fine for a few days, but then see SharePoint ask for credentials when they could access the resources just fine the day before.
The reason I mention this that when users get a pop-up for credential, this .Net Runtime error 1022 appears in the event log at the same time.
SharePoint is configured to use NTLM.
I am thinking this is not a SharePoint problem, but a Windows server issue. However, I really don’t know for sure.
I have run the .Net Framework Setup Verification Utility for .Net 4.0 Full. The utility has verified the product is installed correctly.
So, I am stuck on what is going on? Can anybody help?
Paul
Question
Answers
-
This one may help. The process ID 6384 may be the culprit.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.- Marked as answer by Mandy YeModerator Wednesday, April 23, 2014 9:29 AM
All replies
-
This one may help. The process ID 6384 may be the culprit.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.- Marked as answer by Mandy YeModerator Wednesday, April 23, 2014 9:29 AM
-
I just experienced this same error code, and it appeared at two minute intervals according to the event log. I could tell from the start and end time of the problem that what I was doing was copying a folder containing around 130GB of images from my External Drive to my C: Drive at that time, though why that should have this effect I have no idea, I'm afraid such things are way beyong my abilities.
The error messages ceased when the copying stopped, so whether that can help to offer any clues to the causes of this problem I don't know, it might be interesting to see if the other user has any programs running a back up to another drive at the 30 minute intervals when the error messages are appearing?