Archive for the ‘2013’ Category

Best Practices on using OneNote with SharePoint

Monday, January 18th, 2016

Best Practices on using OneNote with SharePoint

Version: 1.1, Modified Date: 01/19/2016

Scenario:
There are few other ways to use Microsoft OneNote with SharePoint. For this scenario, assume that you didn’t deploy Office Web App 2013, a server product that allows browser based Onenote editing / updates.

SharePoint Online (part of Office 365) has Onenote syncing features by default enabled.SharePoint and OneNote There is a way to use Microsoft OneNote with SharePoint Server 2013 on-premises version.

1. Click on the gear on top right and choose Add an App
2. Click on Documents Library app
3. Click on Advanced Option link on ‘Adding Document Library’ dialog box
4. Enter name e.g ‘ProjectNotes’ and other information for the library. Choose ‘Microsoft OneNote 2010 Notebook’ under Document Template drop down
5. Click Create
6. Copy the URL address for the OneNote Library you just created

That will create a library specifically for OneNote. Now go into that library and follow steps listed below:

1. Click on Files ribbon tab on top left
2. Click on the New Document icon on the ribbon.
3. Click Allow if prompted to allow website to open program
4. That will bring Unpack OneNote window.
5. Enter name for workbook. In Path field, enter the path of your OneNote Library that you created in step 4 of first section.
6. Click Create button
7. Create OneNote pages, sections etc as you normally like to organize information in your OneNote workbook
8. OneNote will Sync the changes back to the Site’s OneNote library
9. In OneNote 2013 / 365 on desktop, click on File > Info to view your workbook showing SharePoint Site URL and not the local path.
10. Click the ‘View Sync Status’ button there to see the sync status

 

More to come in next version of this post.

Configure SharePoint 2013 Hostname based User Profile Service Application

Friday, November 27th, 2015

Configure SharePoint 2013 Hostname based User Profile Service Application

Scenario: All Service Application configured except UPS.

  1. Have a cname record that redirect to existing My.svdomain.com Citrix LB VIP
  2. Create a new Web App with host header set to My.svdomain.com and using Farm admin account for App Pool
  3. Create a Quota Template with 5000 MB limit and 4000 MB warning
  4. Create a root site collection using ‘My Site Host’ template
  5. Go to CA > Manage Services on Server and start:
    1. User Profile Service on one app and two WFE servers
  6. Create User Profile Service Application
    1. SA Name: User Profile Service Application
    2. App Pool: SharePoint Web Services System
    3. Use PPMTest_ as prefix for databases name
    4. Profile Sync Instance: SPAppSrv01
    5. Mysite Host URL: http://My.svdomain.com
    6. MySite Managed Path: /personal
  7. Go to CA > Manage Services on server and turn on User Profile Synchronization Service on one App server. Enter the password for the service account there
    • That will enable two Forefront services in Windows Services console
      • Forefront Identity Manager Service
      • Forefront Identity Manager Synchronization Service
  8. Go back to Manage Service Application > User Profile SA Properties and make sure the Profile Sync instance has the correct server selected and click cancel.
  9. Make sure Service Account (Farm account) has permissions under User Profile SA > Administrators.
  10. Go to User Profile Service Application configure:
    1. Under My Site Settings > Setup My Sites: Under Email notifications, enter My_Sharepoint@svdomain.com as the sender email
    2. Under Configure Synchronization Connections, click ‘Create new connection’ to setup AD connection for profile sync.
      1. Connection Name: svdomain UserProfile ADSync Test
      2. Forest Name: svdomain.ds
      3. Account Name: svdomain\FarmAdmin
      4. Pass: Yourpass
      5. Populate Containers and select the AD OU levels to sync with.
        • svdomain.com
        • Main
          • Admin – checked
          • App – checked
          • Contacts – checked
          • Groups – checked
          • Journaling – checked
          • Users – [Check then uncheck these sub levels]
            • Migrated Users
          • Termed Accounts – checked
          • Users – checked
    3. Click on AD Connection Name and from dropdown choose ‘Edit Connection Filters’. Add user filter for userAccountControl Bit on equal 2. Click OK
  11. Review the Forefront Identity Manager client “C:\Program Files\Microsoft Office Servers\15.0\Synchronization Service\UIShell\miisclient.exe”
  12. Go to User Profile Service Application > Synchronization > Start Profile Synchronization. Perform a full sync. In case the profiles are not imported, review the FIM client for error.
  13. Assign AD Replicate Directory changes permissions to SharePoint account used in User Profile SA (Farm Admin)
  14. Reboot the servers if needed.

 

References:
  1.  https://technet.microsoft.com/en-us/library/hh296982.aspx
  2. User profile properties and profile synchronization planning worksheets for SharePoint Server 2013
  3. Plan user profiles in SharePoint Server 2013
  4. Planning worksheets for SharePoint 2013
  5. Grant Active Directory Domain Services permissions for profile synchronization in SharePoint Server 2013
  6. Administer the User Profile service in SharePoint Server 2013
  7. Plan profile synchronization for SharePoint Server 2013 – Active Directory Domain Services
  8. FIM 2010 Technical Overview
  9. Creating User Profile Synchronization Exclusion Filters using the userAccountControl attribute
  10. Connection filter data types and operators in SharePoint Server 2013
  11. SharePoint 2013: User Profile Syncronization – Direct Active Directory Import
  12. First Look: SharePoint Server 2013 Active Directory Import
  13. Required User Profile Synchronization Permissions in Active Directory for SharePoint 2010

Setup Workflow Manager on SharePoint 2013

Tuesday, November 10th, 2015

V: 1.0

