Specifics:
First machine: SharePoint single server Farm
Second machine: SQL 2005 with Report Services
Installed SP2 and RS Add-in, added SQL pc to farm, and followed steps to set
up integration, including changing SQL service accounts to domain accounts.
Everything went smoothly until we clicked on â'Set Server Defaultsâ' under
Reporting Services in SharePoint Central Admin and we got an error message:
An unexpected error occurred while connecting to the report server. Verify
that the report server is available and configured for SharePoint integrated
mode. --> Server was unable to process request. --> The request failed with
HTTP status 401: Unauthorized.
Nothing in the Event Log on the MOSS server but on the SQL server there is
an Event ID 529 â' unknown user name or bad password. This error message also
shows that the Logon Process and the Authentication Package are Kerberos.
We have beaten our heads against the wall trying to solve. Any help would be
appreciated.Did you check your Service Accounts in IIS and the Reporting Services setup
in SQL server. We had the same issue and it turned out to be we had missed
some of the accounts in Central Admin and IIS.
"AlisonZ" wrote:
> Specifics:
> First machine: SharePoint single server Farm
> Second machine: SQL 2005 with Report Services
> Installed SP2 and RS Add-in, added SQL pc to farm, and followed steps to set
> up integration, including changing SQL service accounts to domain accounts.
> Everything went smoothly until we clicked on â'Set Server Defaultsâ' under
> Reporting Services in SharePoint Central Admin and we got an error message:
> An unexpected error occurred while connecting to the report server. Verify
> that the report server is available and configured for SharePoint integrated
> mode. --> Server was unable to process request. --> The request failed with
> HTTP status 401: Unauthorized.
> Nothing in the Event Log on the MOSS server but on the SQL server there is
> an Event ID 529 â' unknown user name or bad password. This error message also
> shows that the Logon Process and the Authentication Package are Kerberos.
> We have beaten our heads against the wall trying to solve. Any help would be
> appreciated.
>
No comments:
Post a Comment