OLAP-Cube Problem not resolved

[Henry]

Hi folks

I described in the past a OLAP communication problem where everything was
obviously OK, but was not.

I was able to create an OLAP cube in the Project Center w/o an error, but
the cube was not instantiated on a (different) SQL-Server. Find an error
log at the end. I now assume I have solved or better discovered the
reason why. At home, where I develop the set-up, I have SQL2000-Server
Enterprise, and at the company I am developing for they have
SQL2000-Server Standard. Is this the reason? When I browse over the pages
at MS and list the features of the different kind of packages, only the
Enterprise Edition supports the OLAP stuff, correct???

Thanks
Henry

------------- Old stuff, just as a reminder --------------------------
Started a new thread, because some time went by since my last posting,
what was not answered.

I still have this communication problem between the two servers (SQL vs.
Project Server), both running Analysis Services with SP3. Initiating the
cube does not spit out any error on the project Server, but looking in
the event log the eight(!) errors start with:

------------------- log starts -------------------------
25.06.2004 14:44:02 Microsoft Project Server Tracing Eventlog Provider
Fehler Keine 2 NT-AUTORIT’T\LOKALER DIENST AFG-PROJECT "File:
C:\Office\dev\project\WebClient\source\utility\pjadorsutil2.cpp
Line: 1691
Error Number: 0x80004005
Description: <Description><![CDATA[Assert Detected. The error code was
also included.]]></Description>
___________________________________

Description: <Description><![CDATA[Cannot find file
'<PC11DSN>\resglobal']]></Description>

------------------- log ends -------------------------

 

[Gary L. Chefetz \(MVP\)]

Henry

The edition of SQL server has nothing to do with it. You've got an
authentication issue, perhaps with the OLAP Admin account.

--

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

-

 

[Henry]

Thanks Gary,

I will x-check, but the user running the packages has admin priv. and is
an additional OLAP admin, what not necessarily mean, that there is not a
possible authentication issue. Do I have your point, that a SQL 2000
Standard Edition on a different server as the Project Server is no
inhibitor for OLAP cubes and the Portfolio Analyzer? (Even if on the
Microsoft pages in a comparison between a Standard and a Enterprise
Edition is mainly OLAP capabilities?)

Henry

Henry

The edition of SQL server has nothing to do with it. You've got an
authentication issue, perhaps with the OLAP Admin account.

--

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

-

[snip]

 

[Henry]

Gary,

just a brief addition, the Project Server SQL database makes no problem
on the same SQL server, the user (pmtool) is the same as the one that
likes to instantiate the cube, what does not work.

Henry

Thanks Gary,

I will x-check, but the user running the packages has admin priv. and is
an additional OLAP admin, what not necessarily mean, that there is not a
possible authentication issue. Do I have your point, that a SQL 2000
Standard Edition on a different server as the Project Server is no
inhibitor for OLAP cubes and the Portfolio Analyzer? (Even if on the
Microsoft pages in a comparison between a Standard and a Enterprise
Edition is mainly OLAP capabilities?)

Henry

Henry

The edition of SQL server has nothing to do with it. You've got an
authentication issue, perhaps with the OLAP Admin account.

--

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

-

[snip]

 

[Gary L. Chefetz \(MVP\)]

Henry:

Regarding the SQL edition, the differences between the editions is not
meaningful to the Project Server environment. I don't understand what you're
trying to say in your second reply.

--

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

-

Thanks Gary,

I will x-check, but the user running the packages has admin priv. and is
an additional OLAP admin, what not necessarily mean, that there is not a
possible authentication issue. Do I have your point, that a SQL 2000
Standard Edition on a different server as the Project Server is no
inhibitor for OLAP cubes and the Portfolio Analyzer? (Even if on the
Microsoft pages in a comparison between a Standard and a Enterprise
Edition is mainly OLAP capabilities?)

Henry

Henry

The edition of SQL server has nothing to do with it. You've got an
authentication issue, perhaps with the OLAP Admin account.

--

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

-

[snip]

 

[Henry]

Hi Gary,

I found a web site at MS, in the meantime I have the link ->
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/archite
c/8_ar_ts_1cdv.asp, where you can find a comparison between several types
of packages, and only the Enterprise Edition has support for analysis
capabilities like real-time OLAP cubes, etc. This may misguided me to
assume my problem is related to the different kinds of packages, because
everything what is listed in the table that has to do something with OLAP
cubes for analysis services, is not supported in the Standard Edition.
Possible, that I don't need all this stuff for the OLAP capabilities and
the Project Server.