Full video on Workflow Manager 1.0 deployment for SharePoint 2013 or Project Server 2013 is at the bottom of this article.

 

  1. Download Workflow Manager 1.0 and run WorkflowManager.exe (94 KB)
  2. Click Option and uncheck Customer Experience setting
  3. On the Workflow Manager Configuration Wizard page, click Advanced button.
    1. Enter SQL Server name. A highly available SQL Server setup will help the Workflow Manager database availability as well. Use SQL Server Availability Group during Workflow Manager config. Like SQLAG\MSSQLServer,1464
    2. Configure database names for (default name listed below):
      1. Farm Management DB: WFManagementDB
      2. Instance Management DB: WFInstanceManagementDB
      3. Resource Management DB: WFResourceManagementDB
    3. Configure Service Account. Use SP Farm Account
    4. Leave Configure Certificates to Auto-Generate
      1. Use SP2013 as the ‘Certificate Generate Key’ [use a secure key instead of words ‘SP2013’ in production]
    5. Configure Ports
      1. Workflow Manager Management Port: 12290
      2. HTTP Port: 12291
    6. Check the box “Allow Workflow management over HTTP on this computer”
    7. Configure Admin Group (gets access to all DBs): Leave BUILTIN\Administrators
  4. Service Bus Configuration
    1. Farm Management DB: SbManagementDB
    2. Gateway DB: SbGatewayDatabase
    3. Message Container DFB: SBMessageContainer01
    4. Check the box under ‘Configure Service account’ to use same account as used in Workflow Manager config.
    5. Under ‘Configure Certificate’ section use Auto-Generate and check the box to use same certificate generation key as was used for Workflow Manager.
    6. Under Configure Ports use:
      1. HTTPS Port: 9355
      2. TCP Port: 9354
      3. Message Broker: 9356
      4. Internal Communication Port Range: 9000
    7. Configure Admin Group (gets access to all DBs): Leave BUILTIN\Administrators
  5. Review Summary page of the wizard, save the summary using copy and PowerShell options and then click Apply check mark icon on bottom right. That will start the configurations.
  6. At the end of Configuration, click on View Log link to review and save the log. then click on check mark at the bottom to close the wizard.
  7. Exit the Web platform Installer.
  8. Review the database server. You should see 6 new databases.
  9. Review IIS for Workflow Manager Site. Make sure you can get to http://servername:12291 site address for non-SSL: https://servername:12290 for SSL enabled site. You may need to have a DNS address / Load balancer configuration for Workflow URL, if you plan on using multiple servers in the same farm with Workflow Manager.
  10. Review SharePoint Central Admin > Manage Service Applications page to review ‘Workflow Service Application’.
  11. Open SharePoint Management PowerShell with run As admin. Enter following command to connect SP and Workflow Manager.
    • Single Server with HTTP
      Register-SPWorkflowService -SPSite “http://Sharepoint.SVdomain.com” -WorkflowHostUri “http://SPWFE1:12291” -AllowOAuthHttp
    • With DNS FQDN through Citrix Netscaler / Load Balancer
      Register-SPWorkflowService -SPSite “http://Sharepoint.SVdomain.com” -WorkflowHostUri “http://Sharepoint.SVdomain.com:12291” –
      AllowOAuthHttp -forceNote:
      -force parameter will override the previous setting.MSP2013_WorkflowManager_with_FQDN_via_LB_WO_Persistence
  12. Go back to SharePoint Central Admin site > Manage Service Applications > Workflow Service Application. You should see
    ‘Workflow is Connected’ message confirming the workflow manager is connected to SharePoint.
  13. Go to SharePoint Designer, connect to a site and try to create new site workflow. Review the dropdown option for SharePoint 2013 workflow option.

 

To verify the Workflow Manager Deployment

Go to SharePoint Central Administration > Manage Service Applications > Click on Workflow Service Application. If you see the following message, then Workflow Manager is not registered with the SharePoint. You will see Workflow is connected message if the workflow manager is setup correctly with SharePoint.

MSP2013_WorkflowManager_Installed_SP_Serviceapp_NotConnected

 

b. Go to the Workflow Manager URL from one of the SharePoint server. If you get the response, then it is working.

MSP2013_WorkflowManager_with_FQDN_via_LB_WO_Persistence_IE

 

Review the Workflow Changes in SharePoint Designer

In SharePoint 2013 (or Project Server 2013) launch SharePoint Designer, connect to a site and create a new workflow and you will notice that only SharePoint 2010 workflow type is an option. That is due ti missing Workflow Manager setup in the farm.

PPM2013_Dev_SPD_2013WorkflowsNotAvailable

 

Setup Workflow Manager, register it in the SharePoint 2013 farm and then review the SharePoint Designer 2013 Platform Type option. You will notice SharePoint 2013 Workflow as an option. If you will be connected to Project Server 2013 PPM site, you will notice Project Server 2013 as additional option.

PPM2013_Dev_SPD_Showing_Workflows_for_3_Platforms

 

Softvative Video – Workflow Manager 1.0 for SharePoint 2013 / Project Server 2013

 

Softvative Logo

References:

  1. Install and configure workflow for SharePoint Server 2013
  2. Download Workflow Manager 1.0
  3. Video series: Install and configure Workflow in SharePoint Server 2013
  4. Installing and Configuring Workflow Manager 1.0
  5. Configure workflow in SharePoint Server 2013
  6. Service Bus 1.0 for Windows Server – Architecture Overview

SharePoint File Upload Error Due to Symantec Protection Engine Service Failure

Friday, March 20th, 2015

Version: 1.0

Issue Summary

This has been a little tricky issue. Symantec Protection Engine (SPE) that is part of Symantec Protection for SharePoint Servers (SPSS) product has dependency on JAVA JRE component. A Java update caused the Symantec Protection Engine service on the SharePoint Server to fail. Service fails to start with Error 1053. That lead to file uploads in SharePoint to throw error.

Error Details

Symantec Protection Engine (SPE) component depends on Java JRE as you have to use the web browser to get to the Symantec Protection Engine Console. That web console is by default at this location on SharePoint Servers.

https://localhost:8004/

The issue started in this order:
a. A user was trying to upload a file to SharePoint and got the error
b. Symantec Protection Engine service on server was stopped and failed to start with Error 1053
c. Java update caused issue for the Symantec Protection Engine to fail

a. A user was trying to upload a file to SharePoint and got the error

The user received this error in browser.

Error Found
The installed virus scanner is currently unavailable. If the problem persists, contact your administrator.

