EPMFAQ
Project Server Help, FAQs, Blogs, and HowTos
This is The Header Then

Event ID 6398, 6482, and 7076 in your event logs?

posted February 9th, 2008 by Stephen Sanderlin
1 Star2 Stars3 Stars4 Stars5 Stars (3 votes, average: 4 out of 5)
Loading ... Loading ...

Are you seeing one or more of the following Event IDs (6398, 6482, and 7076) in your event log approximately every minute? Many of our clients have seen these errors indicating insufficient storage on their MOSS/WSS/Project Server farms, but are unable to find exactly what the errors refer to. Upon investigation, they generally find that there is sufficient memory and hard disk space on all servers in the farm (including SQL Server). However, even in cases where the amount of available storage is lacking, expanding the amount of available storage does not make the errors stop.

The full errors are:




Discuss this post on the EPMFAQ Blog Posts Forum.


Related Posts



Are your timer jobs inexplicably failing to complete?

posted January 24th, 2008 by Stephen Sanderlin
1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 5 out of 5)
Loading ... Loading ...

I recently encountered a situation where I would see literally hundreds of errors in the ULS logs like this:

01/18/2008 10:22:59.99 OWSTIMER.EXE (0×0600) 0×08F8 Windows SharePoint Services Timer 5uuf Monitorable The previous instance of the timer job ‘Config Refresh’, id ‘{3F51D43C-C7DD-403D-A63B-1163EA9B46A6}’ for service ‘{2F8D95DC-ECBF-4661-83AD-92CA4162CD4E}’ is still running, so the current instance will be skipped. Consider increasing the interval between jobs.

Every single Timer Job Definition was throwing these errors (sometimes hundreds of them) every time it was invoked. There were no other errors in the Application Log or ULS Logs, even with verbosity cranked all the way up. Alerts weren’t going out, the cube build was failing, and literally everything that relied on a timer job was nonfunctional. Restarting the Timer service alleviated the problem temporarily, but it would inevitably come back after the first invocation of the timer job.




Discuss this post on the EPMFAQ Blog Posts Forum.


Related Posts



Are you recieving a ReportingWssSyncListFailed error after modifying a Project Workspace or deploying a customized Project Workspace Template?

posted January 13th, 2008 by Stephen Sanderlin
1 Star2 Stars3 Stars4 Stars5 Stars (3 votes, average: 4.33 out of 5)
Loading ... Loading ...

A few of our clients have reported that after customizing a Project Workspace or deploying a customized Project Workspace, they begin to see Reporting (WSS Sync) errors in their queue:

Queue Errors

When they view the details of this error, they see the following details (duplicate lines removed for your convenience):

Error summary/areas:
Reporting Wss list sync failed
ReportingWssSyncListFailed
Reporting message processor failed
ReportingWSSSyncMessageFailed
Queue
GeneralQueueJobFailed

Error details:

<errinfo>
<general>
<class name="Reporting Wss list sync failed">
<error id="24018" name="ReportingWssSyncListFailed" uid="7e7fa8da-24d4-4c4d-a9ab-c32ed46e205c" SPListType="1100" Error="Failed to prepare the transfer of SP list 1100 for project ‘89ec6841-1f56-46b1-b97b-d775f0ca7e06′. The field Category was missing from the SP list and was ignored." />
</class>
<class name="Reporting message processor failed">
<error id="24016" name="ReportingWSSSyncMessageFailed" uid="79d63cef-5a83-46b1-bc6c-c0124311b60f" QueueMessageBody="ProjectUID=’89ec6841-1f56-46b1-b97b-d775f0ca7e06′. ForceFullSync=’False’" Error="RDS failed while trying to sync one or more SP lists. The RDS queue message will be retried." />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed" uid="b04b7077-731c-4149-87ac-89af07377229" JobUID="ba088e4e-781a-4bc4-b787-3e24ac2849ec" ComputerName="EPM2007DEMO" GroupType="ReportingWSSSync" MessageType="WSSSyncMessageEx" MessageId="1" Stage="" />
</class>
</general>
</errinfo>




Discuss this post on the EPMFAQ Blog Posts Forum.


Related Posts



Cube Build Failure: Your permissions on the server computer do not allow you to administer this Analysis server

posted December 22nd, 2007 by Stephen Sanderlin
1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 3.5 out of 5)
Loading ... Loading ...

When building a cube for the first time,  a deployer will sometimes see an error similar to the following error message in the Cube Status screen:

Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to delete the Olap database: PWA_AnalysisServices. Error: Your permissions on the server computer do not allow you to administer this Analysis server. Error:

Typically, this error is caused by failing to correctly or completely follow the directions outlined in this article on configuring Analysis Services 2005 to work with Project Server 2007. It can also caused by not restarting Analysis Services after you give the SSP account administrative permissions to Analysis Services — this does not appear in the aforementioned article, but it is sometimes required.




Discuss this post on the EPMFAQ Blog Posts Forum.


Related Posts




The opinions expressed on this site by the authors and those providing comments are theirs alone, and do not reflect the opinions of the respective employers of the authors or any employee thereof. Our respective employers are not responsible for the accuracy of any of the information supplied by on this site.

Terms of Use | Privacy Policy | Publishers

All content on this website is covered by the
Creative Commons Attribution-Share Alike 3.0 United States License.
Theme ©2007 The Heckerped WordPress Theme created by JTk of Doc5 under the Creative Commons Attribution License.