# Wednesday, February 24, 2010

If you have already begun installing the SharePoint Server 2010 Beta on Microsoft Windows Server 2008 R2 you may have already encountered the following error when provisioning Service Applications or when accessing pages that make service calls:

Exception details:
System.Configuration.ConfigurationErrorsException: Unrecognized attribute 'allowInsecureTransport'. Note that attribute names are case-sensitive

To resolve this issue you will need to download the KB976462 hotfix which can be found at

http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=23806.

posted on Wednesday, February 24, 2010 2:15:37 PM (GMT Standard Time, UTC+00:00)  #    Comments [1] Trackback
# Monday, February 22, 2010

If you type SPSecurity, Visual Studio 2010's intellisense does not recognize it as a valid object, but once you type the entire line out, Visual Studio won't add the red underlined squiggle line indicating a syntax error. This is because when creating sandboxed solutions, you are still building against the full Sharepoint Object Model, but Visual Studio uses a different intellisense file to help the developer know which objects they will not have access to when the component runs in the sandboz.

Your sandboxed solution cannot include a reference to the SPSecurity type. If you use similar to following syntax

SPSecurity.RunWithElevated Priviliges(delegate
{
   //Your Code
});

You show the error like

posted on Monday, February 22, 2010 12:02:16 PM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback
# Monday, January 11, 2010

Resolution

  • Go to the windows directory and find the TEMP folder. (c:\windows\TEMP) Right click the TEMP folder and select the security tab.
  • Click the add button for adding a new user. Write the name "network service". Give Read/Write rights and click OK.
  • Go to the location c:\windows\system32\Logfiles. Write the name "network service". Give Read/Write rights and click OK.
posted on Monday, January 11, 2010 2:19:53 PM (GMT Standard Time, UTC+00:00)  #    Comments [1] Trackback

Error : "Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (The item was deleted because it was either not found or the crawler was denied access to it.)"

Solution :

  • Click Start, click Run, type regedit, and then click OK.
  • In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  • Right-click Lsa, point to New, and then click DWORD Value.
  • Type DisableLoopbackCheck, and then press ENTER.
  • Right-click DisableLoopbackCheck, and then click Modify.
  • In the Value data box, type 1, and then click OK.
  • Quit Registry Editor, and then restart your computer.
posted on Monday, January 11, 2010 1:17:51 PM (GMT Standard Time, UTC+00:00)  #    Comments [1] Trackback

Sometimes Office Sharepoint Server Search service is hanged it is showing in "starting" state there is no stop,start or restart option in services.msc console. You can restart your server, but problem still continue.

You can try the following stsadm commands to fix it.

stsadm -o osearch -action start 
stsadm -o osearch -action stop
net stop oSearch
net start oSearch

But sometimes problem still continue too, then try this command

psconfig -cmd services -install

posted on Monday, January 11, 2010 1:11:29 PM (GMT Standard Time, UTC+00:00)  #    Comments [1] Trackback
# Tuesday, January 05, 2010

You can't install SharePoint 2010 on Microsoft Virtual PC as it needs 64 bit Platform. As of now, Microsoft Virtual PC don’t support 64 bit operating system guest.

posted on Tuesday, January 05, 2010 12:16:47 PM (GMT Standard Time, UTC+00:00)  #    Comments [1] Trackback
# Monday, December 14, 2009

If you cannot open or build an Office InfoPath project in Visual Studio under source control, you need to read this KB article: http://support.microsoft.com/default.aspx?scid=kb;en-us;887039

Not mentioned in the KB article, is that when you try to build, this error will show as:

 

The "UpdateInfoPathManifest" task failed unexpectedly. System.UnauthorizedAccessException: Access to the path '<projectdir>\InfoPath Form Template\manifest.xsf' is denied."

 

To fix this problem, check-out the manifest.xsf for edit.

Thanks to Ryan Beesley

posted on Monday, December 14, 2009 11:39:45 AM (GMT Standard Time, UTC+00:00)  #    Comments [1] Trackback
# Monday, October 05, 2009

I read a post in DotNetMafia(Corey Roth) that describes a stupid error in Infopath Form Templates in Visual Studio 2008 with TFS

 "As you are working, you might come to a point where you receive an error like the following when trying to save your file.

InfoPath cannot save the following form: InfoPath Form Template.  The form is read-only.