SharePoint File Upload Error due to SharePoint Antivirus Failure
SharePoint File Upload Error due to SharePoint Antivirus Failure

b. Symantec Protection Engine service on server was stopped and failed to start with Error 1053

Looking at the Symantec Protection Engine (SPE) service under Windows Service console on SharePoint showed the service as stopped. When I tried to start the service, I got following error:

Error:
Windows could not start the Symantec Protection Engine service on local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.

SharePoint Server - Symantec Protection engine service stopped and failed to start with error 1053
SharePoint Server – Symantec Protection engine service stopped and failed to start with error 1053

Following errors were logged in Event View log.

Error 1
Log Name:      System
Source:        Service Control Manager
Date:          2/05/2015 2:17:10 PM
Event ID:      7000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SPAppServer01.svlab.com
Description:
The Symantec Protection Engine service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Service Control Manager” Guid=”{69908d1-a6d7-4795-8e1e-26931d2012f4}” EventSourceName=”Service Control Manager” />
    <EventID Qualifiers=”49152″>7000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime=”2015-02-26T15:17:10.310766100Z” />
    <EventRecordID>187359</EventRecordID>
    <Correlation />
    <Execution ProcessID=”580″ ThreadID=”5204″ />
    <Channel>System</Channel>
    <Computer>SPAppServer01.svlab.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name=”param1″>Symantec Protection Engine</Data>
    <Data Name=”param2″>%%1053</Data>
  </EventData>
</Event>

Error 2
Log Name:      Application
Source:        Application Error
Date:          2/05/2015 2:17:10 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SPAppServer01.svlab.com
Description:
Faulting application name: symcscan.exe, version: 7.0.2.4, time stamp: 0x5167b609
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0xf38
Faulting application start time: 0x01d051d7416d9dad
Faulting application path: C:Program Files (x86)SymantecScan Enginesymcscan.exe
Faulting module path: unknown
Report Id: 88260445-bdca-11e4-91bc-0050569300d1
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Application Error” />
    <EventID Qualifiers=”0″>1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=”2015-02-26T15:17:10.000000000Z” />
    <EventRecordID>331301</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SPAppServer01.svlab.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>symcscan.exe</Data>
    <Data>7.0.2.4</Data>
    <Data>5167b609</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>00000000</Data>
    <Data>f38</Data>
    <Data>01d051d7416d9dad</Data>
    <Data>C:Program Files (x86)SymantecScan Enginesymcscan.exe</Data>
    <Data>unknown</Data>
    <Data>88140445-bdca-11e4-91bc-0050569300d1</Data>
  </EventData>
</Event>

c. Java update caused issue for the Symantec Protection Engine to fail

It turned out to be that the last Java update that updated the Java JRE from some 7.x version to 8.x version caused the issue. After seeing the service failure error and reading Symantec KB articles, I removed and tried to redeploy Symantec Protection Engine component. I got the following error during SPE’s redeployment:

Error:
The Java Runtime Environment could not be found.
Please install the java runtime, 1.5 family, preferably build 13 or higher.

SharePoint File Upload Failure - Symantec Protection Engine re-installation error for Java JRE
SharePoint File Upload Failure – Symantec Protection Engine re-installation error for Java JRE

Keep reading the next section for the resolution.

Resolution

I removed the Java JRE version, rebooted the server and then installed a version from 7.x series 7u60. After that I was able to re-install Symantec Protection Engine. The re-installation fixed the service issue as well.

Make sure you review the Symantec KB resources listed below. In my case just removing version 8.x java and putting back the 7.x would have fixed the issue without re-installation of Symantec Protection Engine.

References

Keywords:

  • SharePoint File Upload error
  • SharePoint File Upload error due to antivirus failure
  • Symantec Protection engine service fails to start with error 1053
www.Softvative.com
Visit www.softvative.com for professional services.

Marrying CSV file type with Microsoft Excel with SharePoint as the Chaperone

Tuesday, February 24th, 2015

Version: 1.3, Modified On: 03/25/2015

The title of this post can be read as following in SharePoint terms:
How to open CSV files in Microsoft Excel when using CSV from SharePoint?

Scenario

.CSV file type is not tied with Microsoft Excel in SharePoint. When users click on a CSV file in a SharePoint Library, it opens the CSV file in Notepad on the user’s computer. In contrast, if user clicks on a .CSV file on their PC, it opens the file in Microsoft Excel.

Antoher scenario where a user has the CSV file checked out, but he closed the CSV file without checking in the file. Now the users clicks on the checked out CSV and it opens in the notepad.

Another issue, the CSV files don’t have any icon associated with the file in SharePoint.

CSV File in SharePoint – Default Behavior

Let’s review the default behavior of CSV file in SharePoint. We have a test CSV file already uploaded to a library in SharePoint.

1. You can see there is no descriptive icon associated with the CSV file unlike Excel file. See the Excel file and .TXT file has relevant icon.

SharePoint - CSV File with no icon - Default behavior
SharePoint – CSV File with no icon – Default behavior

2. Click on the CSV file and you will get a prompt to open, save or save as the file

SharePoint - CSV File type clicked - Default behavior
SharePoint – CSV File type clicked – Default behavior

3. Click Open and it will open the CSV file in Microsoft Excel.

SharePoint – CSV File Opened in MS Excel – Default behavior

4. Now let’s check out the CSV file

SharePoint - Check Out CSV File - Notice Edit in Excel not an Option in menu - Default behavior
SharePoint – Check Out CSV File – Notice Edit in Excel not an Option in menu – Default behavior

5. Click on the checked out CSV file

SharePoint – Check Out CSV File – Click to open – Default behavior

6. Click ok on the Open Document dialog box

SharePoint - Check Out CSV File opens Document dialog box - Default behavior
SharePoint – Check Out CSV File opens Document dialog box – Default behavior

7. The opens up in Notepad!!!

SharePoint - Check Out CSV File opens up in Notepad - Default behavior
SharePoint – Check Out CSV File opens up in Notepad – Default behavior

