Sharepointtechs's

Unable to move Content Editor Webpart from one place to other

sharepointtechs — Fri, 18 Nov 2011 07:10:15 +0000

Issue

While moving the Content Editor webpart from one place to another We get the following error message “Error On page” on the Bottom left of the IE.

After moving the content Editor webpart , when we click Exit edit mode . It gives “Unexpected error has occured”.

Cause

This usually happens whenever we copy the HTML code from one Content Editor webpart to another. When we copy the HTML code it also copies the Webpart ID and it conflicts.

Resolution

Open the Site in FIrefox\Chrome browser as IE will not give you the Drop down to edit the webpart

Modify the Content Editor Webpart

Open the Source Code

Remove the following Tag from the code for eg:- ”id=WebPartWPXX WebPartID=”XXXX-XXXX-XXXX-XXXX-XXXXXXXX”

Click Apply – OK

You can then move the webparts without any issues

Workflow Error: “An error has occurred in Approval”

sharepointtechs — Fri, 18 Nov 2011 04:26:27 +0000

It’s not a known issue But it’s more of a Setup error

We have the SharePoint OOB Approval workflow which can be attached to a document library to start whenever a new document gets created and get the required approvers to review and approve the document for publishing.

It is a very easy task to set-up this workflow

Steps to setup a workflow :

For a document library or list , go to Settings->Workflow Settings->Add Workflow

Choose the Approval workflow from the list, make it start on item creation go to the second workflow page.

Select the approvers and check “Update the approval status (use this workflow to control content approval) “

Finish and create a document in the library.

Although this might seem as an easy straightforward task the workflow might after all still end-up in error:

Error System Account An error has occurred in Approval

Cause : Because This is an approval workflow

which should update the approval status of the document Also

if you missed one step like setting the approval for the document library this simple task will fail at the end.

The workflow will start and run flawlessly until the end when it will try to update the approval status.

If this setting is set to not to require content approval it will fail to update it hence throwing the above error.

So, if you encounter this, just go into the document library settings and go to Versioning Settings Page

Set “Require content approval for submitted items ” to yes and everything should be fine.

Updating SharePoint list by using InfoPath form

sharepointtechs — Fri, 18 Nov 2011 04:24:45 +0000

Step 1: Create the list

1. Create a new custom list named: MyContacts
2. From the Settings button choose List Settings
3. Click Create Column
4. Add the following columns/data types:
• FirstName, Single line of text
• LastName, Single line of text
• Email, Single line of text
• Phone, Single line of text

The next step is to create a Collaborative Application Markup Language (CAML) template that contains the same XML nodes as the columns we added to our list – this will be used as a secondary data connection in the InfoPath Form Template.

Step 2: Create the CAML template

1. Launch Notepad (or any text editor)
2. Copy and paste the following code to the Notepad document:









3. Save this as: Add List Item Template.xml

Step 3: Create the InfoPath Form Template

1. Create a new, blank, browser-compatible form template
2. Add a “Receive” type secondary data connection to the Add List Item Template.xml file created in Step #2. (Make sure the options “Include the data as a resource file in the form template” and “Automatically retrieve data when the form is opened” are enabled.)
3. Add a “Receive” type secondary data connection to the “MyContacts” SharePoint List created in Step #1 and make sure the option “Automatically retrieve data when the form is opened” is enabled.
NOTE: Be sure to include the “Title” field along with the custom fields we created.
Each SharePoint list is created with a unique identifier called a GUID. In order to submit items to a SharePoint list, you must know the unique GUID for that list. These next steps will enable you to identify the GUID for your “MyContacts” list.

Step 4: Identify the list GUID

1. Open a browser and navigate to the MyContacts list
2. From the Settings menu choose List Settings
3. In the browser’s address bar you will see the URL appended with “List=”

4. Copy everything after the equals sign and paste this into a text editor as we will need this value later on.
NOTE: We will need the list GUID to be formatted as “{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}”. If your GUID appears as above with the hyphens and braces “escaped” (i.e. %7B for the braces and %2D for the hyphens) then you will need to replace the escaped characters with the braces and hyphens so when we use this GUID later, it will appear as: {0D73FBB5-88E1-4435-B607-51ADC5DA6D58}

