Monthly Archives: May 2011
- Manage document conversions (SharePoint Server 2010).
- How Do I: Configure Document Conversions in SharePoint 2010?| TechNet.
- Document Conversion to PDF within SharePoint.
- Adlib Software First to Deliver Complete Document Transformation Solution for SharePoint® 2010 | Business Wire.
- PDF for SharePoint product | Adlib Software.
- Bamboo Solution: SharePoint PDF – Convert Office Files to PDFs in SharePoint.
- Muhimbi – PDF Converter for SharePoint 2007.
- Use a Three-state workflow – SharePoint Server – Office.com.
- The Three-State Workflow – The Forgotten Out-Of-The-Box Workflow for Both WSS and MOSS — SharePoint Solutions Team Blog.
Here is a simple description of »Three state« workflow how it works.
- Create a new »Issue« (before doing this assign »Three State Workflows« to »Issue tracking« list)
- Edit and save the item. When the item is saved, the first workflow is generated.
- A new item appears in the »Issue tracking« list.
- User receives an e-mail with instructions what to do:
- A new generated workflow appears in the »Tasks« list.
- In order to finish the task, open the task in edit mode.
- Set the status filed to »Completed«. The task is complete now and will made a change on the »Issue tracking« item. This item will go to the middle state and the second workflow will be generated.
- On the task list you can see that the first task is completed and the new one is here.
- At the same time the item on the »Issue tracking« list is now in the »Resolved« state. At the beginning it was in »Active state«.
- Let us complete the second task now.
- Both tasks are now completed.
- On the »Issue tracking« list an item is now in the final state »Closed«. The case is finished.
I got this error when I tried to open the site in SharePoint Designer 2010. SPD is installed on the client.
The server could not complete your request.
An error occurred while trying to fetch data from your SharePoint site. Unexpected response from the server. The content type of the response is “”. The status code is “OK”.
The reason is that there can only be 1 binding on a web application. If you have more than 1, it will no longer work and you get this error.
One possible solution is to extend your web application (central administration – application management – manage web applications).
If you open the site of that extented web app, SPD will connect to that site again.
My worflow failed to start. In the ULS logs I got the following message:
Category: Workflow Infrastructure Message: System.ArguementException: Item does not exist. It may have been deleted by another user.
According to the discussion in this thread I concluded that the »Workflow source files« (.XSN, .XOML) were Checked Out. I checked in these files and it started to work.
Final explanation on this thread was:
Basically the problem was in fact related with the versioning state of the SPD workflow files. The files in the workflow publishing process were not checked in and so no other user could access them, which lead to the errors described in the post above. And the reason for the fail in the check-in was because the list that has the workflow files has a Title field that was set to required and not Optional as it should be.
This was due to the fact that the Title field is being inherited from somewhere at the sitecollection level where it is being “Required”. We suspect that this is happening at the “Document” parent level (by default the Title for the “Document” content type is “optional”). That needs to be changed.
Solution: One needs to go to the Document content type and verify if the “Title” field is set to “Required”. If it is, click on “Title” and then change it to “Optional” and save the change (this might return an error stating it can’t propagate the change to some content types, but it propagated to the workflow lists).
Take the following steps:
- In SPD in the »Site Objects« pane select »All files« and then »Workflows«.
- Find your workflow and select it
- You can see that some files are checked out (green tick marks)
- Check In all these files
- My workflow started to work after taking these steps.
1. Open Windows Explorer
2. Write the path to the server file structure in the following form:
Example 1: This is the path to the root directory on the server “server_name” on the C:\ disc.
Example 2: This is the path to the “System32” directory on the server “server_name” on the C:\ disc.
3. The system asks you for your credentials.
4. After succesfull login you can freely navigate around the server file structure.
In order to trace events in SharePoint or events that are somehow connected to the SharePoint, you can find helpful information on the following sites:
- Diagnostic logging in SharePoint 2010.
- SharePoint LogViewer – View ULS logs the easy and efficient way – Home.
- ULS Viewer – Home.
- How do I troubleshoot SharePoint? So many logs! – The Bamboo Team Blog – Bamboo Nation.
- How to troubleshoot mysterious SharePoint errors. «
- IIS Logging Overview.
- Where are My IIS Log Files Stored? – SmarterTools Inc..
- Maximize IIS logging to track user activity | TechRepublic.
- ETL File Extension – Open .ETL files.
- Free Web Analytics and SEO Software.
In general, there are three main places, where trace events are logged. You can find them in:
- Windows Event Viewer
- SharePoint logs (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS)
- IIS logs (location specified on each website)
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS
Setup Logging in IIS:
1. Launch Internet Information Services (IIS) Manager.
2. In the Connections pane, select the desired website for which you want to configure logging.
3. Double-click the Logging feature in the Actions pane.
4. On the Logging page, select the desired logging format to be used.
5. Specify the location of the log file by typing a log path into the Directory text box. Alternatively, click the Browse button and select a directory to store the files.
6. In the Log File Rollover section, select the method to create the new log file. The options include specifying an Hourly, Daily, Weekly, or Monthly schedule, entering a maximum file size (in bytes), or selecting the option that puts a stop to the creation of new log files.
7. The final option requires you to determine whether to use local time for file naming and rollover.
8. After all the log file settings have been given; select Apply in the Actions pane to commit the changes.
NOTE: It is possible to either enable or disable a log file for a specific site by selecting Enable or Disable in the Actions pane of the Logging feature page. To enable logging for IIS 7.0, the HTTPLoggingModule must be installed.