We will review the inside behavior and how we can enhance the user experience for the CSV files.

Different Areas To Review and Resolution

We’ll review few areas related to this issue:

a. Default Programs settings on the user’s PC
i. Set your default programs
ii. Associate a file type or protocol with a program
b. IIS Web Server MIME Settings for .CSV on SharePoint Servers
c. Adding line item for CSV file and behavior in DocIcon.xml on SharePoint Servers
d. Changing Hkey_Classes_Root.csv on user’s PC

a. Default Programs settings on the user’s PC

Excel is the default program for CSV and is usually not the issue for the .CSV file to open in Microsoft Excel when the CSV file is on the PC or network share.

i. Set your default programs

1. Go to Control Panel > Default Programs
2. Click on Set your default programs

CSV File Association - Control Panel > Default Programs
CSV File Association – Control Panel > Default Programs

3. Click on Excel from the list of program on left side. Then click on ‘Choose defaults for this program’

CSV File Association – Control Panel > Default Programs – Excel Defaults

4. Make sure the csv extension is checked for Excel. Then click Save.

CSV File Association – Control Panel > Default Programs – Excel Defaults

ii.    ii. Associate a file type or protocol with a program

Let’s review the file type association under Default Programs.

1.  Go to Control Panel > Default Program
2. Click on ‘Associate a file type or protocol with a program’

CSV File Association - Control Panel > Default Programs - Associate File Type or Protocol
CSV File Association – Control Panel > Default Programs – Associate File Type or Protocol

3. On next page, make sure .csv file type is associated with Excel. Click on Change Program button if it is not or if you want to change it.

CSV File Association - Control Panel > Default Programs - CSV File Type Associate
CSV File Association – Control Panel > Default Programs – CSV File Type Associate

4. From Open With dialog screen, choose Excel. If Excel is not listed then expand ‘Other Programs’ section by clicking on the small arrow on right side. If Excel is not listed there then use Browse button to go to folder location where Microsoft Excel is installed and select the Excel.exe executable file. Make you to check the box that says ‘Always use the selected program to open this kind of file’

CSV File Association - Control Panel > Default Programs - CSV File Type Association with Excel
CSV File Association – Control Panel > Default Programs – CSV File Type Association with Excel

5. Click OK and close Default Program window.

b. IIS Web Server MIME Settings for .CSV on SharePoint Servers

We’ll now review the MIME type in IIS.

1. On SharePoint Servers, open IIS Manager
2. Click on the Server name on the left side of the console. On the right side of console make sure you have Features View tab highlighted

Note: You can make this change for selective web application (IIS site) rather than to the whole server.

3. From the features list, click on the MIME Types

SharePoint Servers - IIS Manager > MIME Types for CSV Changes
SharePoint Servers – IIS Manager > MIME Types for CSV Changes

4. Look for .CSV under the MIME Types. [Hint: You can select the first item in list and type .csv on kleyboard. It will take you right to the CSV extension]

The default .CSV MIME Type config is set to: application/octet-stream

5. Double click on the .CSV (or select .cSV and choose Edit from actions area on right).
Enter this value for CSV: application/vnd.ms-excel

Note: I’ve also noticed few people used below .CSV MIME Type value:
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

SharePoint Servers - IIS Manager > Updated MIME Types for .CSV Extension
SharePoint Servers – IIS Manager > Updated MIME Types for .CSV Extension

The IIS MIME type change will make the CSV file open in Microsoft Excel. Read below for details. Some scenarios may require below changes as well.

c. Adding line item for CSV file and behavior in DocIcon.xml on SharePoint Servers

Now to better user experience, we would like to add some icon with CSV file and enabled ‘Edit in Microsoft Excel’ in file menu in SharePoint. Look into the icon for CSV file in the first image at the top of this post.

On SharePoint Servers, we have DocIcon.xml file at following location that holds the key to the file type and behavior.

Location:
C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14TEMPLATEXMLDOCICON.xml

Under the ByExtension section add the line for CSV file type. Notice the CSV16.gif is the icon file that I’m using for the CSV. You can use other icons like icxltx.png
<Mapping Key=”csv” Value=”CSV16.GIF” EditText=”Microsoft Excel” OpenControl=”SharePoint.OpenDocuments”/>

The location to store your own file icon or use one already there:
C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14TEMPLATEIMAGES

Note:
I’ve noticed people have used one of these configuration for the CSV file type in DocIcon.xml. I choose the above line entry.
<Mapping Key=”csv” Value=”CSV16.GIF” OpenControl=””/>

<Mapping Key=”csv” Value=”CSV16.GIF” OpenControl=”SharePoint.OpenDocuments”/>

<Mapping Key=”csv” Value=”CSV16.GIF” EditText=”Microsoft Excel” OpenControl=”SharePoint.OpenDocuments” OpenApp=”ms-excel”/>

Important:
After performing the MIME Type change and this DocIcon.xml addition on all SharePoint Servers, make sure to perform the IISreset/noforce on SharePoint Servers.

d. Changing Hkey_Classes_Root.csv on user’s PC

On few user systems, I noticed the checked out files will still open in notepad if clicked by the same user.

To resolve that issue, I had to delete “PerceivedType”=”text” from the following registry location. [Use at your own risk and with backups].

HKEY_CLASSES_ROOT.csv

SharePoint - Deleted PerceivedType entry from Registry for .CSV Extension on user PC
SharePoint – Deleted PerceivedType entry from Registry for .CSV Extension on user PC

That registry location had these value:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT.csv]
“PerceivedType”=”text”
@=”Excel.CSV”
“Content Type”=”application/vnd.ms-excel”

[HKEY_CLASSES_ROOT.csvExcel.CSV]

[HKEY_CLASSES_ROOT.csvExcel.CSVShellNew]

[HKEY_CLASSES_ROOT.csvPersistentHandler]
@=”{guid}”

Few other notable Registry Location:
HKEY_CLASSES_ROOT.***
HKEY_CLASSES_ROOT<ProgId>shellopencommand
HKEY_CLASSES_ROOTMIMEDatabaseContent Type