Step 5: Add controls to the InfoPath Form Template

1. Open the Data Source Task Pane
2. From the Data Source dropdown box choose the “MyContacts” connection

3. Right-click on “MyContacts” and choose Repeating Table – this will add a repeating table bound to that connection to your View
4. From the Data Source dropdown box choose Main
5. Add a text box to the “myFields” node named: ListName and set the Default Value property to the GUID value of your list – we will use this node to specify the list when we perform the Submit operation

To update the SharePoint list we will be using the “UpdateListItems” method of the SharePoint “lists.asmx” web service. This web method requires a couple of parameters (the list name and what gets updated) – now that we have added the “ListName” node which contains the GUID and we have the Add List Item Template XML data connection which describes our data structure we have all the necessary information to add the “UpdateListItems” web method!

Step 6: Add the “lists.asmx” web service

1. Add a new “Submit” type of web service data connection to the “lists.asmx” web service – this is typically located at: http://servername/_vti_bin/lists.asmx
2. Select the “UpdateListItems” operation
3. Double-click the “listname” parameter and assign the “my:ListName” node as the value

4. Double-click the “updates” parameter, select the “Add list Item Parameter” data source, select “Batch” and click OK
5. For the “Include” option select “XML subtree, including selected element”

6. Complete the Data Connection Wizard
Now that we have all the connections that are required, we now need to add the “submit” functionality to the form template.

Step 7: Add Submit functionality

1. Display the Data Source Task Pane
2. From the Data Source dropdown box choose the Add List Item Template data connection
3. Drill down through the data source, right-click on the Field node and choose Repeating Table

We need to change the text box control in the “Name” column to Read-only – if these values were to be changed it would affect the CAML and the submit would fail.
• Double-click on the text box in the Name column of the Repeating Table
• Select the Display tab
• Enable the Read-only property and click OK
• Add a new Button control to the View
• Double-click the button to display the Properties
• Click the Submit Options button
• Enable the option “Allow users to submit this form”
• Enable the option “Perform custom action using Rules” and click the Rules button
• Click the Add button
• Click the Add Action button
• From the Action dropdown box choose “Submit using a data connection”, select the “Web Service Submit” data connection and click OK
• Click the Add Action button
• From the Action dropdown box choose “Query using a data connection”, select the “MyContacts” data connection and click OK (this will automatically refresh the list in InfoPath so you can see the newly added record)

• Click OK until you are back to your form
NOTE: If you want to automatically clear out the submitted values, add another action to this Rule to “Set a field’s value” and the only option you need to specify is the “Field” option – select the “Field” node from the “Add List Item Template” data connection and then simply leave the Value option blank.

Step 8: Test

1. Click the Preview button to preview the form
2. Fill in values for each of the fields: Title, First Name, Last Name, E-mail and Phone

3. Click the Submit button – the contact information should be submitted successfully and the “MyContacts” list automatically updated

Not able to map a SharePoint site as a Mapped drive

sharepointtechs — Fri, 18 Nov 2011 04:23:29 +0000

OS - XP SP2

Error : The format of the specified network name is invalid

Cause = Webclient is diabled on the cleint machine

Steps to Enable webclient

Start => run

In the run box type services.msc

we will find webclient service right click and open the properties and change it from disabled to automatic or manual and start the service apply the changes

Now we can then map the drive

However one more thing to add is we had to specify the url as \\sitename\sites\sitecollectionname

You try to open a word document in Sharepoint and get the error “Ambiguous name detected: tmp.dde”

sharepointtechs — Fri, 18 Nov 2011 04:20:28 +0000

Resolution:

· Research on the above error and found that if we rename normal.dot and reopen the word it will recreate it.

· Did the same.

· Close all the word document and rename NORMAL.DOT

· You will find that under :

· C:\Documents and Settings\\Application Data\Microsoft\Templates

· Open a blank word document and close it.

