Report Builder Report Download 401 Unauthorized Error

Environment:-
Server1 -- SQL services, SQL reporting services all 2008 R2 64bit, SharePoint installation 2010 and Reporting services add-in

Server2 -- SharePoint installation with Central Administration hosted 2010, Reporting services add-in .

Issue:- While downloading Report Builder report Externally (from Internet) it does not download and gives a "Cannot Retrieve error"

Error:- PLATFORM VERSION INFOWindows : 5.0.2195.262144 (Win32NT)
Common Language Runtime : 2.0.50727.42
System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200)
mscorwks.dll : 2.0.50727.42 (RTM.050727-4200)
dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll : 2.0.50727.42 (RTM.050727-4200)

SOURCESDeployment url :
http://URL/ReportServer/ReportBuilder/ReportBuilder.applicationERROR SUMMARYBelow is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://URL/ReportServer/ReportBuilder/ReportBuilder.application resulted in exception. Following failure messages were detected:
+ Downloading http://URL/ReportServer/ReportBuilder/ReportBuilder.application did not succeed.
+ The remote server returned an error: (401) Unauthorized.
COMPONENT STORE TRANSACTION FAILURE SUMMARYNo transaction error was detected.WARNINGSThere were no warnings during this operation.OPERATION PROGRESS STATUS* [08/05/2008 09:33:39] :
Activation of http://URL/ReportServer/ReportBuilder/ReportBuilder.application has started.

Tried and tested
So many blogs and articles online on this issue that I have lost count how many read and how many times I might have deleted and recreated web applications. As most of the articles and blogs suggest to enable Annonymous Access on the ReportBuilder Virtual directory in IIS, but SQL 2008 reporting services does not create this Virtual directory in IIS so how do we give annonymous access??? Broken my head on this issue with my colleagues and lot of hours reading long msdn and technet articles but all in vain...

Resolution:-
1. Browse to Central Administration of SP 2010
2. Application Management
3. Manage Web applications -> Select the Web Application which will be used for SSRS
4. Select Authentication Providers -> Select "Enable Annonymous Access" checkbox
5. Click Ok.

This will setup the most required annonymous access for the virtual directories in IIS and Report builder will start downloading from Internet also. Hope this helps to many out there. Also to mention our SP site was also configured with Kerberos and SSL using a Hostheader.

.WMV Documents are not visible after uploading in Doc lib in Sharepoint 2007

Environment: Sharepoint 2007 x64bit
IIS 7.0
Windows server 2008 SP2

When we try uploadig documents in sharepoint 2007 doc lib, it was giving me error due to big file size.
After research got the technet article as http://support.microsoft.com/kb/925083 which says that we need to do changes in web.config file for that web application along with settings in IIS related to connection timeout.

Increase the maximum upload size

Click Start, All Programs > Administrative Tools, and then click SharePoint Central Administration > click Application Management.
Under SharePoint Web Application Management > Web application general settings.
On the Web Application General Settings page, click the Web application that you want to change.
Under Maximum upload size, type the maximum file size in megabytes that you want, and then click OK.

Increase the connection time-out setting

By default, the IIS connection time-out setting is 120 seconds. To increase the connection time-out setting in IIS 7.0 , follow these steps:
Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
Selecet the site for which you want to imcrease the connection time out settings > on right had side, click advanced settings
Under Behavior, click on the + sign for connection limit and edit the connection time out settings (seconds) to 360(as per required).

Add the executionTimeout value

Use Notepad to open the Web.config file. By default, this file is in the following location:
Program Files\Common Files\Microsoft Shared\Web server extensions\12\TEMPLATE\LAYOUTS
Add the executionTimeout value that you want. For example, replace the value as follows.

Existing code (Note: remove -- from the tags)
<--location path="upload.aspx">
<--system.web>
<--httpRuntime maxRequestLength="2097151" />
<--/system.web>
<--/location>

