Melick's Blog

This is use full in many scenarios. For me it’s more use full for disable keep on prompting credentials in SharePoint 2013 Environment. In this method you need to add your domain as an exception list to IIS for not checking the FQDN for loopback. Open the RegEdit. And navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa and click on MSV1_0 Then add new Multi Connection String And add BackConnectionHostNames Then you will see that is added to the registry. You can double click and add your fully qualified domain names (One per line) that will be working as an exception. Then you can save and restart the IIS.

There is a slightly different between earlier SSRS report parameters and NEW SSRS running in SharePoint server 2013. URL parameters are slightly different from native mode and SharePoint Mode. This article is only about SharePoint mode parameters. SSRS running on SharePoint has few parameter types and types are passing to SSRS engine using prefix.   Parameter Type Prefix Note Report Viewer Control rc: Report Server HTML controller Report Server rs: Report Server to process Report Viewer Web Part rv: Web part parameters Report Parameters rp: Report parameters Most of the time passing parameters to report is more frequently used than any other Passing the Reports as a URL Parameter Assume that we have created a Report with parameter interval and need to pass the values from the URL. Let’s see the attributes of the @interval parameter. I have mentioned the visibility as visible but you can also have it as Internal as well. Internal will not be ...

Report Server has encountered a SharePoint error. ---> Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error. ---> Microsoft.SharePoint.SPException: The user does not exist or is not unique. ---> System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors in SharePOint 2013 This is error accouring because of Anonimous access to the Microsoft Reporting Services. According to the Microsoft ; Microsoft Reporting Service not supporting annonimous access for integrated mode. Ref: https://msdn.microsoft.com/en-us/library/bb283324.aspx#Anchor_4 So you might be wondered how you can archive this. Option One Simply you can dissable the Anonimous access from IIS. But this wont work if you really want anonimous access in your farm. For an Example If are hosting internet site with integration mode public reports you can not dissable the anon...

  I was failed installing Windows Live writer  in few attempts and It didn't work for me by doing several work rounds that is available in the web.   So I have ultimately switched to the OpenLive Writter that was very similar in every aspects. You can find the open source version of your great tool by using the following link http://openlivewriter.org/

this is a common and simple error due to Dissable of Active Scripts. You can go to internet explorer settings and Click –> Custom Level button and Enable in Active Scripting under Scripting

  When you debuging your Sharepoint Search you might have come a cross that there is a error in crawl log in sharepoint farm. The URL of the item could not be resolved. The repository might be unavailable, or the crawler proxy settings are not configured. To configure the crawler proxy settings, use Search Administration page This is because your search can not be resolved to a perticular address ; most probably youy coperate proxy blocking it domain name resolution is not happening inside the sharepoint crawl Easiest way to resolve the error is First clear any proxy settings you have specified in the search settings. You can go to the Crawling Proxy settings and make sure you didint specify the proxy for content crawling. Then goto each server in your farm and add the doman name entry resolution in the HOST file. C:\Windows\System32\drivers\etc\hosts Now you can run the crawler again and you will see there are no top level erros in your crawl log. 

  You might have encountered this problem when you are trying to create a Team Project Usign Visual Studio and You might be wondered that you are having correct permision also. Actually this is not about Permision it is all about the correct verision for Visual Studio. If you are using TFS 2013 you should use correspondign Team Explorer (Ex: Visual Team Explorer 2013) or related visual studio.