· Check the location again, you will find that normal.dot will be created.

· Ask the user to open the word document from the Sharepoint site and it should work fine

Your client does not support opening this list with Windows Explorer

sharepointtechs — Fri, 18 Nov 2011 04:15:59 +0000

we are very much familiar with this error message and know what exactly needs to be done if such issue occurs. But this issue varies if operating system changes from XP to Windows Vista.

FYI- This is a known issue with windows vista OS and we have a Microsoft KB for this: http://support.microsoft.com/kb/841215

Before we can go ahead and conclude on to above mentioned KB, make sure to check the following points:

1) Web client service should be started

2) You can also get the error if the URL to the document library is 100 characters long

3) If you are using Internet Explorer 6 you will get the error. You know it’s time to upgrade

It would be a good question as What exactly this KB suggest ?

Please refer the following info:

Click Start

type regedit.exe in the Start Search box

Locate and expand the list and navigate to the following location

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameter

Locate the value BasicAuthLevel

Right click the value and choose Modify.
In the Value data box, type 2, and then click OK.

Exit Registry Editor, and then restart the computer.

Note: We will not do any kind of changes inside the registry so this should be done with the help of Desktop Support Team

If it’s a Windows Server 2008 OS then please check the following:

Open up the Windows Server Manager.

Click Features in the left hand menu

Click Add Features, in the main window.

Select the Desktop Experience feature, and then click Next.

Click Install.

Click Close when the Add Features wizard is done.

Choose to reboot when done.

If it’s a Windows Server 2003 OS then please check the following:

Download and install the Microsoft Hotfix

Windows Office needs a Web Client update to work properly with WebDAV.

List of MOSS 2007 Template ID Information

sharepointtechs — Fri, 18 Nov 2011 04:10:38 +0000

0 – GLOBAL (SetupPath=global) – “Global template”

1 – STS – “windows SharePoint Services Site”, “Team Site”, “Blank Site”, “Document Workspace”

2 – MPS – “Basic Meeting Workspace”, “Blank Meeting Workspace”, “Decision Meeting Workspace”, “Social Meeting Workspace”, “Multipage Meeting Workspace”

3 – CENTRALADMIN – “Central Admin Site”

4 – WIKI – “Wiki Site”

7 – BDR – “Document Center”

9 – BLOG – “Blog”

20 – SPS (OBSOLETE) – “SharePoint Portal Server Site”

21 – SPSPERS – “SharePoint Portal Server Personal Space”

22 – SPSMSITE – “Personalization Site”

30 – SPSTOC (OBSOLETE) – “Contents area Template”

31 – SPSTOPIC (OBSOLETE) – “Topic area template”

32 – SPSNEWS (OBSOLETE) – “News area template”

33 – SPSNHOME (SubWebOnly) – “News Home template”

34 – SPSSITES – “Site Directory area template”

36 – SPSCOMMU (OBSOLETE) – “Community area template”

38 – SPSREPORTCENTER – “Report Center Site”

39 – CMSPUBLISHING (SetupPath=SiteTemplates\PUBLISHING) – “Publishing and Team Collaboration Site”

40 – OSRV (SetupPath=SiteTemplates\OSRV) – “Shared Services Administration Site”

47 – SPSPORTAL – “Corporate Intranet Site”

50 – SRCHCEN – “Search Center”

51 – PROFILES – “Profiles”

52 – BLANKINTERNETCONTAINER – “Internet Presence Web Site”

53 – BLANKINTERNET – “Publishing Site”, “Press Releases Site”, “Publishing Site”

54 – SPSMSITEHOST – “My Site Host”

90 – SRCHCENTERLITE (SetupPath=SiteTemplates\SRCHCENTERLITE) – “Search Center Lite”

6221 – PWA (SetupPath=SiteTemplates\PWA) – “Project Web Access Site”

6215 – PWS (SetupPath=SiteTemplates\PWS) – “Project Workspace”

14483 – OFFILE – “Records Repository”, “Records Repository”

How to find out the ID of a site collection ….

