Hi Gary,
We're running SQL 8.00 with SP4. I'm pretty sure we haven't changed the
configuration recently, but we have had a couple of projects published
recently. One of these projects had illegal characters in the task names,
which I have removed and then saved the project. There was also a project
with an illegal character in the project name, which I rectified with the
project renamer tool and then published the project plan using the View
Populator tool. Hope this is helpful to some degree?
Cheers,
John
:
What version of SQL are you using and at what SP? We don't expect to see
errors like this in a normally operating system, so it may be some data in
the system that's causing the problems unless your configuration recently
changed.
Hi Gary,
We have a single dedicated server setup, using MS Project Server 2003 at
SP2a. PMs have MS Project 2003 with SP2. We upgraded to SP2a roughly six
months ago, and our system has run as smooth as a baby's derier since
then.
Is this enough, or would you like more info?
I have recently tried removing all .xml files from the viewdrop folder and
inserting them a few at a time. This seems to be working, and I am now
down
to c. 200 files left to process. I had a load of warning messages turn up
in
the log coinciding with me removing the files. The message is copied
below,
but I think its just telling me that the files disappeared, so the xml
couldn't be loaded? Presumably the 0x80004005 refers to Viewdrop
permissions?
Although "everybody" has permission to the Viewdrop folder.
Anyway, hope this is useful information. Once I've got all of the xml
files
processed, the next step I was going to try was to delete and recreate the
COM+ objects. Would this make a difference to how fast the xml files are
being loaded? I have certainly used the View Populator tool in the past to
publish all project plans, and I don't recall the xml being processed this
slowly before.
Cheers,
John
Event Type: Warning
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 1
Date: 13/09/2006
Time: 12:39:34
User: NT AUTHORITY\LOCAL SERVICE
Computer: PROJECT
Description:
Component: Views Notification Service
File: C:\Office\devsp\project\pcportal\source\viewsnotify\ViewNotify.cpp
Line: 186
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to load document into XML
DOM]]></Description>
___________________________________
Component: Views Notification Service
File: C:\Office\devsp\project\WebClient\source\utility\xmlhelpers.cpp
Line: 62
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to load document into XML DOM.
The
document follows: C:\Program Files\Microsoft Office Project Server
2003\BIN\VIEWDROP\FEEA5888-6BD5-40D3-9996-E664F9FA7075.xml]]></Description>
___________________________________
Component: msxml3.dll
Description: <Description><![CDATA[The system cannot locate the resource
specified.
]]></Description>
:
John:
Can you describe your system? What's the basic setup? What SP levels are
you
at with Project Server?
Sorry Gary,
I've been playing, trying to work out what's going on here, and I've
noticed
soemthing else weird. I used the View Populator tool to publish all of
the
project plans, and the tool said that they were all successfully
submitted
for publishing. I checked the Viewdrop folder, and now nearly 1.5hours
later,
all 319 files are still in the viewdrop folder! Another piece of the
jigsaw I
guess...
Cheers,
John
:
John:
When you build the cube manually, the system uses your logon
credentials
to
run the job. When you run it as a scheduled job, the system uses the
OLAPAdmin credentials you provided at setup to run the job. If there
were
something wrong with the OLAPAdmin account, such as the account being
disabled or the password expired, we'd see things working with a
manual
build and not with the scheduled build. Look in the server application
event
log for errors.
Marc,
OK, so this morning it failed to update properly again. Again the
message
stated the cube had built successfully, again no messages in the
event
log,
but again, PA did not display any data. So, now I have run the
TRUNCATE
SQL
query, deleted the Cube, rebuilt the cube, and have scheduled it to
build
in
the next half hour. I'll let you know what happens on that one, but
do
you
know why the data would appear when a "manual update" is done, but
when
scheduled, it disappears?
Cheers,
John
:
John,
At the very end make sure you give permission to 'everyone' in
Analysis
Manager to all cubes. If you don't do that you won't be able to
access
the
Cube from PWA.
Marc
--
MCP, EPM consultant
Basel, Switzerland
http://msepm.blogspot.com
:
Marc,
Cheers for the vey quick reply. I will display my ignorance now,
but
what do
you mean by truncate the tables. Not something I've done before,
at
least
knowingly!
Cheers,
John
:
John,
Besides deleting the cube in the Analysis Manager and thus
letting
it
build
from scratch again, you might want to truncate the three
following
tables
that are used for the cube building process:
MSP_CUBE_ASSN_FACT,
MSP_CUBE_RES_AVAIL_FACT and MSP_CUBE_TIME_BY_DAY .
Hard to say what really causes this behaviour though.
Hope this helps...
Marc
--
MCP, EPM consultant
Basel, Switzerland
http://msepm.blogspot.com
:
Hi All,
As of Monday morning, and therefore for the past three nights
I
have a
rather odd situation wrt my Cube. Each morning when I check
