B
Brian Tkatch
Project 2003.
In PWA, under Admin=>Manage Enterprise Features, we have a cube setup,
but updating it results iun the error:"Could not connect to the OLAP
server specified.".
Connecting to Analysis Services directly (which is on the same server
as Project Server) does compile the cubes without error. Also, using
the same settings in PWA on another instance of Project Server
(different box) works fine too. The actual database used by Analysis
Services for the cube is on another Project server.
When the error appears, the server show 9 Application Log entires, and
13 Security Log entires.
The 9 Application log entries are 7 successful successive logins (for
the same user) and two errors:
--------------------------------------------------------------------------------------
Component: MSP Resource Availablity Refresh and OLAP Cube Creation
Component (ProjOLAP)
File: PROJOLAPProcess
Line: 1
Description: <Description><![CDATA[DSO.Server.Connect failed with
error message 'Bad file name or number' Error Number :
'52]]></Description>
--------------------------------------------------------------------------------------
Component: MSP Resource Availablity Refresh and OLAP Cube Creation
Component (ProjOLAP)
File: PROJOLAPProcess
Line: 1
Description: <Description><![CDATA[Error #: 0 Desc. :]]></Description>
--------------------------------------------------------------------------------------
The 13 Security Log entires are 11 logon messages, as follows:
Logon Attempt, Logon attempt using explicit credentials, Successful
Logon, Special privileges assigned to new logon, User Logoff. And
repeated a second time for the same user, (that's 10), and a
Successful Network Logon for NTLM.
The final two are similar Failure Audits for the same user that logged
in twice:
------------------------------------------------------------------------------
Logon Failure:
Reason: An error occurred during logon
User Name: xxxxxxxx
Domain: xxxxxxxx
Logon Type: 3
Logon Process: ”ðú
Authentication Package: NTLM
Workstation Name: xxxxxxxx
Status code: 0xC000006D
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: xxx.xxx.xxx.xxx
Source Port: 0
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
------------------------------------------------------------------------------
Note the peculiar Logon Process name.
Checking on DSO and PivotTable versions, the two systems have similar
version between the two systems, except for one file:
File lists garnered from:
<URL:http://msdn2.microsoft.com/en-us/library/aa936726(SQL.80).aspx>
and <URL:http://msdn2.microsoft.com/en-us/library/ms135462.aspx>.
Working Not Working
atl.dll 3.5.2283.0 3.5.2283.0
msdmeng.dll 8.0.2039.0 8.0.2039.0
msdmine.dll 8.0.2039.0 8.0.2039.0
msmdcb80.dll 8.0.2039.0 8.0.2039.0
msmdcube.dll 7.0.1458.219 7.0.1458.219
msmdgd80.dll 8.0.2039.0 8.0.2039.0
msmdgdrv.dll 7.0.1460.531 7.0.1460.531
msmdun80.dll 2000.80.382.0 2000.80.2039.0
msolap80.dll 8.0.2039.0 8.0.2039.0
msolap.dll 7.0.1458.219 7.0.1458.219
msolapr.dll 7.0.1458.219 7.0.1458.219
msolapui.dll 7.0.0.1458 7.0.0.1458
msolui80.dll 8.0.0.2039 8.0.0.2039
msvbvm60.dll 6.0.97.82 6.0.97.82
msdmine.rll 8.0.2039.0 8.0.2039.0
msolap80.rll 8.0.2039.0 8.0.2039.0
olapuir.rll 8.0.2039.0 8.0.2039.0
Msmddo80.dll 8.5.0.1054 8.0.0.2039
Msmddo.dll 8.5.0.1054 8.0.0.2039
Msmdlock.dll 8.5.1054.0 8.0.2039.0
Msmdnet.dll 8.5.1054.0 8.0.2039.0
Msmdso.rll 8.5.1054.0 8.0.2039.0
Replacing msmdun80.dl on the non-working server with the newr version
does not seem to help. (Though, i didn't restart anything.)
Any ideas?
B.
In PWA, under Admin=>Manage Enterprise Features, we have a cube setup,
but updating it results iun the error:"Could not connect to the OLAP
server specified.".
Connecting to Analysis Services directly (which is on the same server
as Project Server) does compile the cubes without error. Also, using
the same settings in PWA on another instance of Project Server
(different box) works fine too. The actual database used by Analysis
Services for the cube is on another Project server.
When the error appears, the server show 9 Application Log entires, and
13 Security Log entires.
The 9 Application log entries are 7 successful successive logins (for
the same user) and two errors:
--------------------------------------------------------------------------------------
Component: MSP Resource Availablity Refresh and OLAP Cube Creation
Component (ProjOLAP)
File: PROJOLAPProcess
Line: 1
Description: <Description><![CDATA[DSO.Server.Connect failed with
error message 'Bad file name or number' Error Number :
'52]]></Description>
--------------------------------------------------------------------------------------
Component: MSP Resource Availablity Refresh and OLAP Cube Creation
Component (ProjOLAP)
File: PROJOLAPProcess
Line: 1
Description: <Description><![CDATA[Error #: 0 Desc. :]]></Description>
--------------------------------------------------------------------------------------
The 13 Security Log entires are 11 logon messages, as follows:
Logon Attempt, Logon attempt using explicit credentials, Successful
Logon, Special privileges assigned to new logon, User Logoff. And
repeated a second time for the same user, (that's 10), and a
Successful Network Logon for NTLM.
The final two are similar Failure Audits for the same user that logged
in twice:
------------------------------------------------------------------------------
Logon Failure:
Reason: An error occurred during logon
User Name: xxxxxxxx
Domain: xxxxxxxx
Logon Type: 3
Logon Process: ”ðú
Authentication Package: NTLM
Workstation Name: xxxxxxxx
Status code: 0xC000006D
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: xxx.xxx.xxx.xxx
Source Port: 0
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
------------------------------------------------------------------------------
Note the peculiar Logon Process name.
Checking on DSO and PivotTable versions, the two systems have similar
version between the two systems, except for one file:
File lists garnered from:
<URL:http://msdn2.microsoft.com/en-us/library/aa936726(SQL.80).aspx>
and <URL:http://msdn2.microsoft.com/en-us/library/ms135462.aspx>.
Working Not Working
atl.dll 3.5.2283.0 3.5.2283.0
msdmeng.dll 8.0.2039.0 8.0.2039.0
msdmine.dll 8.0.2039.0 8.0.2039.0
msmdcb80.dll 8.0.2039.0 8.0.2039.0
msmdcube.dll 7.0.1458.219 7.0.1458.219
msmdgd80.dll 8.0.2039.0 8.0.2039.0
msmdgdrv.dll 7.0.1460.531 7.0.1460.531
msmdun80.dll 2000.80.382.0 2000.80.2039.0
msolap80.dll 8.0.2039.0 8.0.2039.0
msolap.dll 7.0.1458.219 7.0.1458.219
msolapr.dll 7.0.1458.219 7.0.1458.219
msolapui.dll 7.0.0.1458 7.0.0.1458
msolui80.dll 8.0.0.2039 8.0.0.2039
msvbvm60.dll 6.0.97.82 6.0.97.82
msdmine.rll 8.0.2039.0 8.0.2039.0
msolap80.rll 8.0.2039.0 8.0.2039.0
olapuir.rll 8.0.2039.0 8.0.2039.0
Msmddo80.dll 8.5.0.1054 8.0.0.2039
Msmddo.dll 8.5.0.1054 8.0.0.2039
Msmdlock.dll 8.5.1054.0 8.0.2039.0
Msmdnet.dll 8.5.1054.0 8.0.2039.0
Msmdso.rll 8.5.1054.0 8.0.2039.0
Replacing msmdun80.dl on the non-working server with the newr version
does not seem to help. (Though, i didn't restart anything.)
Any ideas?
B.