HKEY_LOCAL_MACHINESOFTWAREClasses.csv

After these changes, the CSV filetypes will show the icon on the left, the SharePoint file menu will show Edit in Microsoft Excel as an option and edit the file will open the file in Microsoft Excel.

SharePoint - CSV File Types Showing Icon, Menu Showing Edit in Microsoft Excel Option
SharePoint – CSV File Types Showing Icon, Menu Showing Edit in Microsoft Excel Option

The short summary of this overall jargon can be explained in this Softvative Graphics.

Quick Process to Make CSV filetype work in MS Excel on SharePoint
Quick Process to Make CSV filetype work in MS Excel on SharePoint

@@@@@ At the end, the CSV and MS Excel lived happily ever after. 🙂  @@@@@

Few good resource to read on MIME Types and CSV

Keywords:

  • How to open CSV file in Sharepoint
  • How to open CSV file in Microsoft Excel
  • How to open CSV file in Excel
  • Open CSV in Excel
  • Open CSV from SharePoint
  • open .CSV from in Excel
  • open .CSV from SharePoint
  • CSV MIME Type changes
  • CSV MIME Type changes in SharePoint
  • CSV MIME Type changes for SharePoint
  • CSV MIME Type changes for Excel
  • CSV open document behavior
  • CSV default program association
  • Marry the CSV to Excel
  • CSV Registry locations
Visit www.softvative.com for professional services.

Four ways to Get Report of SharePoint Folders and Files for a Library

Wednesday, February 11th, 2015

Version: 1.0

Scenario

You might have many layers of folders insides folders and files insides those folders in a SharePoint Library. How to get a quick report of folders and files for a single Document Library?

There are different ways to get that information:

a. Using Generate File Plan Report Feature of Document Library
b. Using Mapped Drive with Dir Command
c. Using SQL Query
d. Using Power Shell

a. Using Generate File Plan Report Feature of Document Library

SharePoint has a feature in Document Library called ‘Generate File Plan Report’. Follow the steps below:

1. Go to a document library for which you need to get the list of folders and files
2. Go to Library > Library Settings
3. Click on ‘Generate File Plan Report‘ under Permissions and Management

SharePoint Document Library - Generate File Plan Report
SharePoint Document Library – Generate File Plan Report

5. On next page, Save location field will default to the same library. That is the place where the system will generate and save the report file. Click Ok
6. Report will be generated and you will see a link on next page. Click on the page to open the report in MS Excel

SharePoint Document Library - Click the link to review report
SharePoint Document Library – Click the link to review report

7. Click OK and you will back to the Document Library. You can locate the file in the same library or to a place you picked in step 5

Example Report File

b. Using Mapped Drive with Dir Command

The above report doesn’t show you the folders and files that are inside those folders. It just reports the Total # of items at each folder layer.

To get the full hierarchy of folders including files inside each level of hierarchy, you need to switch back to basics. My 1992 study of  Peter Norton’s Dos Guide came to rescue from here.

1. Copy the URL http://sharepoint.svlab.com/sites/biz1/project1/ProjectsDocLib/                                [notice I removed .aspx view file and form folder that contains the view pages]
2. Map an available drive letter on your PC say W: and use the above URL
3. Open a command prompt and go to W: drive
4. Use the command
dir /s > c:FilesFolders.txt

You can add /b switch to get rid of file / folder details and just get the files / folder names.
dir /s /b > c:FileFolders.txt

5. Open the txt file and you will see the folders and files in hierarchical structure
6. Make sure to disconnect the W: drive.

Navigating using Windows Explorer with SharePoint is not the fastest way to work with SharePoint.

c. Using SQL Query

You can use the SQL query to get the list of files and folders. Run at your own risk in a pre-production system.

— Query to list Files and Folders within Sites
— By Faisal Masood
SELECT 
Webs.Title AS ‘WebApp’,
AllLists.tp_Title AS ‘ListName’,
AllDocs.DirName AS ‘URL’,
AllDocs.LeafName AS ‘FileName’,
AllDocs.ExtensionForFile AS ‘FileType’,
AllDocs.TimeCreated
FROM AllDocs 
JOIN AllLists
ON AllLists.tp_ID = AllDocs.ListId
JOIN AllDocStreams
ON AllDocStreams.Id = AllDocs.Id
JOIN Webs
ON Webs.Id = AllLists.tp_WebId
WHERE — Webs.Title LIKE ‘%SharePoint Company Sitet%’ AND
AllDocs.DirName like ‘documents%’
–AND AllDocs.TimeCreated > ‘2010-05-10 00:00:00.000’
ORDER BY Webs.Title

c. Using Power Shell

PowerShell might be the best option to get customized report with selective information. The PowerShell code below will get show all documents under a document library names that has Documents in name and that are under site sharepoint.svlab.com site.

# List Files and Folders under a Documents Library
# By: Faisal Masood – PMP, MCSE, MCITP, MCSA
#Add SharePoint PowerShell SnapIn if not already added
 if ((Get-PSSnapin “Microsoft.SharePoint.PowerShell” -ErrorAction SilentlyContinue) -eq $null) {
    Add-PSSnapin “Microsoft.SharePoint.PowerShell”
}

# http://sharepoint.svlab.com/
Get-SPWeb http://sharepoint.svlab.com/ |
  Select -ExpandProperty Lists |
    Where { $_.GetType().Name -eq “SPDocumentLibrary” -and
            -not $_.Hidden } |
    Select -ExpandProperty Items |
    Where { $_.Url -like “*Documents*” } |
    Select Name, {$_.File.Length}, url

Download .ps1 PowerShell Script File

Keywords:

  • get report of files and folders in SharePoint
  • report folders and files in SharePoint
  • Four ways to get Files Folder structure
  • SQL query to get Files Folder structure
  • PowerShell to Files Folder structure
Visit www.softvative.com for professional services.

Project Web Access 2010 Manage Timesheets and IE 11 Compatibility

Thursday, February 5th, 2015

Version: 1.0

Scenario

