SharePoint search and adobe "There was an error opening this document. The filename, directory name, or volume label syntax is incorrect."

I am not sure what the root cause ,but I got error when click on pdf document "There was an error opening this document. The filename, directory name, or volume label syntax is incorrect." when I install adobe reader current XI. What it look like is the Adobe try to open pdf on client mode not browser mode that causing the issue. Here is my work around

1) Create a copy of Item_PDF.html template say Item_PDF_Custom.html.
2) modifiy from ctx.CurrentItem.csr_OpenControl = "PdfFile.OpenDocuments";
 to

  ctx.CurrentItem.csr_OpenApp = "word";
3) Go to site  -> Search ->result type
4) create a copy of PDF and point to new item create in step 1 and give it a new name.

 

SharePoint 2013 Powershell remoting

On the Server:

Enable-PSRemoting -Force
Enable-WSManCredSSP -Role Server -Force

On the Client:

Enable-WSManCredSSP -Role Client -DelegateComputer  myservername -Force 
Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentials -Name WSMan -Value WSMAN/*
Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentialsDomain -Name WSMan -Value WSMAN/*

or manual set fresh creditnal

Computer Configuration > Administrative Templates > System > Credentials Delegation > Allow Delegating Fresh Credentials.


To Start a session:
Enter-PSSession server05 -Authentication CredSSP -Credential DOMAIN\username


if you still run into error complain about NTML try,
Computer Configuration\Administrative Templates\System\Credentials Delegation and set "Allow Delegating Fresh Credential with NTLM on Server Authentication"

If you run into error about WinRM, try winrm quickconfig and make sure all network card is not set to public. I have couple vm, virtual network. I have to disable it before I can run winrm

The Managed Metadata Service "Managed Metadata Service" is inaccessible

My manage metadata service is suddenly stop working after i reboot the server. I check

• Service is running in central admin
• Account running under app pool is still work
• App pool  running this service is not stop

I try to do iisreset and even restart machine one more time to see if it does any good but no luck. I decided to recreate the manage metadata service. Here are step to create

1. Delete broken metadata service but DO NOT DELETE DATABASE (ex: meta1)
2. create a new metadata service using same app pool and new database name (ex: meta2)
3. Go back and change the name of the database to broken metadata service database  (meta1)
4. delete the new metadata service Database just create. (meta2)

That should back to normal.

Content Query Web Part (CQWP) vs Content Search Web Part (CSWP) in SharePoint 2013 ?

1) Content Query Web Part

• Use xsl to customize look  and feel
• Information are display instant unless caching enable
• Can display both minor and major version
• Can use Target Audience
• Can only query content same site collection.

2) Content Search Web Part

• Use HTML and JAVASCRIPT to customize look and feel so very flexible
• Base on search crawl so data/information published is not instance
• Only display major version
• Can't use Target Audience
• Can query cross site collection

What i miss the most is Target Audience is missing in CSWP. 

SharePoint 2013 change look single page. (CSS)

There a lot of time that I have to do some css modification to specific home page like remove spacing between the banner and the content. I script editor  to modified style and/or add additional javascript.

example:

1) Insert script editor webpart
2) insert following to override some css.
<style>
#suiteBar {DISPLAY: none}
.ms-core-navigation { DISPLAY: none }
#contentBox { margin-left: 0px }
.ms-mpSearchBox {DISPLAY: none}
.ms-siteactions-normal {DISPLAY: none}
</style>

SharePoint 2013 March PU (with search component and workflow manager 1.0)

SharePoint 2013 March Public Update is a base for any future update to SharePoint. The following is high level instruction.

Note: any existing workflow 2013 might need to delete and republish.

Assume (2 web front end, 2 apps server and 1 db) - i will call web1, web2, app1, app2 and db1 (app1 host central admin and search admin)

1) add user profile sync account to local admin group. This might break UPS if  you don't.
2) net stop SPTImerV4
    net stop OSearch15
    net stop SPSearchHostController
3) installl march PU on Web1 and restart, repeat this for Web2, App2 and App1 (last)
4) repeat step 2
5) run sharepoint configuration Wizard on Web1
6) restart SPSearchHostController
    restart OSearch15
    restart SPTimerV4
7) repeat step 4 to 6 on Web2 , App2 and App1( last)
6) re-run Register-SPWorkflowService

http://social.technet.microsoft.com/wiki/contents/articles/12497.sharepoint-2013-build-numbers.aspx

http://blogs.technet.com/b/wbaer/archive/2013/05/09/sharepoint-server-2013-march-2013-public-update.aspx

http://blogs.technet.com/b/tothesharepoint/archive/2013/03/13/how-to-install-update-packages-on-a-sharepoint-farm-where-search-component-and-high-availability-search-topologies-are-enabled.aspx

http://www.andrewconnell.com/blog/Updates-For-SP2013-Workflow