OLAP CUBE ERROR HELP NEEDED

R

raj

Current Cube Status

The cube scheduled to be built on 9/20/2004 at 3:43 AM
failed.

(457) This key is already associated with an element of
this collection

Does any one know what might be the issue and how can
this be resolved.

we have project server 2002. sql server 2000 on win 2000
box.
 
G

Gary L. Chefetz \(MVP\)

Raj:

This is most likely related to a duplicate project record or duplicate
assignment record. There are some known vulnerabilities in 2002 that are
fixed by SP1. Find the dupes, remove them and the cube will build.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-
 
M

Mike

Gary,

We have been having no issues with OLAP at all until last night. I checked
PWA's Manage enterprise features and found the following error.
The cube scheduled to be built on 1/18/2005 at 2:03 PM failed. (0)

When I tried to manually build the cube through PWA I get "Could not connect
to the OLAP server specified" error. I then went to the SQL server where the
OLAP cube is located and opened Analysis Services. I was able to build the
cube there so the cube itself should be OK. We are able to go into PWA and
see cube data but it is from the time before the job failed, so that would
indicate that the OLAPAdmin account is still intact. Finally, I checked the
services running on the application server that are related to OLAP: Project
Server Views Notification Service and Project Server Scheduled Process
Service and both are showing started. At this point I am not sure what else
to do other than to restart the Project Server Views Notification Service. I
could run PSCOM+ utility for OLAPAdmin, but this seems a little drastic since
we can get in and see data and create Analysis Services views with the old
data.

Mike
 
G

Gary L. Chefetz \(MVP\)

Mike:

The most likely cause is the OLAP Admin account being locked out, password
expired, etc. Please post error messages from the server event log and
specify which version you're using if you post again on this topic.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-
 
M

Mike

Gary:

I'm running Project Server 2003. SQL Server 2000

The password is set to never expire.

Mike
 
M

Mike

This is the error message in the application log when we try to do a manual
update

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>
 
G

Gary L. Chefetz \(MVP\)

Mike:

Were there any changes made to your SQL environment prior to this occurring,
such as service pack updates? What have you done to prove that the OLAP
account is working? Have you tried logging on to a system using this
account? Have you tried running the COM+ utility to reinitiate the identity?

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-
Mike said:
This is the error message in the application log when we try to do a manual
update

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>


Gary L. Chefetz (MVP) said:
Mike That means nothing. Accounts get locked with good passwords too! What
about the event log?

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-
PWA
and that
would the
old that
are
Click to expand...
Click to expand...
 
M

Mike

Yes, but as expected it did not resolve the issue. If we were having
difficulty viewing the OLAP data or unable to log into the SQL box using the
OLAP Admin account, I would say PSCOM+ would be the appropriate approach;
however, none of those symptoms exist. The build just stopped working.

Gary L. Chefetz (MVP) said:
Mike:

Were there any changes made to your SQL environment prior to this occurring,
such as service pack updates? What have you done to prove that the OLAP
account is working? Have you tried logging on to a system using this
account? Have you tried running the COM+ utility to reinitiate the identity?

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-
Mike said:
This is the error message in the application log when we try to do a manual
update

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>


Gary L. Chefetz (MVP) said:
Mike That means nothing. Accounts get locked with good passwords too! What
about the event log?

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-
Gary:

I'm running Project Server 2003. SQL Server 2000

The password is set to never expire.

Mike

:

Mike:

The most likely cause is the OLAP Admin account being locked out,
password
expired, etc. Please post error messages from the server event log and
specify which version you're using if you post again on this topic.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-
Gary,

We have been having no issues with OLAP at all until last night. I
checked
PWA's Manage enterprise features and found the following error.
The cube scheduled to be built on 1/18/2005 at 2:03 PM failed. (0)

When I tried to manually build the cube through PWA I get "Could not
connect
to the OLAP server specified" error. I then went to the SQL server
where
the
OLAP cube is located and opened Analysis Services. I was able to
build
the
cube there so the cube itself should be OK. We are able to go into PWA
and
see cube data but it is from the time before the job failed, so that
would
indicate that the OLAPAdmin account is still intact. Finally, I
checked
the
services running on the application server that are related to OLAP:
Project
Server Views Notification Service and Project Server Scheduled Process
Service and both are showing started. At this point I am not sure what
else
to do other than to restart the Project Server Views Notification
Service.
I
could run PSCOM+ utility for OLAPAdmin, but this seems a little
drastic
since
we can get in and see data and create Analysis Services views with the
old
data.

