Visual Studio Debugger Error: The web server process that was being debugged has been terminated by Internet Information Services (IIS). This can be avoided by configuring Application Pool ping settings in IIS. See help for further details.

STEP to fix this:

Run Internet Information Services (IIS) [ if you don’t know then follow the steps to find it.]

1.       Open the Administrative Tools window.

2.       Click Start and then choose Control Panel.

3.       In Control Panel, choose Switch to Classic View, if necessary, and then double-click Administrative Tools.

4.       In the Administrative Tools window, double-click Internet Information Services (IIS) Manager.

5.       In the Internet Information Services (IIS) Manager window, expand the node.

6.       Under the node, right-click Application Pools.

7.       In the Application Pools list, right-click the name of the pool your application runs in, and then click Advanced Settings.

8.       In the Advanced Settings dialog box, locate the Process Model section and chose one of the following actions:

 *.Set Ping Enabled to False.

—or—

*.Set Ping Maximum Response Time to a value greater than 90 seconds.

Explanation:

Setting Ping Enabled to False stops IIS from checking whether the worker process is still running and keeps the worker process alive until you stop your debugged process. Setting Ping Maximum Response Time to a large value allows IIS to continue monitoring the worker process.

9.       Click OK.

OWSTimer unhandled exception popup – System.Security.Cryptographic.CryptographicException

Here’s the resulting event log error:

An unhandled exception occurred and the process was terminated.

Application ID: DefaultDomain
Process ID: 6148
Exception: System.Security.Cryptography.CryptographicException
Message: Keyset does not exist
StackTrace: at System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException(Int32 hr)
at System.Security.Cryptography.SafeProvHandle._FreeCSP(IntPtr pProvCtx)
at System.Security.Cryptography.SafeProvHandle.ReleaseHandle()
at System.Runtime.InteropServices.SafeHandle.InternalFinalize()
at System.Runtime.InteropServices.SafeHandle.Dispose(Boolean disposing)
at System.Runtime.InteropServices.SafeHandle.Finalize()

Cause of the error is when SharePoint 2010 and Visual Studio 2010 are both installed on the same machine you may see this error every 24 hours. This occurs when the OWSTimer service has a regular process recycle and in the shutdown of the old process an exception is raised. The exception doesn’t interfere with the normal process shutdown and recycle and is only ever seen if you have a JIT debugger installed on the machine.

You can ignore these exceptions and close the window.

You can stop the popup exception message by disabling JIT debugging on your machine. THIS WILL DISABLE JIT DEBUGGING FOR ALL APPLICATION ON THE MACHINE.

Follow the steps to configure the server  which will not show a dialog when an unhandled exception occurs, use the registry editor to delete the following registry keys:

· HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger
· HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger

On a 64-bit operating system also delete the following registry keys:

· HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

· HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\DbgManagedDebugger

More details on JIT Debugging are at:

http://msdn.microsoft.com/en-us/library/5hs4b7a6(VS.80).aspx

SharePoint Connection Error

--------------------
SharePoint Connection Error
--------------------
Cannot connect to the SharePoint Site: http://yoursharepointsite. Make sure that the site URL is valid, that the Sharrepoint si running on the local computer, and that the current user has the necessary permissions to access the site.

Additional information:

"Cannot connect to the SharePoint site: http://yoursharepointsite.. Make sure that this is a valid URL and the SharePoint site is running on the local computer. If you moved this project to a new computer or if the URL of the SharePoint site has changed since you created the project, update the site URL property of the project."

Resolution to this problem is.

1. Add current user as FARM administrator.
2. Add user as Site Collection administrator.
3. Give user permission on Database as DBO and DBO.OWNER on SharePoint_Config Database and site collection Content Database.

This will resolve the issue.

SPSecurity referance in Sandbox solution.

SPSecurity.RunWithElevatedPrivileges
is not available in Sandbox solution.

Read below referance from Microsoft.

http://msdn.microsoft.com/en-us/library/gg615454.aspx

Use the ‘Comments’ form to share your thoughts.

Show Quick Launch on SharePoint 2010 Custom Webpart Page

When you create a webpart page on SharePoint 2010 by default it will not have the quick launch will vanish.

All you needed to do is edit the page in SharePoint Designer and remove the following lines:


< asp:Content ContentPlaceHolderId="PlaceHolderNavSpacer" runat="server">
< asp:Content ContentPlaceHolderId="PlaceHolderLeftNavBar" runat="server">

You also need to delete the following:

< style type="text/css">
body #s4-leftpanel {
display:none;
}
.s4-ca {
margin-left:0px;
}


Done. Now refresh the page and the quick launch will now display on the web part page.