Turn Off Tabs
Serena Business Manager 2009 R4 Readme
This readme file contains known issues and other important information for Serena® Business Manager This file also contains information that might not be available in other SBM documentation. Last updated on 2011-06-28. For third-party software information, refer to the SBM_Third_Party_Copyrights.txt and SBM_Third_Party_Licenses.txt files located on the Support download site or the DVD for this release.


Terminology Changes

The following terminology and component name changes have been made since the release of SBM 2009 R3.
Note: If you are upgrading from TeamTrack, refer to the Moving to Serena® Business Manager guide for terminology changes from TeamTrack to SBM.
Old Term New Term
Serena Business Mashups Serena® Business Manager or SBM
mashup process app
Mashup Server SBM Server
Configuration Utility SBM Configurator
Mashup Composer SBM Composer
Mashup Manager SBM Application Administrator
Mashup Administrator SBM System Administrator
Web interface SBM User Workspace
Mashup Repository SBM Application Repository
Mashup Script SBM AppScript
Mashup Registry AppCentral™
mashup tool event definition
mashup event event
Note: Systems created beginning with 2009 R4 include a Global Process App. In systems created before 2009 R4, the Global Process App is referred to as the Global Mashup.


This section provides general upgrade information and important notes for all upgrades to 2009 R4. Before you upgrade, review the following sections and proceed with the upgrade according to the version that you currently have installed.

Supported configurations, new features, and changes in behavior are listed in the Release Notes. Please refer to prior readmes for a list of features and changes that were added in another version before this release.

Upgrades from the following products and versions are supported in this release. Upgrades are supported from specified base releases and patches on those base releases.
  • TeamTrack 6.6.1.x
  • Serena Business Mashups 2008 R1.05 (Japanese version only)
  • Serena Business Mashups 2008 R2.0x
  • Serena Business Mashups 2009 R1.0x
  • Serena Business Mashups 2009 R2.0x
  • Serena Business Mashups 2009 R3.0x

New Installations of Serena Business Manager

If this is a new installation, download version 2009 R4 from http://www.serena.com/support and then follow the instructions in the Serena® Business Manager Installation and Configuration Guide to install Serena Business Manager for the first time.

Upgrading From TeamTrack 6.6.1.x

If you have TeamTrack 6.6.1.x installed, download version 2009 R4 from http://www.serena.com/support, and then follow the instructions in Moving to Serena® Business Manager. This guide only covers upgrades from TeamTrack.

Note: This version requires a database upgrade. Back up your existing database before installing this version.

You should also refer to solution S137372 to learn about the upgrade preparation utility.

Upgrading From Earlier Versions of SBM

To test this release, you must mimic your installation on a separate set of hardware. This test installation should include all environments used by your system. You can then upgrade and test this installation before upgrading your production installation. To upgrade successfully, 2009 R4 must be installed on each server machine and on each machine on which SBM Composer and SBM System Administrator are installed.

SBM 2009 R4 supports both major and minor upgrades:

Important Notes for Major and Minor Upgrades

