Message
Access Denied.
Editing/Settings are NOT enabled even for administrators.
Context
SharePoint Site Collection, maybe after backup/restore a site collection
Explanation
The Site Collection is in "Read only" mode. Maybe due to a stsadm backup brutally interrupted.
Solution
Open the SharePoint Central Administration. Under Application Magement, click on the "Configure quotas and locks" link. Than have a look under the section "Site Lock Information" and be sure it is selected "Not locked" option.
A collection of common error messages with their solutions for saving time to those who are experiencing the same problems.
Wednesday, February 22, 2012
Monday, February 20, 2012
UnauthorizedAccessException opening UNC path file with FileStream
Message
UnauthorizedAccessException: Access to the path '...' is denied.
Context
Executing the following line of code (C# ASP.NET under Visual Studio, localFile or UNC path)
FileStream fs = new FileStream(fileName, FileMode.Open);
Explanation
ND
Solution
Add the fileaccess mode option "FileAccess.Read":
FileStream fs = new FileStream(fileName, FileMode.Open, FileAccess.Read);
Add the fileaccess mode option "FileAccess.Read":
FileStream fs = new FileStream(fileName, FileMode.Open, FileAccess.Read);
Monday, February 13, 2012
The Operation Could not be Completed
Message
Starting the debugger process (debugging) in Visual Studio after changing some settings (i.e. in the app.config file) it comes out a popup with the following message: The Operation Could not be completed.
Context
Debugging on Visual Studio 2008 or Visual Studio 2010
Explanation
Visual Studio doesn't delete the vshost.exe files in the application folder after launching debug. It looks like a Visual Studio bug. The vshost.exe files needs to be manually killed after debugging, or we need to close and reload the project.
Starting the debugger process (debugging) in Visual Studio after changing some settings (i.e. in the app.config file) it comes out a popup with the following message: The Operation Could not be completed.
Context
Debugging on Visual Studio 2008 or Visual Studio 2010
Explanation
Visual Studio doesn't delete the vshost.exe files in the application folder after launching debug. It looks like a Visual Studio bug. The vshost.exe files needs to be manually killed after debugging, or we need to close and reload the project.
Solution
Go to the Property window of your project, open the de "Debug" tab, look for the "Enable the Visual Studio hosting process" option and uncheck/disable that option.
Go to the Property window of your project, open the de "Debug" tab, look for the "Enable the Visual Studio hosting process" option and uncheck/disable that option.
Friday, February 10, 2012
Enabling IntelliSense for Client Object Model script in Visual Studio
Message
A simple way to enable/activate IntelliSense in Visual Studio while writing ECMA script. It allows, for example, to write your javascript or jQuery code for SharePoint saving you a lot of time.
Some references: http://msdn.microsoft.com/en-us/library/ff798328.aspx
Context
Visual Studio 2010, SharePoint 2010, Visual WebPart
Explanation
Solution
Add following lines at the start of the .ascx file in a visual webpart.
PS: Exclude these references while deploying the code to production environment.
A simple way to enable/activate IntelliSense in Visual Studio while writing ECMA script. It allows, for example, to write your javascript or jQuery code for SharePoint saving you a lot of time.
Some references: http://msdn.microsoft.com/en-us/library/ff798328.aspx
Context
Visual Studio 2010, SharePoint 2010, Visual WebPart
Explanation
Following is the list of debug .js files present in _layouts folder and depending upon the objects you are working with, you may need to add a reference to any of them to get IntelliSense.
- SP.debug.js (to get IntelliSense on list objects)
- SP.Core.debug.js
- SP.Ribbon.debug.js
- SP.Runtime.debug.js
- JsGrid.debug.js
- JsGrid.Gantt.debug.js
Solution
Add following lines at the start of the .ascx file in a visual webpart.
<script type="text/javascript" src="/_layouts/MicrosoftAjax.js"></script>
<script type="text/javascript" src="/_layouts/SP.Debug.js"></script>
<script type="text/javascript" src="/_layouts/SP.Core.debug.js">
Sunday, February 5, 2012
The remote computer disconnected the session because of an error in the licensing protocol
Message
The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator.
Context
Windows XP
Explanation
ND
Solution
Create a backup of the MSLicensing registry key and its subkeys on the client, and then remove the original key and subkeys by doing the following:
Create a backup of the MSLicensing registry key and its subkeys on the client, and then remove the original key and subkeys by doing the following:
- On the client, navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing.
- Click MSLicensing.
- On the Registry menu, click Export Registry File.
- In the File name box, type mslicensingbackup, and then click Save.
- If you need to restore this registry key in the future, double-click mslicensingbackup.reg.
- On the Edit menu, click Delete, and then click Yes to confirm the deletion of the MSLicensing registry subkey.
- Close Registry Editor, and then restart the computer.
Subscribe to:
Posts (Atom)