Article ID: 817837 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
When you build an On-Line Analytical Processing (OLAP) cube, Microsoft Project Server cannot use the date values that you specified in the fixed Date range option.
This problem occurs because Microsoft Project Server cannot use the date range that you specify in the Use the fixed date range specified below option when you build the cube by using the scheduling service.
Part 1: Download and Install the Update
Service Pack InformationThis problem is corrected in Project Server 2002 Service Pack 1.
To resolve this problem, obtain the latest service pack for Project Server 2002. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/867830/ )How to obtain the latest Microsoft Project Server 2002 service pack
Hotfix InformationA supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Project service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMSNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The global version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
After the hotfix is installed, the following files will have the listed attributes or later:
Date Time Size File name ------------------------------------------- 03-Apr-2003 20:29 4,018,688 Prjsvr10.msp
Date Time Version Size File name ----------------------------------------------------------- 03-Apr-2003 20:29 n/a 4,018,688 Prjsvr10.msp 24-Mar-2003 21:24 10.0.2003.324 320,000 Atlconv.dll 24-Mar-2003 21:45 n/a 611 Build.inc 05-Sep-2002 19:19 n/a 6,133 Clntutil.asp 24-Mar-2003 19:58 n/a 1,550 Comlib.asp 05-Sep-2002 19:19 n/a 13,525 Dlmain.asp 24-Mar-2003 19:58 n/a 9,110 Grid.asp 05-Sep-2002 19:19 n/a 6,946 Issshell.asp 05-Sep-2002 19:19 n/a 16,837 Linkissu.asp 24-Mar-2003 19:58 n/a 13,927 Locstr.asp 24-Mar-2003 19:58 n/a 22,744 Modtool.asp 19-Feb-2003 00:08 10.2003.0.218 126,976 Mspnav.dll 05-Sep-2002 19:19 n/a 3,975 New4task.asp 11-Mar-2003 02:05 10.2003.0.310 630,784 Pds.dll 09-Oct-2002 19:31 10.0.2002.1009 909,824 Pj10od10.dll 25-Mar-2003 00:56 n/a 912,779 Pjclient.cab 28-Jan-2003 05:08 10.0.2003.127 188,928 Pjnpe.dll 01-Oct-2002 01:00 10.0.2002.930 167,936 Pjobjprv.dll 24-Mar-2003 21:24 10.0.2003.324 4,108,800 Pjoledb.dll 03-Dec-2002 01:06 n/a 30,535 Portview.asp 06-Aug-2002 18:16 n/a 3,584 Prjsvre.mst 03-Apr-2003 02:12 10.2003.0.402 307,200 Projolap.dll 03-Apr-2003 02:15 10.2003.0.402 57,344 Psvracub.dll 03-Dec-2002 01:06 n/a 96,082 Qylibstd.sql 05-Sep-2002 19:19 n/a 53,683 Svrdbdl.asp 02-Apr-2003 21:32 n/a 20,991 Tsktrans.asp 24-Mar-2003 19:58 n/a 1,069,326 Websps.sql
Part 2: Activate the UpdateTo activate this update and to make sure that your Microsoft Project Server has all of the fixes that are contained in this update applied correctly, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Project Server 2002 Service Pack 1.