The following notes apply to both major and minor upgrades:
  • You must disable the User Access Control setting before you install SBM on a Windows 2008 or 2008 R2. To disable this setting, perform the following steps:
    1. From the Windows Start menu, open the Control Panel and select User Accounts.
    2. On Windows 2008, open the User Accounts window and click Turn User Account Control on or off. On Windows 2008 R2, click Change User Account Control settings.
    3. On Windows 2008, clear the Use User Account Control (UAC) to help protect your computer check box. On Windows 2008 R2, move the slider to the Never notify position.
    4. Click OK.
    5. Reboot the server and perform the install.

    After the installation is finished, you can enable UAC; however, you must disable it again if you attempt to uninstall SBM.

  • Microsoft .NET Framework 3.5.1 must be installed on all Windows machines. If it is not detected, .Net Framework 3.5.1 is installed by SBM. To save download and installation time, you may want to install version 3.5.1 prior to running the SBM installer. Also, if you will not have Internet access during the installation, you should download and install 3.5.1 beforehand.
  • On Windows 2003 systems, the SBM installer requires Windows Installer 4.5 in order to install SQL Express without a system restart. (This is not a requirement if you are not installing SQL Express). If you do not pre-install Windows Installer 4.5, the SBM installer performs the install for you and prompts you to restart the system after you select the option to install SQL Express. When the system restart is finished, you must begin the installation again starting from the Welcome dialog. Therefore, to avoid an unscheduled system restart, download and install Windows Installer 4.5 from Microsoft, restart your server, and then install SBM. To determine if version 4.5 is already installed, open the command line and enter the following:
    msiexec -?
  • If you are connecting to a Microsoft SQL Server 2008 database, you must select the 2008 SQL Server Native Client driver. The SQL Server ODBC driver is not compatible with Microsoft SQL Server 2008.
  • If you upgrade to Windows 2008 in addition to upgrading SBM, you must enable the Web Server (IIS) role before you install the SBM Application Engine on a Windows 2008 server. If the Web Server (IIS) role is not already configured on your Windows 2008 server, see the "Enabling the Web Server (IIS) Role in Windows 2008 Server" section in the Serena® Business Manager Installation and Configuration Guide for steps to enable the role.
    Note: SBM requires Internet Protocol Version 4 (IPv4) on Windows 2008 systems (IPv6 alone will not work). Both IPv4 and IPv6 protocols can be enabled simultaneously on Windows 2008; however, SBM requires at least IPv4 on each Windows 2008 server in your SBM environment.
  • If you decide to enable or disable Single Sign-On (SSO) in your installation as part of the upgrade, you must also redeploy all of your deployed process apps.
  • Upgrade support for migrating to a 64-bit version of SBM is handled through a new suite installation on one or more 64-bit Windows 2008 R2 servers. You can either perform a Custom install that installs one or more SBM components on multiple 64-bit operating systems or you can perform a Complete install, which installs every component on a single 64-bit server. You can still perform Remote Administration tasks or connect directly to the database via ODBC using 32-bit clients.

    You can use the SBM System Administrator that is installed by the suite installer on a 64-bit Windows 2008 R2 server to upgrade the database. As part of the upgrade, review and upgrade any scripts and APIs that were originally created on a 32-bit operating system to ensure that they also run on a 64-bit system. For example, if you have any scripts that load .dll files, those dll files must be upgraded to run on a 64-bit machine.

    The hardware requirements for SBM running on a Windows 2008 R2 64-bit operating system are as follows. The memory requirements are greater than those for a 32-bit operating system.

    • Recommended Requirements – 2 GHz or higher multi-processors; 16 GB memory; 10 GB operational disk space.
    • Minimum Requirements – 800 MHz or higher single processor; 8 GB memory; 2.5 GB operational disk space.
  • For Oracle systems, you must perform the database upgrade using either the Mashup2009 DSN that is installed with SBM or a system DSN that uses the "Oracle for SBM" driver that is installed with SBM. As part of the 2009 R4 upgrade, the existing Mashup2009 DSN is automatically converted to use the new "Oracle for SBM" driver. If you attempt to use a DSN other than the Mashup2009 DSN provided by SBM, the SBM System Administrator prompts you to either use the Mashup2009 DSN or to modify or create a DSN that uses the "Oracle for SBM" driver.
  • The Application Administrator fails to launch on Oracle systems if the blocksize for the tablespace is less than 8k. To work around this problem, create a .dmp of the existing SBM Application Repository tablespace and restore it into a tablespace with a blocksize that is at least 8k.

Minor Upgrades

This section provides important notes and upgrade instructions for upgrades to 2009 R4 from version 2009 R3 and later.

Before you upgrade, review the information above in addition to the following topics:

Pre-upgrade Steps

Follow these steps before beginning the upgrade:

  1. Verify that 2009 R3 or later is installed on your system by opening the "About" box in the Web interface or Mashup Administrator. You can also view the current version of each component in the System Information tab of the SBM Configurator.
  2. Back up your existing database before installing this version.
  3. Back up the installation directory structure for Business Mashups on your Application Engine Web server machine.
  4. Download the release from support.serena.com.
  5. Stop the following services on the Application Engine Web server: Internet Information Services – IIS, Serena Common JBoss, and the Notification Server and Mail Client.
    Note: You can stop IIS and the Serena Common JBoss Service on the Manage Services tab of SBM Configurator.

Server Installation