When this occurs, it really is a bad time because every time I have received it, the form was already checked out and not marked read only.  The only solution I have found for this is to close Visual Studio and restart it.  This can be particularly frustrating when you have made a bunch of changes to the form template as you will end up losing them.  For this reason, I have made a practice of attempting to save the form, before I start making any changes to it."

 You can read the full post via this link

posted on Monday, October 05, 2009 11:38:27 AM (GMT Daylight Time, UTC+01:00)  #    Comments [3] Trackback
# Saturday, April 18, 2009

If you get the error says "Cannot deserialize the Web Part" i think your wss is running underNetwork Service credentials. I f that is the case you can do the following steps

   -  Go to C:\WINDOWS\Temp directory

   -  Right click the folder and click security tab.  In security tab add user named "Network Service"and give it Read/Write permissions

   -  Go to C:\WINDOWS\system32\Logfiles directory 

   -  Right click the folder and click security tab.  In security tab add user named "Network Service"and give it Read/Write permissions 

posted on Saturday, April 18, 2009 11:10:00 AM (GMT Daylight Time, UTC+01:00)  #    Comments [0] Trackback

You cannot browse a Secure Sockets Layer (SSL)-secured Microsoft Office SharePoint Server 2007 site or to the Search Settings page for a Shared Services Provider (SSP). Additionally, when you examine the Application log on the server in the server farm that is running Office SharePoint Server 2007, you see that an Error event ID 6482 was logged every minute.

This issue occurs when the following conditions are true:

   -   The server that is running Office SharePoint Server 2007 has the query role in a server farm.

   -   The server farm was updated with Microsoft .NET Framework 3.5 Service Pack 1 (SP1).

   -   The roles of the query server and the index server are not on the same server in the server farm

To resolve this issue, follow these steps:

    Stop the Windows SharePoint Services Search service. To do this, follow these steps:
      Click Start, click Run, type cmd , and then click OK.At the command prompt, type net stop osearch, and then press ENTER.Type exit to exit the command prompt.
    Download and install the IIS 6.0 Resource Kit Tools. To obtain the IIS 6.0 Resource Kit Tools, visit the following Microsoft Web site: http://www.microsoft.com/downloads/details.aspx?familyid=56FC92EE-A71A-4C73-B628-ADE629C89499 On each server in the farm that has Office SharePoint 2007 installed, follow these steps:
      Click Start, click Run, type cmd , and then click OK.At the command prompt, type selfssl /s:951338967 /v:1000, and then press ENTER. 

      Notes
        951338967 is the default ID of the Office Server Web Services certificate.1000 is the number of days that the certification will be valid.
    Start the Windows SharePoint Services Search service. To do this, follow these steps:
      At the command prompt, type net start osearch, and then press ENTER.Type exit to exit the command prompt.
    Download and install the following update to the .NET Framework 3.5 SP1. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 959209  An update for the .NET Framework 3.5 Service Pack 1 is available
posted on Saturday, April 18, 2009 11:09:32 AM (GMT Daylight Time, UTC+01:00)  #    Comments [0] Trackback
# Friday, April 17, 2009

If you create a workflow with using Microsoft Office Sharepoint Designer 2007, and you want to use "Send an EMail Activity" to send task reminders, workflow success reports, etc sometimes Sharepoint Designer does not allow you to copy other Send an EMail activities content. If you just create long HTML content to an activity you want to copy and paste it too.

If you have this issue clear the look-up references on your Send an EMail Activities content and try again. Now you can copy the content and paste it to your new activities body.

posted on Friday, April 17, 2009 11:08:44 AM (GMT Daylight Time, UTC+01:00)  #    Comments [0] Trackback
# Wednesday, March 25, 2009

After you install Windows SharePoint Services 3.0 SP1, declarative workflows will not start automatically if the following conditions are true:

1. The Windows SharePoint Services Web application runs under a user's domain account.
2. The user logs in by using this domain account.
3. The site displays the user name as System Account.

Here is the link to the solution : 
http://kbalertz.com/947284/declarative-workflow-start-automatically-after-install-Windows-SharePoint-Services-Service.aspx
 

posted on Wednesday, March 25, 2009 9:56:32 AM (GMT Standard Time, UTC+00:00)  #    Comments [2] Trackback
# Thursday, February 12, 2009

If your Sharepoint site always prompts for username/password on accessing it you can set your browser to not prompt

