S
Storr, Gary
I have a bit of a problem on our Project Server setup that is got me totally
stumped . Specifically it is with Sharepoint and OLAP Analysis Services. My
setup is the following:
- server1 running MS Project Server PWA
- server2 running SQL Server as the Project Database
- server3 running Sharepoint Team Services as our Sharepoint Server
- server3 running SQL Server as the Analysis Services Server.
All configuration and all components of the system were running fine (PWA,
OLAP, Sharepoint). Cubes were being built daily and issues were being
logged. Then Friday I was forced (corporate policy) to reset my WinNT
password. My ID happened to be the 'impersonated' ID (using PSCOM+) on the
Project Server to access both OLAP and Sharepoint on server3. Since that
time I cannot build a cube from Analysis Services or access Sharepoint
Issues. Sharepoint documents work fine from PWA, and all other aspects of
Project Server are preforming normally.
Error messages I receive:
Sharepoint:
Microsoft Project Web Access Documents and Issues are based on SharePoint
Team Services from Microsoft.
There is a problem establishing a connection with the Web server running
SharePoint Team Services. Please contact your system administrator.
OLAP:
(-2147221424) Cannot open connection to Analysis server 'server3'. Security
error [The user could not be authenticated] ''
What I've tried:
Reset (numerous times) my Win ID/password on server1using PSCOM+
Ran proxycfg on server1 to 'reset' proxy services (proxycfg -d -p
"noproxyserver" "<local>"). We don't use a proxy so this is per
documentation.
Ran IISRESET on server1
Checked that my ID in an administrator on both server1 and server3
Checked SQL Server permissions on server3 to ensure I have db_datareader
permissions.
Restarted the SQL Server base on server3
Rebooted server3
Numerous other suggestions that I have found on the MS knowledge base or
newsgroups
Clearly it seems to be an authentication error but everything seems to be in
order. The only change was my password. I cannot seem to get this resolved
and is impacting our production base. Any help would be greatly appreciated.
stumped . Specifically it is with Sharepoint and OLAP Analysis Services. My
setup is the following:
- server1 running MS Project Server PWA
- server2 running SQL Server as the Project Database
- server3 running Sharepoint Team Services as our Sharepoint Server
- server3 running SQL Server as the Analysis Services Server.
All configuration and all components of the system were running fine (PWA,
OLAP, Sharepoint). Cubes were being built daily and issues were being
logged. Then Friday I was forced (corporate policy) to reset my WinNT
password. My ID happened to be the 'impersonated' ID (using PSCOM+) on the
Project Server to access both OLAP and Sharepoint on server3. Since that
time I cannot build a cube from Analysis Services or access Sharepoint
Issues. Sharepoint documents work fine from PWA, and all other aspects of
Project Server are preforming normally.
Error messages I receive:
Sharepoint:
Microsoft Project Web Access Documents and Issues are based on SharePoint
Team Services from Microsoft.
There is a problem establishing a connection with the Web server running
SharePoint Team Services. Please contact your system administrator.
OLAP:
(-2147221424) Cannot open connection to Analysis server 'server3'. Security
error [The user could not be authenticated] ''
What I've tried:
Reset (numerous times) my Win ID/password on server1using PSCOM+
Ran proxycfg on server1 to 'reset' proxy services (proxycfg -d -p
"noproxyserver" "<local>"). We don't use a proxy so this is per
documentation.
Ran IISRESET on server1
Checked that my ID in an administrator on both server1 and server3
Checked SQL Server permissions on server3 to ensure I have db_datareader
permissions.
Restarted the SQL Server base on server3
Rebooted server3
Numerous other suggestions that I have found on the MS knowledge base or
newsgroups
Clearly it seems to be an authentication error but everything seems to be in
order. The only change was my password. I cannot seem to get this resolved
and is impacting our production base. Any help would be greatly appreciated.