Note that you must replace all client and server components for all environments. To upgrade to this release on all server machines:
  1. Extract the server installation files.
  2. On the server machine for each server component, launch the suite executable. An installer message prompts you to confirm that you are upgrading your system. Click Next to continue.
  3. The Upgrade Summary dialog box appears and summarizes the components that are currently installed on the server and ready for upgrade. The current installation directory that will be upgraded is noted as well. Click Upgrade Now to proceed.
    Note: For minor upgrades, if you want to uninstall existing components or install new components, you must use the Windows Add/Remove Programs utility to completely uninstall SBM and then perform a Custom install using the suite installer again (which performs a clean install). This process does not upgrade the current installation. It is recommended that you back up your existing SBM installation directory before you uninstall and reinstall with different component selections. Once the desired components are installed, continue to the next step and reconfigure your installation using SBM Configurator.
  4. At the end of the installation process, click Configure to launch SBM Configurator. You must complete the SBM Configurator wizard before you can access SBM.
    Note: If you are prompted to restart your server, SBM Configurator launches automatically once the server has restarted. (On Windows 2008 systems, you must launch SBM Configurator manually once the server has restarted). If you decline to restart the server at this time, you will not be able to run SBM Configurator until the server has restarted.
    When you launch SBM Configurator, it detects that you are upgrading your system and it upgrades the file system by merging existing configurations from your previous installation into the new installation files. After SBM Configurator is finished upgrading your file system, you can run it anytime thereafter to verify or modify your configuration settings as needed. Guidance is available by clicking the Help buttons throughout the wizard.
  5. Launch the SBM System Administrator and upgrade the SBM Application Engine database. You must use the SBM System Administrator installed with the suite installation package to upgrade the database. If you use multiple environments, you must perform this step for each database in each environment.
  6. Review the database upgrade log file in the Log folder of installationDirectory\Serena\SBM\Application Engine directory and correct any problems that occurred during the upgrade. If the log file is empty, no errors or warnings occurred during upgrade.
  7. Merge custom modifications to HTML templates, e-mail templates, and Web interface online help files made to your upgraded files. Backup templates are stored in a backup folder in the installationDirectory\Serena\SBM\Application Engine\Backup<version>-<date>-<time> directory.
    Note: Visit the knowledge base at support.serena.com and search for solution S137984 for a list of configuration files, template files, javascript files and strings that have changed in this release. You must manually merge some of your existing SSO customizations into the newly installed files after you upgrade your software and database.
    Important: If you installed the TeamTrack for ZMF integration prior to upgrading, you must manually restore the integration templates that are saved in the backup folder after the install. Serena recommends that you compare the installationDirectory\Serena\SBM\Backup<version>-<date>-<time> folder to the Application Engine\template folder and merge the missing files into the Application Engine\template folder.
  8. If you performed the previous step, open SBM System Administrator, select File, and then select Put Files in Database. ALL templates and images in the database are replaced by files on your local machine.
  9. Verify that these services are started: SBM Application Engine Web server (Internet Information Services - IIS), the Serena Common JBoss, and the Serena Broker Service.
    Note: You can start IIS and the Serena Common JBoss Service on the Manage Services tab of SBM Configurator.
  10. Instruct all SBM Composer users to install the client tools using the instructions in the following section (Client Installation). SBM System Administrator users who will use the Remote Administrator should also upgrade using the client installer.
  11. Instruct SBM User Workspace and SBM Application Administrator users to clear the cache in their Web browsers.

Client Installation

The client executable contains full versions of SBM Composer and SBM System Administrator and is intended to be run on client machines.

Previous versions of SBM Composer and SBM System Administrator do not need to be uninstalled before upgrading. The new versions are installed in the same location as the old versions.

To install SBM Composer and SBM System Administrator:

  1. Download the client installer from support.serena.com.
  2. Launch the installer by double-clicking the file.
  3. Click Next on the Welcome dialog box.
  4. Click Install to upgrade the current client installation.

Known Issues

This section describes known issues in SBM and contains the following categories:

Application Administrator, Deployment, and Promotion Issues

  • The Application Administrator fails to launch on Oracle systems if the blocksize for the tablespace is less than 8k. To work around this problem, create a .dmp of the existing SBM Application Repository tablespace and restore it into a tablespace with a blocksize that is at least 8k.