sharepointtechs — Fri, 18 Nov 2011 04:09:26 +0000

Open the Central Administration
Application Management
SharePoint Site Management
site collection quotas and locks

Select the appropriate site collection and you will get the ID of that specific site collection

How to find out the ID of a subsite:

Save the current site as site template[.STP extension]
Save it to disk somewhere.
Now, navigate to that location and rename the file to .CAB extension.
Extract the CAB file and find the manifest.xml file.
Now, in the file check for the site ID/TemplateID string and get the value.
Navigate to end of this post for the TemplateID to Name mapping.

How to find out the List ID:

Navigate to the SharePoint list using the browser.
Select the Settings + List Settings menu command.
Copy the URL from the browser address bar into Notepad. It will look something like:

https://personal.collaborationtools.consumer.citigroup.net/personal/Sushant/_layouts/listedit.aspx?List=%7B47F2F5E2%2D6474%2D4929%2DB986%2D64BBE801C97A%7D

Delete everying before and including “List=”.

Change “%7B” to “{”

Change all “%2D” to “-“

Chnage “%7D” to “}”

You are now left with the Id:

{47F2F5E2-6474-4929-B986-64BBE801C97A}

Cannot connect to the configuration database after installing SP2

sharepointtechs — Fri, 22 Jul 2011 05:51:59 +0000

*** Problem Description ***
BEHAVIOR/SYMPTOMS:
====================

PSConfigUI failing after installing WSS 3.0 SP2

Environment:

===============

Wss 3.0 on a stand alone system

Customer is using the windows internal database

Issue :

After the installation of the sp2 which is included as a critical update in the windows update we face connection issues with Sql

Error message :

Access to table dbo.spt_values is blocked because the signature is not valid.

When we run the psconfig

Symptoms:

======

It will start creating n number of sharepoint_config databases without any tables

We will not be able to access the dbo.versions when we try checking the version of the database

We might be able to check for the version of the config database

Resolution :

Download management studio express
Set SQL express to allow tcp/ip and named pipes

Open the connection with the following address

\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

Backup all the databases from the sql server management studio .

Check with the customization as it will be lost

Tak e a screen shot of

Solution management
AAM
Topology
Databases in the Sql server management studio
Uninstall windows internal database from the add remove programs

Uninstall SharePoint and reboot the server

Install back SharePoint with windows internal database (standalone installation )

Restore all the databases

Attach the database back to the farm

The server should be up and running

Troubleshooting tips for the Synchronization Service

sharepointtechs — Thu, 14 Apr 2011 17:55:27 +0000

Below is a list of requirements and common points of failure for the user profile synchronization service. If you have an issue with the sync service failing to start, stuck starting or stopping, verify the items below in the customer’s environment.

Verify that the Sync account is a member of the local administrators group.

Verify the account is a member of the farm administrators group.

Verify that a profile service application has been created prior to starting the sync service.

Verify that the application pool for the UPA is leveraging the farm account.

Look for SQL alias issues using CLICONFG – should be fixed with the CU1 update.

Verify proper permissions in SQL for Sync account – As this is leveraging the farm account, it should have DBCreator and SecurityAdmin.

Look at the registry keys for the FIM components: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\FIMService] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\FIMSynchronizationService]

Monitor ULSViewer during the sync service configuration with a filter of Category contains Profile applied.

Check Application and System logs for errors during configuration

Consider rebuilding the FIM registry keys – See FIMService file in the resources section of this document.

Consider rebuilding the User Profile Application to obtain a new sync database. In this process you need to back up the profile and social databases, then specify those names where appropriate in the new UPA creation, while entering a new name to create a new sync db. This will recreate the UPA while preserving the social and profile data

Consider using Process Monitor to look for Access Denied issues

Verify if the domain was upgraded from Windows 2000. If so add the sync account to the “Pre-Windows 2000 Compatible Access” and “Windows Authorization Access” groups. If in doubt add the account being used by the sync service to those groups in AD as appropriate.

If service is stuck in starting or stopping, consider setting the FIM services back to their default values of Disabled and Local System, and rebooting the server.