I came across a scenario where a user needed to recall and delete some of his Project Web Access (PWA) 2010 timesheets. Its not straightforward, keep reading :). The user was using Internet Explorer (IE) 11 on Windows 7 running under VMware VDI.

Normally a user would click on ‘Manage Timesheets‘ from PWA to delete / recall timesheets. With IE 11 the user was getting error:

Error
This Project Server 2010 feature requires at least Microsoft Internet Explorer 7.0.
Correlation ID:####
Date and Time: MM/DD/YYYY TT:TT

Project Web Access - Manage Timesheets page Error when using IE 11
Project Web Access – Manage Timesheets page Error when using IE 11

Background

Looking at the official Project Web Access 2010 Support page, I noticed that IE 11 is not supported browser for by Microsoft Project Web Access (PWA).

Reference:
Plan browser support (Project Server 2010)
https://technet.microsoft.com/en-us/library/ff631137(v=office.14).aspx

The way to go with IE 11 with Project Web Access 2010

Solution 1:

Add your PWA URL *.companyname.com in the local intranet zone of Internet Explorer.

Besides that review the Compatibility View Settings under Tools menu. The default compatibility view settings display the local intranet sites in Compatibility View.

PWA Manage Timesheets page error - Default IE 11 Compatibility View settings
PWA Manage Timesheets page error – Default IE 11 Compatibility View settings

The above method has few benefits:
a. user will not be prompted with the login to PWA site on local intranet
b. Compatibility view default settings will make the PWA URL to work in compatibility mode

Solution 2:
If adding sites to IE Local Intranet zone is locked down by IT, then review the Compatibility View settings and make sure Local Intranet sites option is checked (above screenshot). If it is not than check it or just add the companyname.com url into the field above and click Add

Solution 3:
If IE Local Intranet zone and Compatibility View settings are locked down by IT, then your next option is to use IE Developer Tool using F12 key and changing Document Mode and User Agent settings.

To recall / delete timesheet using IE11, follow these steps:

Log on to your VDI or virtual desktop environment and launch default Internet Explorer session. In this case IE 11. then follow steps listed below.

1. Go to your PWA 2010 portal http://pwa.svlab.com/pwa
2. Click on Manage Timesheets link on bottom left. The page link is http://pwa.svlab.com/pwa/_layouts/pwa/timesheet/mytssummary.aspx
3. You will get error saying, it need at least IE 7. Press F12 key on keyboard to bring IE developer tools window
4. Go to Emulation tab
5. Change the mode to following

  • Document Mode: 8 (Default)
  • User agent string: Internet Explorer 9

6. The page will automatically refresh and will bring the user timesheets
7. Select a timesheet and click Recall or delete icon for the timesheet

  • You can Delete a Timesheet with Status In Progress
  • You can Recall a Timesheet with status Approved

8. Click on the timesheet link for the period that you want to adjust. For deleted timesheet click on ‘Click to Create’ link
9. Save and submit the timesheet or proceed as needed.

Project Web Access - Manage Timesheets page in IE 11 using F12 Dev Tools and changing Mode
Project Web Access – Manage Timesheets page in IE 11 using F12 Dev Tools and changing Mode

Solution 4:
There are few other tricks but I’ll not cover those details here for the sake of time. Those are around manipulating the user agent & x-ua Compatible settings.

Solution 5:
Roll out Local Intranet Sites and Compatibility view settings via Active Directory Group Policy (GPO) settings.

Alternatively for a Virtual Desktop Infrastructure (VDI), Remote Desktop / Terminal Server or Citrix type environments, make the configuration as part of the global / admin change that all users in that virtual environment will automatically get.

Scope:
This article is not about details of Browser mode, user agent, compatibility view or other related settings.

References:

  1. Project Web App 2010 can use IE 10 in compatibility mode
  2. Erik Van Hurck – Internet Explorer 11, Windows 8.1 and Project Server 2013
  3. Cory Peters – SharePoint and Internet Explorer 11
  4. IEInternals MSDN – Internet Explorer 11’s Many User-Agent Strings

Keywords:

  • using IE 11 with PWA 2010
  • using IE 11 with Microsoft Project Web Acccess 2010
  • manage timesheets page error in pwa 2010
  • this feature requires at least Internet Explorer 7
  • using compatibility view settings with PWA 2010
  • using compatibility view settings in IE 11
Visit www.softvative.com for professional services.

Rename a Project in MS Project Server Part 5

Friday, January 30th, 2015

Rename a Project in Microsoft Project Server – Part 5

Version: 2.0

Applies to:
MS Project Server 2010
MS Project Server 2013
MS Project Online (Office 365)

This is the fifth and last part of the series to explain the details of different cases and how to best rename a project schedule in Microsoft Project Server EPM.

Table of Contents

1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional
3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion

 

Summary

Renaming a project in a MS Project Server EPM environment might require considerations for the OLAP data cube and the Business Intelligence (BI) Center reports.
 

5. Renamed Project Schedule and Business Intelligence Center Reports

We covered so far all the steps to rename project schedule in MS Project Server. The Business Intelligence (BI) Center reports out of SSAS OLAP Cube will show the old and new project name. It is best to select both project names for accurate EPM reporting.

Let’s look Project Web Access (PWA) > Business Intelligence (BI) timesheet reports.
As an example let’s pick one of the timesheet template. Go to PWA > Project BI Center > Templates Library on left> English (United States) folder > Server Name – OLAP Database Name folder > OlapTimesheet.xltx
The path of that file is something like this:
http://pwa.softvative.com/PWA/ProjectBICenter/Templates/English%20(United%20States)/SSAS_server_domain.com_instance%20-%20EPM_Project_Prod/OlapTimesheet.xltx
Click on the OlapTimesheet.xltx template file to open it in Microsoft Excel. First save the file to the root of your Template library using save option or to a place where you like to organize Project BI Reports. I saved it to following location
http://pwa.softvative.com/PWA/ProjectBICenter/Templates/
With Excel report still open, now choose the fields from the PivotTable Fields list on the right side. Create a timesheet report that will have Timesheet Project List in it.
 