Installation and Configuration Issues

  • Some installations of SBM do not allow SBM Configurator to start the Serena Common JBoss service if HTTP Analyzer V6 is installed on the same machine. If you are unable to start JBoss from SBM Configurator, contact Support and refer to solution S138009 for further assistance. You can also use the Windows Services Manager to stop and start the Serena Common JBoss service if it will not start from SBM Configurator.
  • The Amazon widget fails to run and returns a 404 error unless version 2.0 of the ASP.NET Web service extension is installed and enabled in IIS. To verify that it is enabled, open IIS, select the Web Service Extensions folder, and search for ASP.NET. If the ASP.NET 2.0 status is prohibited, click Allow to enable it. If ASP.NET 2.0 is not installed, install it using the following prompts from the command line.
    On 64-bit servers, send the following command:
    C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727>aspnet_regiis.exe -I -enable
    On 32-bit servers, send the following command:
    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis.exe -I -enable
    Once you send the command, you should see the following:
    Start installing ASP.NET (2.0.50727).
    Finished installing ASP.NET (2.0.50727).

    Once the installation is finished, refresh the Web Service Extensions folder in IIS. You should see that ASP.NET v2.0.50727 is now installed. Click Allow if it is not enabled.

  • For new multi-environment installations (which contain development, test, and productions servers), it is recommended that you create unique databases to host the Common Log database in each environment. This ensures that the Common Log messages that you see are specific to each environment. To configure this type of installation, you must provide unique schema or database names for the Common Log database in the Database Servers tab of SBM Configurator on each SBM server installation (development, test, and production).

    For existing multi-environment installations (the development, test, and productions servers that you plan to upgrade), you can create new databases to host Common Log data for each environment. For example, you can back up your current Common Log database on your production server and restore it to a new space on your development database server. Once the data has been restored in the development database, purge the existing Common Log database space on the production database server and create a new database space for your test server and (this results in two blank databases--one for test and one for production). Run SBM Configurator on the test and development SBM servers and update the Database Servers tab with the database connection information for the two new unique Common Log databases. This ensures that you have unique databases for the Common Log in each environment and it also moves your existing Common Log data from the previous production space into the new development space.

  • Microsoft .NET framework 3.5.1 is not installed by the suite installer on Windows 2008 R2 servers if version 3.5.1 is not detected on the server. To work around this issue, navigate to the Control Panel, select Programs and Features, select Turn Windows features on or off, and install .NET 3.5.1 from the Features list.
  • On upgrade, SBM Configurator displays port 8243 as the SSL port for JBoss, even though you might not have configured SSL with JBoss in a older version. In prior versions, HTTPS was enabled by default because an HTTPS connector and sample certificate were provided by SBM. However, this sample configuration does not secure the SBM User Workspace. To secure end-user connections into SBM, run SBM Configurator in utility mode and select Security from the Advanced Settings menu. (The Single Sign-On (SSO) tab has been renamed to Security). In the SSL sub-tab, you can generate, import, or remove SSL certificates for the IIS and JBoss components that are installed on the server. This secures end-user connections into SBM as long as the request is sent using HTTPS.
  • System DSNs that use the "Oracle for SBM" driver cannot be deleted after SBM is uninstalled. To work around this issue, delete all DSNs that use the "Oracle for SBM" driver before you uninstall SBM. If you have already uninstalled SBM and you still need to delete a DSN that uses this driver, contact Support and refer to solution number S138013 for assistance.
  • The SBM Application Administrator product logo may not be visible after you upgrade to SBM 2009 R4. To workaround this problem, stop the Serena Common JBOSS service, and delete the work folder located here:


    After you remove the work folder, restart Serena Common JBOSS.