Replacement code (Note: remove -- from the tags)

<--location path="upload.aspx">
<--system.web>
<--httpRuntime executionTimeout="999999" maxRequestLength="2097151" />
<--/system.web>
<--/location>

After you change the file, click Save on the File menu.
Use Notepad to open the Web application Web.config file. By default, this file is in the following folder:

Inetpub\wwwroot\wss\VirtualDirectories\VirtualDirectoryFolder

Change the following line in the file.

Existing line (Note: remove -- from the tags)

<--httpRuntime maxRequestLength="51200" />

Replacement line (Note: remove -- from the tags)

<--httpRuntime executionTimeout="999999" maxRequestLength="51200" />

After you change the file, click Save on the File menu.
Exit.
Restart the site from IIS and try uploading the required .wmv file
You will be surprised to see that there was no error and it seems as if the file got uploaded.
What is this!!!!!

When you browse to that document library, you will be surprised to see that the file is not there :(

Yes... this is where we need to do some more changes in web.config file for IIS 7.0 users
The changes are as follows:

Adjusting File Size Limit in IIS 7

The problem is that in IIS 7 on Windows 2008 Server, the web application will reject any file that is larger than 30 MB. You can increase the maximum file size by adding the following code to in the web.config file:
(Note: remove -- from the tags)

<--security>
<--requestFiltering>
<--requestLimits maxAllowedContentLength=”2000000000″ />
<--/requestFiltering>
<--/security>

and inplace of the

<--httpRuntime executionTimeout="999999" maxRequestLength="51200" />

that we changed earlier, we need to increase the value to '2000000000' from '51200'

<--httpRuntime executionTimeout="999999" maxRequestLength="2000000000" />

With the above maxAllowedContentLength and Max RequestLength, users can upload files that are 2,000,000,000 bytes in size. This setting will work right away without restart IIS services.

Enabling Barcodes for Library or List

Configure Barcoding system (Barcode) in SharePoint for Document libraries and Lists.

Note:- We can configure the Barcodes for only Document and List libraries in SharePoint 2007
Barcoding is configured for unique identification of Physical assests in the company. SharePoint generates the Unique Barcode values automatically out of the box.

Steps to Enable the Barcode Policy at Site Collection level.
1. Browse to the site where you need to configure Barcodes.
2. Click Site Actions -> Site Settings -> Modify All Site Settings -> Site Collection Policies
3. Click on Create to create the Policy
4. Enter the desired Name and Policy Statement
5. Select the Enable Barcodes checkbox -> Click OK



The Site Collection Policy will be created, now we need to activate this policy for a library or list. The steps are same for both. It needs to be activated at the Content Type level.



Steps to Activate the Policy to a List
1. Browse to the List -> Select Settings -> List Settings -> Advanced Settings -> "Yes" for Allow Managment of Content Types -> OK
2. Click on the Content Type (by Default Item will be shown) -> Select Information Managment Policy Settings -> Select Use a Site Collection Policy -> from drop down, the one we created in above steps -> Click OK

Now when you start Adding items using the Content Type to which the Policy was applied, Barcodes will be generated. Modify the View to show the columns "Barcode" and "Barcode Value"

ORA-01036: illegal variable name/number

Error:- ORA-01036: illegal variable name/number
Env:- Crawling Oracle database and views from SP BDC using SSO.

I had used BDC Meta Man to create the ADF file and after that it was giving the below error while doing full crawl. After working with the BDC support, I found out that the Identifiers we specify in the tool are suppose to be unique in data. Once selecting those Unique identifiers, import the ADF file again and crawl from SharePoint, it will work fine.

Log Name: Application
Source: Office SharePoint Server
Date: 3/12/2010 10:08:30 AM
Event ID: 5701
Task Category: Business Data
Level: Error
Keywords: Classic
User: N/A
Computer: server name
Description:
Could not run query/stored proceedure 'Select ORACLE STRING QUERY Pooling=True;User ID=readonly;Integrated Security=False;Persist Security Info=false;User ID=readonly;' in App Domain 'DefaultDomain'. The full exception text is: ORA-01036: illegal variable name/number

Event Xml:
event xmlns="a href="http://schemas.microsoft.com/win/2004/08/events/event/a>">
5701
2
1330 0x80000000000000 10916226
Application Servername

Select ORACLE STRING QUERY Pooling=True;User ID=readonly;Integrated Security=False;Persist Security Info=false;User ID=readonly;
DefaultDomain
ORA-01036: illegal variable name/number

The error code returned was 0x800706b9 - Configuring SSO for first on fresh installation

I was trying to resolve this error since almost a week and was about to give up. Had tried all the following steps to resolve the issue.

1. Removed the quotes from ssosrv registry key for ImagePath key (as per research on other sites)
2. Made the SSO service account a member of DomainAdmins account.
3. Rebooted the server, stopped the service, re-entered the credentials and password for the service account in Services.msc and started the service
4. Configured the service account in Central Adminstration - Service Accounts for SSO

All the steps you can possibly find on google I had tried and still was getting the below error in the ULS Logs and event viewer.

02/22/2010 20:43:40.65 SSOSRV.EXE (0x1518) 0x162C SharePoint Portal Server SSO 0 Medium NetUserGetInfo said User username exists 02/22/2010 20:43:40.65 SSOSRV.EXE (0x1518) 0x162C SharePoint Portal Server SSO 0 Medium Destroying CCommandEx 02/22/2010 20:43:40.65 SSOSRV.EXE (0x1518) 0x162C SharePoint Portal Server SSO 0 Medium Destroying CSessionEx 02/22/2010 20:43:40.65 SSOSRV.EXE (0x1518) 0x162C SharePoint Portal Server SSO 0 High ::RpcServerUseProtseq() failed with rpc error 1721 02/22/2010 20:43:40.65 SSOSRV.EXE (0x1518) 0x162C SharePoint Portal Server SSO 0 High Error code is: -2147023175 02/22/2010 20:43:40.65 SSOSRV.EXE (0x1518) 0x162C SharePoint Portal Server SSO 0 Critical One or more RPC services for the Microsoft Single Sign-on (SSOSrv) service failed to start. The error code returned was 0x800706b9. For more information, see the Microsoft SharePoint Products and Technologies Software Development Kit (SDK). 02/22/2010 20:43:40.65 SSOSRV.EXE (0x1518) 0x162C SharePoint Portal Server SSO 0 High CRPCService::RegisterRPCInterface() failed to register ISingleSignonConfiguration 02/22/2010 20:43:40.65 SSOSRV.EXE (0x1518) 0x162C SharePoint Portal Server SSO 0 High Error code is: -2147023175 02/22/2010 20:43:40.65 SSOSRV.EXE (0x1518) 0x162C SharePoint Portal Server SSO 0 Critical User domain\username failed to configure the single sign-on server. The error returned was 0x800706b9. Verify this account has sufficient permissions and try again.

Log Name: ApplicationSource: Office SharePoint ServerDate: 2/22/2010 2:23:07 AMEvent ID: 6517Task Category: SSOLevel: ErrorKeywords: ClassicUser: N/AComputer: servername.domain.com Description:User domain\username failed to configure the single sign-on server. The error returned was 0x800706b9. Verify this account has sufficient permissions and try again.
1358321 Application servername.domain.com domain\username 0x800706b9

Resolution:
http://support.microsoft.com/kb/246784
1. Go to this registry path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet

"Ports" key was having the value 5000-50002 with no spaces ( like other articles which mentioned to remove spaces )

2. I changed the value to 0-65335 without any spaces or hitting the enter key, Click OK

3. Restart the server.

Now SSO was Configured without any error. If you check the above registry key, the values will be changed back to what it was before. Dont change them again, if your SSO is configured, dont temper with that registry again.

Upgrade windows 2003 32 bit DC to windows 2008 64 bit DC

Adding Windows Serve 2008 R2 AD DS in Existing Windows Server 2003 32 bit forest

Prepare Windows Server 2008 R2 64 bit
1. Install windows Server 2008 R2 from the installation DVD [ http://www.petri.co.il/how-to-install-windows-server-2008-step-by-step.htm ]
2. Give a Static IP address to the server.
3. Configure the Preferred DNS server as the Windows server 2003 DC.
4. Install the updates from the following site. http://windowsupdate.microsoft.com/. This should install the needed SP2 and post hot fixes.
5. Join the Machine to the Domain as a Member Server. Reboot the Server.

Installing Pre-Requisites
Make sure that .NET Framework 3.5 SP1 is installed.

Preparing Windows Server 2003 Forest for Windows Server 2008 R2 DC
Prepare the Forest
1. Log-on to the Windows 2003 DC Schema Master with the Enterprise Admins, Schema Admins, and Domain Admins groups privileges to prepare the Forest for Windows Server 2008 R2 DC.
2. Insert the Windows Server 2008 R2 DVD into the DVD drive.
3. Run Command Prompt as Administrator.
4. Run the following command from the DVD.
a. D:\support\adprep\adprep /forestprep [ Note: If it is Windows Server 2008, it will be D:\sources\adprep\adprep /forestprep ]
5. If you have multiple Windows Server 2003 DC’s, let the replication finish or use replmon to manually replicate the Domain Controllers before preparing the Domain for Windows Server 2008 R2 DC.

Prepare the Domain
1. Log-on to the Infrastructure master with Domain Admin privileges.
2. Insert the Windows Server 2008 R2 DVD into the DVD drive.
3. Run command prompt as Administrator.
4. Run the following command from the DVD.
a. D:\support\adprep\adprep /domainprep [ Note: If it is Windows Server 2008, it will be D:\sources\adprep\adprep /Domainprep ]
5. If you have multiple Windows Server 2003 DC’s, let the replication finish or use replmon to manually replicate the Domain Controllers before preparing the Domain for Windows Server 2008 R2 DC.
Note: For other Deployment scenarios please follow this link. http://technet.microsoft.com/en-us/library/cc771433(WS.10).aspx

Adding Windows Server 2008 R2 as an Additional Domain Controller.
1. Open Server Manager. Click Start, point to Administrative Tools, and then click Server Manager.

2. In Roles Summary, click Add Roles.

3. If necessary, review the information on the Before You Begin page, and then click Next.

4. On the Select Server Roles page, click the Active Directory Domain Services check box, and then click Next.

5. If necessary, review the information on the Active Directory Domain Services page, and then click Next.

6. On the Confirm Installation Selections page, click Install.

7. On the Installation Results page, click Close this wizard and launch the Active Directory Domain Services Installation Wizard (dcpromo.exe).

8. On the Welcome to the Active Directory Domain Services Installation Wizard page, click Next.

9. On the Operating System Compatibility page, review the warning about the default security settings for Windows Server 2008 R2 domain controllers, and then click Next.

10. On the Choose a Deployment Configuration page, click Existing forest, click Add a domain controller to an existing domain, and then click Next.

11. On the Network Credentials page, type the name of any existing domain in the forest where you plan to install the additional domain controller. Under Specify the account credentials to use to perform the installation, click My current logged on credentials and then click Set. In the Windows Security dialog box, provide the user name and password for an account that can install the additional domain controller. To install an additional domain controller, you must be a member of the Enterprise Admins group or the Domain Admins group. When you are finished providing credentials, click Next.

12. On the Select a Domain page, select the domain of the new domain controller, and then click Next.

13. On the Select a Site page, select a site from the list or select the option to install the domain controller in the site that corresponds to its IP address, and then click Next.

14. On the Additional Domain Controller Options page, make the following selections, and then click Next:
1. DNS server: This option is selected by default so that your domain controller can function as a Domain Name System (DNS) server. If you do not want the domain controller to be a DNS server, clear this option.

15. If you selected Use advanced mode installation on the Welcome page, the Source Domain Controller page appears. Click Let the wizard choose an appropriate domain controller or click Use this specific domain controller to specify a domain controller that you want to provide as a source for replication to create the new domain controller, and then click Next.

16. On the Location for Database, Log Files, and SYSVOL page, type or browse to the volume and folder locations for the database file, the directory service log files, and the system volume (SYSVOL) files, and then click Next.
Windows Server Backup backs up the directory service by volume. For backup and recovery efficiency, store these files on separate volumes that do not contain applications or other nondirectory files.

17. On the Directory Services Restore Mode Administrator Password page, type and confirm the restore mode password, and then click Next. This password must be used to start AD DS in Directory Service Restore Mode (DSRM) for tasks that must be performed offline.

18. On the Summary page, review your selections. Click Back to change any selections, if necessary.
To save the settings that you have selected to an answer file that you can use to automate subsequent AD DS operations, click Export settings. Type the name for your answer file, and then click Save.
When you are sure that your selections are accurate, click Next to install AD DS.

19. On the Completing the Active Directory Domain Services Installation Wizard page, click Finish.

20. You can either select the Reboot on completion check box to have the server restart automatically or you can restart the server to complete the AD DS installation when you are prompted to do so.

Note:- Once the replication is done between the 2003 DC and 2008 DC, you can either change their Static IP addresses or change the DHCP settings for preferred DNS servers, to point it to the new 2008 DC. The same above steps can be taken to add another Additional 2008 DC.

---------------------------------------------------------------------------------------

Alternate Access Mapping error

Issue:- Not able to change any settings in AAM
Error:-
Unexpected end of file while parsing Name has occurred. Line 29, position 13. at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseQName(Boolean isQName, Int32 startOffset, Int32& colonPos)
at System.Xml.XmlTextReaderImpl.ParseElement()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.LoadXml(String xml)
at Microsoft.SharePoint.Administration.SPAlternateUrlCollection.HasMissingUrl(String xml)
at Microsoft.SharePoint.Administration.SPContentDatabase.UpdateAlternateAccessMapping(SPAlternateUrlCollection collection)
at Microsoft.SharePoint.Administration.SPAlternateUrlCollection.UpdateAlternateAccessMappingInContent()
at Microsoft.SharePoint.Administration.SPAlternateUrlCollection.Update()
at Microsoft.SharePoint.ApplicationPages.EditOutboundUrlsPage.BtnSave_Click(Object sender, EventArgs e)
at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

This above error comes after installing April Cumulative pack for SharePoint 2007

This is the extract from the article http://support.microsoft.com/kb/973410 , which is included in the August cumulative update http://support.microsoft.com/kb/974982

"You have a Web application that has more than five incoming URLs. You cannot change Alternate Access Mappings (AAM) settings after you install the 2007 Microsoft Office system cumulative update that was released in April 2008"

There is one more article which has the same issue of editing URL's for more than 5 zone entrie, but does not have the parsing error. Still in this article there is no resolution given by MS. http://support.microsoft.com/kb/2000628

Change Secondary Schema to IE7 for SharePoint Designer 2007

Error:- "In Internet Explorer 6.0 the tag "" is not permitted.

In SharePoint Designer 2007, we need to change the Secondary Schema to IE7 so that certain tags would render without any errors.

On the machine where SharePoint Designer 2007 is installed:
1. Browse to %SystemDrive%\Program Files\Common Files\Microsoft Shared\OFFICE12\SCHEMAS\HTML
2. Copy the IE6_0.XSD and then rename the copied file to IE7_0.XSD
3. Open the IE7_0.XSD file using Notepad or Visual Studio and edit the following lines:
<-- xsd:schema color="#ff0000" targetnamespace="'http://schemas.microsoft.com/intellisense/<--font" version="1.0"><--xsd:schema color="#ff0000" targetnamespace="'http://schemas.microsoft.com/intellisense/<-- xsd:schema version="1.0" targetNamespace='http://schemas.microsoft.com/intellisense/ie7' elementFormDefault='qualified' xmlns='http://schemas.microsoft.com/intellisense/ie7' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:vs='http://schemas.microsoft.com/Visual-Studio-Intellisense' xmlns:fp='http://schemas.microsoft.com/FrontPageScripting'
vs:clientom="ie6_0dom.tlb"
vs:ishtmlschema="true"
vs:isserverschema="false"
vs:htmlflavor="4.0"
vs:MultipleScriptLanguages="true"
vs:cssschema="CSS 2.1"
vs:SuccinctFriendlyName="Internet Explorer 7">
Note: the DOM reference for client side IntelliSense (vs:clientom=”ie6_0dom.tlb) remains the same.
Save and close the file.

Next, open your registry and browse to:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Common\Schemas\] Note: This is on 32bit version machines

If you are using Windows Server 2008, 64bit machine
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\Common\Schemas

Create a new key and name it ie7_0.xsd and then create the following string values:
Value Name:- Abbrev Name
Value Data:- IE7
Value Name:- File
Value Data:- html\\ie7_0.xsd
Value Name:- Friendly Name
Value Data:- Internet Explorer 7.0
Value Name:- URI
Value Data:- http://schemas.microsoft.com/intellisense/ie7

Now, restart SharePoint Designer 2007 and click on Tools > Page Editor Options… In the Secondary Schema drop down select Internet Explorer 7.0. Click OK.

SharePoint 2010 Security Options

Note:- This is subject to change as this is not the Final release

The new options in 2010 we can see are in General Security and Information Policy
In General Security we have new options like,
1. Configure Managed Accounts. :- The service accounts used in SP 2010 are registered or we can register them manually before using the Account for a service.

When you Edit or Add a User account, you will get below options.

2. Configure password Change settings. :- In SP 2010 we have an option to change/reset service account passwords either Manual or Automatic selection. In either ways SharePoint will send notification email to User or Group of Users as configured in this setting.

3. Manage WebPart Security. :- This is quite Self Explanatory.
4. Configure Secure Token Service. :- Not exactly sure about this token service, but surely its related to other Applications and FARM’s who can use this (.svc) URL as endpoints for communication between them.

5. Manage Trust. :- It gives a message “There are no Trusted Identity Providers defined.”

----------------------------------------------------------------------------------

New Features in SharePoint 2010

Note:- These are subject to change as this is Beta Version.
There would be many others which I have missed, but these are the ones which are visible easily.

1. Database failover options, dependant on SQL mirroring.
2. Search, people, BDC, Excel Services all working as individual entities providing robust and
easy to maintain environment.
3. Access Database Integration at server level.
4. Fast Search Server.
5. Lotus Notes Connector for Crawling data.
6. New Connection options for importing User Profiles from different directories other than AD.
7. In-Built Monitoring and Health check on servers.
8. Enhanced options of Site Usage Reports, trimming reports and storing them directly to a library. Web Analytics Report.
9. Direct Edit option using SharePoint Designer 2010 only. Out of the box workflows can also be
edited.
10. New Site Templates [ bugs, projects, charity, Enterprise Wiki ]
11. Enhanced RSS Feed options. Tagging Options.
12. Major My Site template changes. Combination of facebook and newsgator features.
13. Granular Backup and Restore options for site collections and Individual Lists.
14. Recover data from unattached content databases.
15. GUI mode to integrate SQL Reporting services.
16. PowerShell Scripting and Management Console available.
17.Silverlight webpart and few more.
18.External Content Type options
19.Connection to any external application of another FARM which has service app .svc extension (not sure what is this as I am not into developing)