Project Web Access - BI Center Excel Report - Choose PivotTable Fields
Project Web Access – BI Center Excel Report – Choose PivotTable Fields
 
Filter the project list and select only the project name. You will notice only the old project.
 
Project Web Access - BI Center Excel Report - EPM Timesheet Report before project renamed
Project Web Access – BI Center Excel Report – EPM Timesheet Report before project renamed
 
Close the OLAP Excel Report file.
Now enter hours under a different timesheet period and submit. Later process the PWA OLAP cube manually from Server Settings > OLAP Database Management. Highlight your OLAP Database name row (don’t click on cube name), then click on Build Now icon above. Once the cube builds successfully, launch your timesheet report again from the place where you saved it. Apply the filter on the project name and expand the row data. You will now notice the old and new project names there.
 
Project Web Access - BI Center Excel Report - EPM Timesheet Report after project renamed
Project Web Access – BI Center Excel Report – EPM Timesheet Report after project renamed
 
Here the linkto the sample cached excel report from the BI Center.

Conclusion

You can see renaming a project might look like a quick thing to do. But it requires careful steps to update name at different places. You miss a major step and you will see your users complaining about different issues:

  •  I don’t see my project anymore
  • My timesheet hours are lost
  • I can’t get my project SharePoint site
  • List goes on….
A better communication plan for the change and doing this change at non-peak hours is the recommended approach.

That finishes last part of this series. We covered the following topics in this series.

Keywords:

  • Renaming a project in Project Server
  • Renaming a project in Microsoft Project Server
  • Rename a project using MS Project
  • Rename a project using MS Project Professional
  • Rename a Project in Project Server
  • best practice to rename a project in Project Server
  • best practice to change a project name in Project Server
  • How to change a project name in Project Server
  • How To guide for renaming a project in Project Server
  • Primer on renaming a project in Project Server
  • Step by step guide to rename a project in project server
  • Edit Project details to rename a project
  • Rename a project schedule in Project Server
  • Rename a project plan in Project Server
  • How to rename projects in Project Server
  • How to rename a mpp file in Project Server
  • Renaming Projects
  • Project rename process
  • Project rename job aid



Visit www.softvative.com for professional services.

Rename a Project in MS Project Server Part 4

Friday, January 30th, 2015

Rename a Project in Microsoft Project Server – Part 4

Version: 2.0

Applies to:
MS Project Server 2010
MS Project Server 2013
MS Project Online (Office 365)

This is the fourth part of the series to explain the details of different cases and how to best rename a project schedule in Microsoft Project Server EPM.

Table of Contents

1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional
3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion

 

Summary

Renaming a project in a MS Project Server EPM environment might require team members to adjust their timesheets based on few conditions.
 

4. Scenarios: Renaming Project and different Statuses of Timesheets

There are few scenarios based on different statuses of timesheet in MS Project Server.

1. In progress timesheet
2. Approved timesheet (Submitted)
3. Period Closed timesheet
Below is the table that summarizes the conditions.
Timesheet Status Table
Timesheet Status
Description
Can Recall
Can Delete
Project Name
In Progress
Active timesheet created before rename
Yes
Old
Approved (Final)
Approved timesheet
Yes
Old
Period Closed (Final)
Timesheet period closed
No
No
Old
Not Yet Created
Not active yet
New
Note: In this scenario, we assume that users are listed as their own Timesheet Managers and so the submitted timesheets are auto-approved.
You can view status of a timesheet by going to Timesheet page and reviewing the bar above the timesheet grid area (below the ribbon).
 
Project Web Access TimeSheet - In Progress Timesheet
Project Web Access TimeSheet – In Progress Timesheet
 
Project Web Access TimeSheet - Approved Timesheet
Project Web Access TimeSheet – Approved Timesheet
 
New Project name will show up in new timesheets if you go to future or past timesheet periods that were not created at the time the project was renamed (those with status of ‘Not Yet Created’). Timesheets where the project’s tasks were not shown, once you add tasks using Insert Row > Insert Task, will also show the new project name.
You can review summary of timesheets by going to Manage Timesheets page under Settings section on left navigation.
 
Project Web Access Manage Timesheets Link
Project Web Access Manage Timesheets Link
 
Review the status column and you will find timesheets with either one of the three statuses.
Project Web Access Manage Timesheets Page
Project Web Access Manage Timesheets Page
• Clicking on ‘My Timesheet’ under timesheet column for a period will take you to that Timesheet’s page and will show the details.
• Highlighting the row by clicking any area on the row except ‘My Timesheet’ will activate the Recall or Delete icons on the top left ribbon area. Review the Timesheet Status Table listed above to see when you can recall or delete a timesheet based on timesheet status.
Timesheet Recall icon
Timesheet Recall icon
Timesheet Delete icon
Timesheet Delete icon

Exception 1: In Progress Timesheet previously created

Timesheets that were created prior to the project rename will still show the old project name.

Note:
In screen shots of this part you can notice, I renamed the project again before this part.

Project Web Access (PWA) - In Progress Timesheet showing old project name
Project Web Access (PWA) – In Progress Timesheet showing old project name
Resolution
1. Go to Manage Timesheets page, select the row for the timesheet and hit Delete icon on top left of ribbon to delete the In-Progress timesheet showing old project name.

Project Web Access (PWA) – Delete In Progress Timesheet

 

2. Now click over ‘Click to Create’ under Timesheet name to recreate the timesheet.
Project Web Access (PWA) - Create Timesheet
Project Web Access (PWA) – Create Timesheet

 

3. Once timesheet is created, you will be redirected to that timesheet. You can notice the new project name. Notice the previously saved hours are still intact.
Project Web Access (PWA) – Enter time in Timesheet under Project Tasks

Exception 2: Approved Timesheet previously created & Submitted

The timesheets that were approved prior to project rename will need to be recalled and deleted. Then recreate and resubmit the timesheets. Other than recall, the rest of the steps are the same as listed in exception 1 case.
Project Web Access (PWA) - Save and Submit Timesheet Got Approved
Project Web Access (PWA) – Save and Submit Timesheet Got Approved
Project Web Access (PWA) - Recall an Approved Timesheet
Project Web Access (PWA) – Recall an Approved Timesheet
That finishes third part of this series.
 