SBM User Workspace Issues

  • Links to auxiliary items cannot be added to primary items. To work around this problem, find the auxiliary item and add a link to the primary item.
  • In Update mode, the Rich Editable Grid uses the first found Update transition with the name "Update." Regular transitions named "Update" are not used in Update mode, but these transitions can be used when users select the "All Transitions" option for editing items in the grid.
  • Commas included in values for required Numeric float fields are not accepted as valid values.
  • Keyboard navigation features are not fully functional when users submit or transition items or use the Action drop down list inside the Rich Editable Grid.
  • When a user submits an item that goes into a decision state and then cancels a transition that is invoked as a result of a decision step, they receive an error message that indicates an item could not be found. The error message should state that the Submit action was successfully canceled.
  • Users who are granted the "View Attachments I Authored" privilege and no other "view attachments" privilege cannot see attachments they add to items when custom forms are used. To work around this problem, grant these users additional privileges to view attachments, such as the "View Attachments on Any Item," or use quick forms.
  • Users who are not granted privileges to view attachments are unable to view unrestricted attachments on items when custom forms are used. To work around this problem, grant these users privileges to view attachments or use quick forms.
  • The Back to Results link may be removed from the drill-down results list for Distribution reports. This typically happens when the drill-down results contain a large number of items, and users click the "All n" link at the bottom of the page to see the full list. To work around this problem, run the report again.
  • Users cannot use the Accessible Interface to complete Update transitions that require authentication. To work around this problem, users can switch to the regular SBM User Workspace to complete Update transitions that require authentication.
  • Database exceptions occur in Drill Through reports when a Multi-Selection or Multi-Relational field is used in the driving report to control the output of a secondary report. To work around this issue, use a field type other than Multi-Selection or Multi-Relational in the driving report.
  • Users may not notice the error when they provide an invalid value for a Numeric field on the Rich Editable Grid. This and other changes cannot be saved until the user provides a valid value.
  • For Editable Grid reports, when you select a value from a drop-down list, the value will not populate the field. You must immediately perform the action again on the drop-down list for the value to remain selected.

SBM Composer — General Issues

  • If a field does not have the Appears in report field list check box selected in its Property Editor, the field is not included in the Rule Palette, and therefore cannot be added to the left side of a rule expression. To work around this issue, select the check box, add the field to the rule expression, and then clear the check box to restore the original properties.
  • When a process app is upgraded to SBM 2009 R4, the new "application variables" design part is added, but the parent application does not get checked out. Data loss could result if a designer adds application variables and then checks out or gets the latest version of the parent application.

SBM Composer — Orchestration Issues

  • An asynchronous orchestration workflow fails if the name of the application that invokes it starts with a number. To work around this issue, do not use a number as the first character of an application.
  • A deadlock error could occur when running an orchestration workflow in a high-volume environment. For assistance, contact Customer Support and refer to solution S137994.
  • There could be runtime failures when an orchestration workflow has nested ForEach steps, and the output of the inner ForEach step is mapped directly to the input of a subsequent Service step. There could be deployment failures if the the output of the inner ForEach step is a complex type, one of its child elements has the Boolean data type, and that child element is mapped directly to the input of a subsequent Service step. For the workaround to both of these problems, go to solution D11937 .

SBM Application Engine and SBM System Administrator Issues

  • Role assignments are not copied when you copy a group. To work around this problem, edit the new group after it is created and add role assignments.

Single Sign-On (SSO) Issues

  • If you decide to enable or disable Single Sign-On (SSO) in your installation, you must also redeploy all of your deployed process apps.
  • You may experience performance problems if you use Single Sign-On (SSO) and enable automatic session renewal in the SBM Configurator. This problem occurs when a large number of users logs into the system at the same time. To work around this problem, disable automatic session renewal. This setting is located on the Security tab n the SBM Configurator.
  • The Single Sign-On (SSO) components included in the SBM 2009 R4 is incompatible with SSO components included within the released version of Dimensions CM 2009 R2 and CM 2009 R1. Users of SSO between SBM and Dimensions CM must install Dimensions CM 2009 R2.05 or later or upgrade to the major release CM 12.1 before upgrading to SBM 2009 R4. Dimensions CM 2009 R2.05 and Dimensions CM 12.1 are expected to be available inMarch 2011.

Web Services Issues

  • In SBM Web services version 7.2, Multi-Relational fields no longer accept a comma-separated list of internal (tableid:internal-item-id) values on update. Instead, you must specify values individually in an array of values to update a Multi-Relational field. If you are currently using an older version of SBM Web services, please note that you may need to alter any existing calls that use comma-separated lists to update Multi-Relational field values.
  • SBM fails to parse upper case Boolean values that you manually set in SBM Application Engine Web service calls that are sent from within SBM applications. SBM only accepts lower case Boolean values in addition to 0 or 1. To work around this problem, leave the value empty (accepting the default value).