- In Internet Explorer, go to Tools
- Click Internet Options
- Open Security tab
- Click Custom Level button
- Scroll down to this screen and select "Automatic logon with current username and password" radiobutton
- Click OK.

Or, if you add your site's internal zone URL in Alternate Access Mappings section on Central Administration>Operations site, you can add your site url to Internet Explorers "Local Intranet Sites" section. And Sharepoint does not prompt for username/password.
posted on Thursday, February 12, 2009 9:47:26 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

Sometimes you want to backup a sharepoint site or farm you can get an error that says 

"The backup/restore job failed because there is already another job scheduled. Delete the timer job from the Timer Job Definitions page, and then restart the backup/restore job."

You must delete the Backup/Restore timer job after any failed backup or restore operation (such as an access denied error) before you can submit a new backup or restore request. SharePoint reports a conflict with the existing timer job until you delete it, preventing you from proceeding. 

You can view SharePoint timer jobs in the Central Administration site’s Timer Job Definitions page, which you can access by clicking the Timer Job Definitions link in the Global Configuration section on the Operations page.  After you open the Timer Job Definitions page a linked entry is displayed in the page titled Backup/Restore with a Scheduling Type of One-Time. Click on the title for this entry to open its details in the Edit Timer Job page and then click the Delete button to remove the failed backup timer job.

posted on Thursday, February 12, 2009 9:46:38 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

There is a mismatch a user profile data available in Sharepoint and data available in Active Directory. It is a known issue. Data in Active Directory is updated but that is not reflecting the Sharepoint system. So the data between these two system are not in sync.

 A workaround for this issue, we delete all problematic users in site collection and re-add this users after Active Directory profile import job succeed.

posted on Thursday, February 12, 2009 9:32:19 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

Sometimes you tried to crawl your content, you receive an error like the following :

sps3://<servername>
Error in portal crawl web service

In this case you can create a root site collection to your web application and try again. The error disappears and people crawl succeed. If you delete this root site collection error reappears.

I am not sure it's a bug or feature...

posted on Thursday, February 12, 2009 9:31:54 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback
# Wednesday, February 11, 2009

You can find WSS 3.0 formulas and functions in the following url. You can use this functions to create multi-functional Sharepoint list views.

http://office.microsoft.com/en-us/sharepointtechnology/CH100650061033.aspx 

posted on Wednesday, February 11, 2009 9:46:16 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

If your database server has not enough space to locate SQL Server log data, you receive this error. Resolution is in explanation :) 

posted on Wednesday, February 11, 2009 9:45:43 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

Today, i get an interesting error that says :

Value cannot be null

System.InvalidOperationException: The event receiver context for Workflow is invalid. at Microsoft.SharePoint.SPEventReceiverDefinition.ValidContext() at Microsoft.SharePoint.SPEventReceiverDefinition.ValidReceiverFields() at Microsoft.SharePoint.SPEventReceiverDefinition.GetSqlCommandToAddEventReceivers(IList`1 erds) at Microsoft.SharePoint.Workflow.SPWinOESubscriptionService.CommitNewSubscriptions(Transaction txn, IList`1 erds)

