Issue With "SYSTEM_DO_NOT_USE Diskgroup and Importing Bitmaps and Icons

[Stephen_Beck]

We have a new TEST environment we are setting up.  When the diskgroups were set up, a mistake was made with the SYSTEM diskgroup.  The diskgroup name was changed to SYSTEM_DO_NOT_USE in config and a new SYSTEM diskgroup was set up.  The diskgroup number for SYSTEM_DO_NOT_USE is 101 and the diskgroup number for SYSTEM is 102.  They both point to the same share UNC path.  All of the System Document document types are configured for the SYSTEM diskgroup and when typical System Documents are created such as configuration reports, they are stored and retrieved with no problems. 

When we try to load icons and bitmaps in the Thick Client we get a Platter Management Error twice:

"Problem locating ID File For Disk Group: The uncommitted copy of the Disk Group is currently off line.  Please contact your system administrator."

System ID:    1111

Disk Group Name: SYSTEM_DO_NOT_USE

Disk Group# 101

Volume # 1

Copy #  1

Error GetIdFile2: -3

and then a message: "an error occurred while copying C:\Users\<username>\AppData\Local\Temp\ver_107.tmp to the destination disk group."

Does this have something to do with the Disk Number for SYSTEM being 102 instead of 101?  If not, what could be casuse

Here is some code from the Thick Client verbose file:

Insert into hsi.pltrmgmtlog ( usernum, registernum, logdate, severityflag,
 userresponse, messagetext, actionnum, subactionnum, diskgroupnum,
 logicalplatternum, physicalplatternum, tracelvl ) values ( 2, 102, {fn now()},
 0, 0, 'Disk Group Name: SYSTEM_DO_NOT_USE  Disk Group #:    101  Volume #:    
   1  Copy #:          1 

[AdamShaneHyland · Accepted solution]

Hi Steve,

Thanks for the post.  This is a common issue.

The >>System Bitmaps and Icon importer process is designed to look for the System disk group in the standard location, which is disk group #101.  This can be overridden easily, for systems which are licensed for DIP, by changing the Settings for the DIP process to specify the Disk Group as System.  However, if the system does not have a DIP license, you would need to reach out to your first line of support to make the necessary updates.

If the system has a DIP license, to solve this problem the Bitmap Import Dip Process should be reconfigured selecting the corresponding System Document Disk Group in Configurator | Import | Document Import Processor and in settings for >>System Bitmap and Icon Importer.

Hope this helps.