Mike

:

Raj:

This is most likely related to a duplicate project record or
duplicate
assignment record. There are some known vulnerabilities in 2002 that
are
fixed by SP1. Find the dupes, remove them and the cube will build.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-
Current Cube Status

The cube scheduled to be built on 9/20/2004 at 3:43 AM
failed.

(457) This key is already associated with an element of
this collection

Does any one know what might be the issue and how can
this be resolved.

we have project server 2002. sql server 2000 on win 2000
box.
Click to expand...
Click to expand...
Click to expand...
 
G

Gary L. Chefetz \(MVP\)

Mike:

Is this one-box installation or mutli-server? If it's multi-server, try
reapplying the SQL Service pack to the server on which Project Server is
running.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-
Mike said:
Yes, but as expected it did not resolve the issue. If we were having
difficulty viewing the OLAP data or unable to log into the SQL box using the
OLAP Admin account, I would say PSCOM+ would be the appropriate approach;
however, none of those symptoms exist. The build just stopped working.

Gary L. Chefetz (MVP) said:
Mike:

Were there any changes made to your SQL environment prior to this occurring,
such as service pack updates? What have you done to prove that the OLAP
account is working? Have you tried logging on to a system using this
account? Have you tried running the COM+ utility to reinitiate the identity?

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-
Mike said:
This is the error message in the application log when we try to do a manual
update

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>


:

Mike That means nothing. Accounts get locked with good passwords
Click to expand...
too!
What
about the event log?

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-
Gary:

I'm running Project Server 2003. SQL Server 2000

The password is set to never expire.

Mike

:

Mike:

The most likely cause is the OLAP Admin account being locked out,
password
expired, etc. Please post error messages from the server event
Click to expand...
log
and
specify which version you're using if you post again on this topic.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

-
Gary,

We have been having no issues with OLAP at all until last
Click to expand...
night.
I
checked
PWA's Manage enterprise features and found the following error.
The cube scheduled to be built on 1/18/2005 at 2:03 PM failed. (0)

When I tried to manually build the cube through PWA I get
Click to expand...
"Could
not
connect
to the OLAP server specified" error. I then went to the SQL server
where
the
OLAP cube is located and opened Analysis Services. I was able to
build
the
cube there so the cube itself should be OK. We are able to go
Click to expand...
into
PWA
and
see cube data but it is from the time before the job failed,
Click to expand...
so
that
would
indicate that the OLAPAdmin account is still intact. Finally, I
checked
the
services running on the application server that are related to OLAP:
Project
Server Views Notification Service and Project Server Scheduled Process
Service and both are showing started. At this point I am not
Click to expand...
sure
what
else
to do other than to restart the Project Server Views Notification
Service.
I
could run PSCOM+ utility for OLAPAdmin, but this seems a little
drastic
since
we can get in and see data and create Analysis Services views
Click to expand...
with
the
old
data.

Mike

:

Raj:

This is most likely related to a duplicate project record or
duplicate
assignment record. There are some known vulnerabilities in
Click to expand...
2002
that
are
fixed by SP1. Find the dupes, remove them and the cube will build.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-
Current Cube Status

The cube scheduled to be built on 9/20/2004 at 3:43 AM
failed.

(457) This key is already associated with an element of
this collection

Does any one know what might be the issue and how can
this be resolved.

we have project server 2002. sql server 2000 on win 2000
box.
Click to expand...
Click to expand...
Click to expand...
 
M

Mike

Is there any way to receive information from a sharepoint portal and view it
in a reporting format in either Project Web Access and or Windows SharePoint
Services?
 
M

Mike

When doing the PS Server 2003 configuration install, the procedure states
that a OLAP Admin domain account must be created then added to the Local
Administrator group on all servers and added to the OLAP Administrator group
on the database server . Is there anyway around having to add the OLAP Admin
account to the Local Administrator group on all the servers?
 
M

Mike

Here is the issue, the OLAP cube was not building prior to today, so we
removed the OLAPAdmin domain account from the local administrators group on
the database server & the Project Server. We were able to build an OLAP cube
but now were unable to view data in the Portfolio Analyzer in PWA.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

OLAP Cube error (457) 1
OLAP cube failed error message 1
OLAP Cube Generation Error 0
OLAP Cube issue 0
Error while building cubes-connection cannot be made 1
OLAP cube 1
OLAP Problem Again 3
Failed to build the OLAP cubes. Error: 0

Top