Error in commiting pending workflow batch items: System.InvalidOperationException: The event receiver context for Workflow is invalid. at Microsoft.SharePoint.SPEventReceiverDefinition.ValidContext() at Microsoft.SharePoint.SPEventReceiverDefinition.ValidReceiverFields() at Microsoft.SharePoint.SPEventReceiverDefinition.GetSqlCommandToAddEventReceivers(IList`1 erds) at Microsoft.SharePoint.Workflow.SPWinOESubscriptionService.CommitNewSubscriptions(Transaction txn, IList`1 erds) at Microsoft.SharePoint.Workflow.SPPendingWorkBatch.ProcessWorkItemBatch(Transaction transaction, Work method, IList`1 workItemBatch) at Microsoft.SharePoint.Workflow.SPPendingWorkBatch.Commit(Transaction transaction, ICollection items)  

Resolution :   TaskID, TaskProperties, AfterProperties, BeforeProperties, or even your CorrelationTokens have probably not been initialized correctly. In my case, I had forgot to do TaskId = Guid.NewGuid(); in one of my CreateTask event handlers and I got this error.

posted on Wednesday, February 11, 2009 9:29:42 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback
# Friday, February 06, 2009

If you want to use custom web services on your custom applications (hosted by MOSS) sometimes an error has occured and written to the Event Log. 


Event Type: Error
Event Source: Office SharePoint Server
Event Category: Publishing Cache
Event ID: 5785
Date: 23/10/2008
Time: 15:47:36
User: N/A
Computer: EAYAN-MOSS 
Description:
Unable to connect publishing custom string handler for output caching. IIS Instance Id is '148047861', Url is 'http://litwareportal/FormActionManagerWS/ActionManager.asmx'
.


Error has been caused, because your sharepoint applications root web.config adds PublishingHttpModule to your custom application. For the formal solution you must remove this PublishingHttpModule statement on your custom applications web.config file.
<httpModules>
  <remove name="PublishingHttpModule" />
</httpModules
>
posted on Friday, February 06, 2009 9:21:15 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback

If you want to get more meaningful error message from SharePoint than the super informative "Unknown Error" message :) go modify a couple things in web.config.

In <SharePoint><SafeMode> set the CallStack property = "true"
In <system.web><compilation> set the debug property = "true"
In <system.web><customErrors> set the mode property = "Off"

posted on Friday, February 06, 2009 9:20:28 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback
# Sunday, February 01, 2009

When you try to edit a Microsoft Office document that is stored in a document library of a Microsoft Windows SharePoint Services Web site, you may receive one of the following error messages, depending on the version of Office that you are running.'Edit Document' requires a Windows SharePoint Services-compatible application and Microsoft Internet Explorer 6.0 or greater.Solutions


Method 1: Install Office XP or a later version of OfficeInError : "Edit Document' requires a Windows SharePoint Services-compatible application" stall Office XP or a later version of Office on your computer. When you install Office, make sure that you also install the SharePoint support component that is included in Office Tools in the Setup program. In Office XP, this component is named Microsoft SharePoint Support. In Office 2003 and in later versions of Office, this component is named Windows SharePoint Services Support. 

Method 2: Install SharePoint supportIf Office XP is installed on the computer, follow these steps:

1. Click Start, and then click Control Panel.
2. Click Add or Remove Programs. 3. In the list of currently installed programs, click Microsoft Office XP, and then click Change. 4. Click Add or Remove Features - Change which features are installed or remove specific features, and then click Next. 5. In the Features to install box, expand Office Tools, click the down arrow next to Microsoft SharePoint Support, and then click Run from My Computer. 6. Click Update. If Office 2003 is installed on the computer, follow these steps:

1. Click Start, and then click Control Panel.
2. Click Add or Remove Programs. 3. In the list of currently installed programs, click Microsoft Office 2003, and then click Change. 4. Click Add or Remove Features, and then click Next. 5. Click to select the Choose advanced customization of application check box, and then click Next. 6. In the Choose update options for applications and tools box, expand Office Tools, click the down arrow next to Windows SharePoint Services Support, and then click Run from My Computer. 7. Click Update. If a 2007 Office suite is installed on the computer, follow these steps:

1. Click Start, and then click Control Panel.
2. Click Add or Remove Programs. 3. In the list of currently installed programs, click Microsoft Office suite 2007, and then click Change. 4. Click Add or Remove Features, and then click Continue. 5. Expand Office Tools. 6. Click the down arrow next to Windows SharePoint Services Support, and then click Run from My Computer. 7. Click Continue.For more information about how to install the SharePoint support component that is included in Office Tools, see the "Method 2: Install SharePoint support" section.

Method 3: Register the Owssupp.dll fileTo register the Owssupp.dll file, follow these steps:

1. Click Start, and then click Run.
2. In the Open box, type cmd, and then click OK. 3. At the command prompt, switch to the folder that contains the Owssupp.dll file. By default, the Owssupp.dll file is located in one the following folders, as appropriate for your version of Office:

• If Office XP is installed on the computer: Drive:\Program Files\Microsoft Office\Office10
• If Office 2003 is installed on the computer: Drive:\Program Files\Microsoft Office\Office11
• If a 2007 Office suite is installed on the computer: Drive:\Program Files\Microsoft Office\Office12

4.Type the following line, and then press ENTER: regsvr32 -u owssupp.dll
5.Click OK when you receive the message that states that the operation was successful. 6. Type the following line, and then press ENTER:

regsvr32 owssupp.dll

7. Click OK when you receive the message that states that the operation was successful.
8. Type exit to exit Command Prompt.
posted on Sunday, February 01, 2009 9:00:31 AM (GMT Standard Time, UTC+00:00)  #    Comments [0] Trackback