You said I may have a authentication problem with the quite often missing
OLAP admin privileges, but this is not the case. I read the common
trouble with this issue and made sure a long time in advance that this is
not the reason for my problem. And my privileges at the company are close
to an administrator, they said. I installed all the packages under this
account, so I assumed no authentication problem. That is possibly the
wrong assumption.

I will investigate more next Tuesday at the company. (But I have no idea
where to look at the moment, because I can not verify this problem with
my environment, at home, everything works...)

Henry

Henry:

Regarding the SQL edition, the differences between the editions is not
meaningful to the Project Server environment. I don't understand what you're
trying to say in your second reply.

--

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

-

Thanks Gary,

I will x-check, but the user running the packages has admin priv. and is
an additional OLAP admin, what not necessarily mean, that there is not a
possible authentication issue. Do I have your point, that a SQL 2000
Standard Edition on a different server as the Project Server is no
inhibitor for OLAP cubes and the Portfolio Analyzer? (Even if on the
Microsoft pages in a comparison between a Standard and a Enterprise
Edition is mainly OLAP capabilities?)

Henry

Henry

The edition of SQL server has nothing to do with it. You've got an
authentication issue, perhaps with the OLAP Admin account.

--

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

-
Hi folks

[snip]
--

----------------------------------------------------------------------
snail mail : Henry Koplien \|/
From the Center of Nowhere o(O O)o
---- eMail : (e-mail address removed) ----ooOo---(_)---oOoo-----

 

[Henry]

Gary:

The problem is solved. It was not an authentication problem, nor was it a
misconfiguration problem. The reason was the migration of the SQL-Server.
The SQL migration wizard is not able to migrate a SQL database from one
server to another, at least with this admin in the company. He told me
that the ProjectServer database is now number seven out of 14, which
doesn't worked after migration. If the tool is crap or the admin, I don't
know and I don't want to investigate any further. In my case it was a
waste of time and much money.

I deinstalled the Project Server and made a fresh installation from
scratch, before erasing really everything in the SQL database related to
the Project-Server, because the deinstallation does not work adequate,
there are leftovers like the SQL User e.g. I configured afterwards all
the stuff with Team Services and so on, and everything behaved in a
perfect manner, including the OLAP cube, so you was definitely right, the
SQL Standard Edition is sufficient for the Project Server.

So thanks Gary for your assistance, even if it was not of any help for my
particular problem.
Henry

Hi Gary,

I found a web site at MS, in the meantime I have the link ->
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/archite
c/8_ar_ts_1cdv.asp, where you can find a comparison between several types
of packages, and only the Enterprise Edition has support for analysis
capabilities like real-time OLAP cubes, etc. This may misguided me to
assume my problem is related to the different kinds of packages, because
everything what is listed in the table that has to do something with OLAP
cubes for analysis services, is not supported in the Standard Edition.
Possible, that I don't need all this stuff for the OLAP capabilities and
the Project Server.

You said I may have a authentication problem with the quite often missing
OLAP admin privileges, but this is not the case. I read the common
trouble with this issue and made sure a long time in advance that this is
not the reason for my problem. And my privileges at the company are close
to an administrator, they said. I installed all the packages under this
account, so I assumed no authentication problem. That is possibly the
wrong assumption.

I will investigate more next Tuesday at the company. (But I have no idea
where to look at the moment, because I can not verify this problem with
my environment, at home, everything works...)

Henry

Henry:

Regarding the SQL edition, the differences between the editions is not
meaningful to the Project Server environment. I don't understand what you're
trying to say in your second reply.

--

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

-

and

is

an additional OLAP admin, what not necessarily mean, that there is not a
possible authentication issue. Do I have your point, that a SQL 2000
Standard Edition on a different server as the Project Server is no
inhibitor for OLAP cubes and the Portfolio Analyzer? (Even if on the
Microsoft pages in a comparison between a Standard and a Enterprise
Edition is mainly OLAP capabilities?)

Henry


In <[email protected]> "Gary L. Chefetz (MVP)"
wrote:

Henry

The edition of SQL server has nothing to do with it. You've got an
authentication issue, perhaps with the OLAP Admin account.

--

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

-
Hi folks


[snip]
--

----------------------------------------------------------------------
snail mail : Henry Koplien \|/
From the Center of Nowhere o(O O)o
---- eMail : (e-mail address removed) ----ooOo---(_)---oOoo-----