Documentation Issues

  • The commands that appear in the Moving to Serena® Business Manager guide that illustrate how to execute the Unicode Upgrade Utility are incorrect. When you execute the utility, you must enter the utility name without any spaces. For example, use the following format:
    UnicodeUpgradeUtility "DSN=myDSN;UID=sa;PWD=sa"
    Instead of:
    Unicode Upgrade Utility "DSN=myDSN;UID=sa;PWD=sa"
  • The documentation incorrectly refers to the Enable Database Logging check box on the Database tab of the Settings dialog box in SBM System Administrator. This check box has been removed because administrative logging is now always enabled.

Issues with the Japanese Version

  • Suite and client installs are interrupted on Japanese versions of Windows 2008, Windows 7, and Windows Vista unless Web Service Enhancements (WSE) 3.0 is pre-installed. To work around this problem, download WSE 3.0 from Microsoft before running the suite or client installers.
  • The Template Reply Address label is truncated on the Mailbox Configuration tab for the Mail Client in SBM System Administrator.
  • SBM incorrectly appears on several tabs on the LDAP Setup and Tools dialog box in SBM System Administrator.
  • Some help topics in SBM Configurator appear in English instead of Japanese when you are on a Japanese operating system. To work around this problem, refer to the same topics in the Serena® Business Manager Installation and Configuration Guide for assistance.

Resolving InitExtension Failed Errors in the SBM User Workspace

On Windows 2003 servers, Internet Information Server (IIS) uses the IUSR_machinename (Internet Guest Account) account to access the SBM Application Engine database. If you are experiencing InitExtension Failed errors while trying to login to the SBM User Workspace, you may need to set correct privileges for the IUSR account. For SBM to function correctly, this IUSR_ account needs Full Control over the SBM directory. Also, the IUSR_ account needs to have Read and Execute permissions in the WINNT and WINNT\system32 directories.

If you upgrade to Windows 2008 in addition to upgrading SBM, the privileges above apply to the IIS Application Pool Identity instead of the IUSR account. The default Application Pool Identity is NetworkService on Windows 2008. For more information, see the Serena® Business Manager Installation and Configuration Guide.

Tracker Migration

There are two methods for migrating from Tracker to SBM. You can either:
  • Install the SBM System Administrator on a machine that hosts the Tracker Administrator. Create an application that contains at least one workflow and one project and use the Data Import Wizard to the import your Tracker data into this application. For detailed steps, see the SBM System Administrator Guide. Consider this option if you do not want to create SBM applications that are based on your existing Tracker projects.
  • Use TeamTrack 6.6.1.x to create solutions based on your Tracker projects and migrate your Tracker data before you upgrade to SBM. The Tracker solution wizard that creates SBM applications based on Tracker projects is not available in SBM because the wizard has been deprecated. Therefore, if you want to create SBM solutions based on Tracker projects, perform the following steps to create the solutions before you upgrade:
    1. Install TeamTrack 6.6.1.x on your Tracker server.
    2. Run the Tracker Solution Wizard in the TeamTrack Administrator client. Instructions for this task are included in the TeamTrack 6.6.1 Setup and Installation Guide.
    3. Upgrade your TeamTrack 6.6.1.x installation to SBM following instructions in the Moving to Serena® Business Manager.
    4. Import data from your Tracker projects using the Import Data Wizard in SBM System Administrator. You can use the solution mapping you defined in the Solution Wizard when you map fields for the import process. Instructions are provided in the SBM System Administrator Guide.
Both scenarios require you to install either the SBM System Administrator or the TeamTrack Administrator on your Tracker Adminstrator machine to perform the Tracker data migration.
Note: Serena Business Manager is now supported on the 64-bit version of Windows Server 2008; however, the Tracker migration utility is not available in the 64-bit version of the SBM System Administrator. Therefore, if you plan to run SBM on a 64-bit version of Windows 2008, you must first use the 32-bit version of SBM System Administrator on Windows 2003 or 2008 SP2 to migrate your Tracker data and then install SBM on your 64-bit server and connect it to your SBM database.

Build Numbers

The following component build numbers apply to version 2009 R4:

  • SBM User Workspace: 355
  • SBM Composer (32-bit): 182
  • SBM Composer (64-bit): 181
  • SBM System Administrator: 355
  • Application Administrator: 376
  • Database version: 904001002