More on this and other scenarios is coming in next parts of this series. So far we have completed the three parts. Review the fourth part for timesheet related gotchas and remedies.
 


Keywords:

  • Renaming a project in Project Server
  • Renaming a project in Microsoft Project Server
  • Rename a project using MS Project
  • Rename a project using MS Project Professional
  • Rename a Project in Project Server
  • best practice to rename a project in Project Server
  • best practice to change a project name in Project Server
  • How to change a project name in Project Server
  • How To guide for renaming a project in Project Server
  • Primer on renaming a project in Project Server
  • Step by step guide to rename a project in project server
  • Edit Project details to rename a project
  • Rename a project schedule in Project Server
  • Rename a project plan in Project Server
  • How to rename projects in Project Server
  • How to rename a mpp file in Project Server
  • Renaming Projects
  • Project rename process
  • Project rename job aid



Visit www.softvative.com for professional services.

Rename a Project in MS Project Server Part 3

Friday, January 30th, 2015

Rename a Project in Microsoft Project Server – Part 3

Version: 2.1

Applies to:
MS Project Server 2010
MS Project Server 2013
MS Project Online (Office 365)

This is the third part of the series to explain the details of different cases and how to best rename a project schedule in Microsoft Project Server EPM.

Table of Contents


Summary

1. Steps to rename a project using Project Web Access (PWA)
2. Steps to rename a project using MS Project Professional
3. Rename Project site
4. Scenarios: Renaming Project and different Statuses of Timesheets
5. Renamed Project Schedule and Business Intelligence Center Reports
Conclusion

 

Summary

Renaming a project site in a MS Project Server EPM environment requires the following procedure.
 

3. Rename a Project Site

Renaming a project site is optional step. Even if you keep the old project site name, it will work and not break things. It is though good to have consistent naming across all places. The connection between a project schedule and project site is maintained by Project Server under Server Settings > Project Sites area. Renaming Project site has two steps:

a. Rename Project site’s Title and URL
b. Update the connection between Project schedule and Project site with new URL
 

a. Rename Project site’s Title and URL

To rename the project site follow the steps listed below.
1. Go to PWA > Project Center and locate your project
2. Select the project by clicking the first empty cell on left and then in the navigate ribbon group, click on Project Site
 
MS Project Web Access (PWA) - Select a Project and go to Project Site
MS Project Web Access (PWA) – Select a Project and go to Project Site


3. That will open your project site in new tab / window
4. Click on Site Actions > Site Settings on top left

MS Project Web Access (PWA) - Project Site > Site Settings
MS Project Web Access (PWA) – Project Site > Site Settings


5. Under Look and Feel section, click on ‘Title, description and icon’

MS Project Web Access (PWA) - Project Site > Site Settings > Look and Feel
MS Project Web Access (PWA) – Project Site > Site Settings > Look and Feel


6. Update the fields as needed:

Title and Description: to reflect the new name that will show up on the project site’s top left.
Web site Address: to update the URL address of the project site

MS Project Web Access (PWA) - Project Site > Site Settings > Title Description and Icon
MS Project Web Access (PWA) – Project Site > Site Settings > Title Description and Icon


7. Click OK to save your changes

b. Update the connection between Project schedule and Project site with new URL

Following the steps below. Without this step, the project site link will not work from Project Center and other places as it will be still be pointing to old project site URL. Users will get 404 not found error.

1. To update the connection URL between Project Schedule and Project Site, go to PWA > Server Settings
2. Click on Project Sites under Operations Policies section

MS Project Web Access (PWA) - Server Settings > Project Sites
MS Project Web Access (PWA) – Server Settings > Project Sites


3. Locate your project (using new name) in the list. Note the old URL still showing up even though the project schedule is showing the new name

MS Project Web Access (PWA) - Server Settings > Project Sites > Project showing old project name in URL
MS Project Web Access (PWA) – Server Settings > Project Sites > Project showing old project name in URL



4. Select the project by clicking on the row and then from top of the page click on ‘Edit Site Address’

MS Project Web Access (PWA) - Server Settings > Project Sites > Edit Site Address
MS Project Web Access (PWA) – Server Settings > Project Sites > Edit Site Address
5. In the Edit Site Address dialog box, update the URL address with new project site address (changed in section 3.a.6 above)


MS Project Web Access (PWA) - Server Settings > Project Sites > Edit Site Address Dialog box
MS Project Web Access (PWA) – Server Settings > Project Sites > Edit Site Address Dialog box


6. Click OK to any prompt and then locate the project on the page and verify the new site address

MS Project Web Access (PWA) - Server Settings > Project Sites > Edit Site Address Prompt for permissions
MS Project Web Access (PWA) – Server Settings > Project Sites > Edit Site Address Prompt for permissions
MS Project Web Access (PWA) - Server Settings > Project Sites > Project showing new project name in URL
MS Project Web Access (PWA) – Server Settings > Project Sites > Project showing new project name in URL


That finishes third part of this series.

More on this and other scenarios is coming in next parts of this series. So far we have completed the three parts. Review the fourth part for timesheet related gotchas and remedies.
 
 
Summary
 


Keywords:

  • Renaming a project in Project Server
  • Renaming a project in Microsoft Project Server
  • Rename a project using MS Project
  • Rename a project using MS Project Professional
  • Rename a Project in Project Server
  • best practice to rename a project in Project Server
  • best practice to change a project name in Project Server
  • How to change a project name in Project Server
  • How To guide for renaming a project in Project Server
  • Primer on renaming a project in Project Server
  • Step by step guide to rename a project in project server
  • Edit Project details to rename a project
  • Rename a project schedule in Project Server
  • Rename a project plan in Project Server
  • How to rename projects in Project Server
  • How to rename a mpp file in Project Server
  • Renaming Projects
  • Project rename process
  • Project rename job aid



Visit www.softvative.com for professional services.