Skip to main content

Posts

Showing posts from August, 2016

Working with SharePoint Report Server 2012 using URL parameters in SSRS 2008/2012 in SharePoint Integrated Mode – Part Two

In my previous post I have explained how to pass the custom URL parameter to the Report when it is SharePoint Integrated Mode. As explained earlier post report server parameter has three parts. <prefix>:<Parameter Name>= <Value>   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 (Explained in Part One) When you are running the Report Server under SharePoint, You can Access the report Server using /_vti_bin/reportserver. You can find similar page if report server is running.   rc: This is for passing parameters to Report Server HTML viewer. Here are the list of parameters. rc:Parameters rc:Zoom rc:Section rc:FindString rc:StartFind rc:EndFind rc:FallbackPage rc:GetImage rc:Icon rc:Stylesheet EX: - http://mysharePoint/_vti_bin/ reportserver?<Document Li

SharePoint 2013 Web site Keep on Prompting for credentials

There are many reasons to happen this but most of the time it will happen when you change the Access mapping to match your domain. For an example you might have webwfe01 as your web application in your default zone. And if you change that to www.sampleweb.com this may be occurred for Windows Users. This is because by not having Fully Qualified Domain name specified is not matching with the local machine. For an Example, Your local machine can be in a domain myorg.com and the specified Mapping is sampleweb.com Thus this will cause LoopBack check which it true by design for security reasons. Microsoft specifies two methods to resolve the issue. Disable Strict Name Checking [ Ref ] Disable Loopback Check [ Ref ] REF: https://support.microsoft.com/en-us/help/896861/you-receive-error-401.1-when-you-browse-a-web-site-that-uses-integrated-authentication-and-is-hosted-on-iis-5.1-or-a-later-version You need to do it all SharePoint servers for safe side in the future service deploymen