Está en la página 1de 45

iFIX Error Messages in the Ebooks

Contents
Recipe Builder ......................................................................................................4
Uploading and Downloading Messages ...................................................................................13 Audit Trail for Recipe Builder.....................................................................................................14 Other Recipe.............................................................................................................................18

Auto Alarm Manager...........................................................................................1 !erminal "er#er...................................................................................................$1 "ecurit% "%nchroni&er........................................................................................$$


Application rror !odes "#$$%#&&'............................................................................................#3 User Account rror !odes "1$$%1&&'........................................................................................#4 (eneral rror !odes "1%&&'.......................................................................................................#) !o**and +ine ,ara*eter rrors..............................................................................................#)

'istorical Assign ...............................................................................................$( 'istorical Collect ...............................................................................................$) 'istorical *ispla% ...............................................................................................$ +et,ork Error Codes..........................................................................................-1
-tartup rror !odes...................................................................................................................31 Run%ti*e rror !odes................................................................................................................31

Application .alidator..........................................................................................-$ Importing iFIX /ictures into /ro0ic% /ortal......................................................-"12 !rigger Block Alarms and Block Errors .................................................-4 iFIX and FIX on the "ame Computer.................................................................-4 *atabase Manager..............................................................................................-4 Mission Control...................................................................................................-3
AAM Ta. ..................................................................................................................................3/ -0+ Ta.....................................................................................................................................38

"12 "er#er..........................................................................................................-4 *isco#er% And Auto5Assembl% Component 6*AC7.........................................48 **E.......................................................................................................................48 Access.................................................................................................................4'istorian "er#er..................................................................................................4.isiconX...............................................................................................................4"%stem Messages ..............................................................................................44 9/C Errors..........................................................................................................44 Alarming..............................................................................................................44 iFIX 9*BC............................................................................................................44

Recipe Builder
Message Are 1ou sure 1ou want to clear all o2errides3 Meaning and Action The Recipe Builder is a.out to delete all the 2alues in the O2erride 4alue colu*n of the recipe. -elect the 5es .utton to delete these 2alues or the 6o .utton to a.ort the procedure. The Recipe Builder is a.out to delete the recipe recipe_name and all the files associated with it. -elect the Delete .utton to delete these files or select the !ancel .utton to a.ort the procedure. The Recipe Builder is atte*pting to calculate the arccosine of a nu*.er that is greater than one and less than negati2e one. Ret1pe the for*ula using a 2alue that is .etween 1 and %1. The Recipe Builder is atte*pting to calculate the arcsine of a nu*.er that is greater than one and less than negati2e one. Ret1pe the for*ula using a 2alue that is .etween 1 and %1. 5ou opened a te7t recipe with an in2alid entr1 in the audit trail field. 4alid entries are: 6o Audit Trail; -u**ar1 Audit Trail; and Detailed Audit Trail. Modif1 the te7t recipe using the guidelines in the section diting a Te7t Recipe. The Recipe Builder is atte*pting to calculate the .ase 1$ log of a nu*.er that is less than one. Ret1pe the for*ula using a 2alue that is greater than or e=ual to one.

Are 1ou sure 1ou want to delete recipe recipe_name3

Bad arccosine e7pression "operand 8 %1 or 9 13'

Bad arcsine e7pression "operand 8 %1 or 9 13'

Bad audit trail support option

Bad .ase%1$ log e7pression "operand 8<$3'

Bad di2ision e7pression "di2ide The Recipe Builder is atte*pting to di2ide two nu*.ers. ?owe2er; .1 >ero3' the di2isor is in2alid and *a1 e=ual >ero. Ret1pe the for*ula using a 2alue for the di2isor that is non%>ero. Bad natural log e7pression "operand 8< $3' The Recipe Builder is atte*pting to calculate the natural log of a nu*.er that is less than or e=ual to >ero. Ret1pe the for*ula using a 2alue that is greater than >ero. The Recipe Builder is atte*pting to calculate the s=uare root of a negati2e nu*.er. Ret1pe the for*ula using a 2alue greater than or e=ual to >ero. The Recipe Builder cannot delete the recipe file; filename. The file *a1 ha2e one or *ore attri.utes set to pre2ent deletion or *a1 .e in use "for e7a*ple; fro* a file ser2er'. -elect the 5es .utton to continue deleting recipe files or select the 6o .utton to stop deleting files. Ahile starting; the Recipe Builder could not locate its displa1 for*at file; D BAU+T.RBT. The file *a1 not e7ist or *a1 ha2e

Bad s=uare root e7press "operand 8 $3'

!an@t delete Recipe file filename. Do 1ou want to continue deleting the files for this recipe3

!an@t open displa1 for*at file

Message

Meaning and Action .een rena*ed. To create the file; custo*i>e the displa1 for*at as needed and sa2e it in the +ocal path.

!annot displa1 the -ecurit1 Areas list

The Recipe Builder is una.le to displa1 the list of a2aila.le securit1 areas. The -A6AM -.!B( file "which includes the list of securit1 area na*es' *a1 .e da*aged or rena*ed. !onsult 1our s1ste* ad*inistrator .efore proceeding. The Recipe Builder cannot upload fro* the data.ase .ecause it cannot read fro* the re=uested tagna*e. The .locC in *e*or1 *a1 .e corrupt or there *a1 .e a co**unications pro.le*. Tr1 reloading the data.ase and; if the .locC resides on a re*ote node; *aCe sure networC co**unications are functioning properl1. The Recipe Builder cannot open the specified file .ecause it is not a recipe or does not ha2e a recogni>a.le e7tension. Bor a list of recipe e7tensions; refer to the chapter Recipe Biles. The Recipe Builder is una.le to locate or use the s1ste* clip.oard file. The file *a1 ha2e .een rena*ed or is corrupt. The Recipe Builder cannot upload data fro* the data.ase. There *a1 .e a co**unications pro.le* or the data.ase in *e*or1 *a1 .e corrupt. Tr1 reloading the data.ase and; if the .locC resides on a re*ote node; *aCe sure networC co**unications are functioning properl1. The Recipe Builder is una.le to paste data fro* the s1ste* clip.oard. Tr1 cop1ing a single row to the clip.oard and pasting it .acC into the recipe. 5ou atte*pted to sa2e a *aster .acCup or a control .acCup recipe. -elect a different recipe t1pe and tr1 sa2ing the recipe again. The e7tension 1ou specified does not ha2e a recogni>a.le e7tension. Bor a list of recipe e7tensions; refer to the chapter Recipe Biles. 5ou atte*pted to sa2e a new recipe fro* the Recipe Operations window. -witch to the Recipe De2elop*ent window and tr1 sa2ing the recipe again. 5ou entered a .atch si>e in the -et Batch -i>e dialog .o7 that: Ds greater than &;&&&;&&&.$; Ds less than $.$$$$$$1; !ontains a negati2e nu*.er; or

!annot fetch data due to .ad node:tag.field

!annot open a non%recipe file

!annot open clip.oard

!annot read data fro* data.ase

!annot read fro* clip.oard

!annot sa2e a .acCup recipe file

!annot sa2e a non%recipe file

!annot sa2e an untitled recipe file

!annot set .atch si>e "reason'

Message

Meaning and Action !ontains non%nu*eric data. Ret1pe the .atch si>e 1ou want and tr1 again.

!annot set tag group "!annot delete tag group assign*ent while su.stitutions are on'

5ou atte*pted to delete or re%assign a tag group while the Recipe Builder is su.stituting tagna*es for s1*.ol na*es. !licC the !ancel .utton on the Assign Tag (roup dialog .o7 and then select -how -1*.ols fro* the Aindow *enu. Once this co**and is selected; 1ou can delete or re%assign the tag group assign*ent. 5ou entered a field t1pe for the upload or download interlocC that the Recipe Builder does not allow. Use onl1 BE fields for interlocC tagna*es. The Recipe Builder is una.le to cop1 or cut an1 data to the s1ste* clip.oard. Tr1 cop1ing a single row to the clip.oard and pasting it .acC into the recipe. 5ou are changing an o2erride li*it while an o2erride 2alue is in effect for the current recipe ite* or 2aria.le. -elect the 5es .utton to clear the o2erride 2alue and change the o2erride li*it or select the 6o .utton to a.ort the operation. 5ou ha2e a set of for*ulas that reference each other. Modif1 one of these for*ulas so that is contains a nu*eric or string constant or references a different 2aria.le. The Recipe Builder was una.le to replace an1 data in the selected colu*n .ecause it is not *odifia.le. -elect a different colu*n or *odif1 the displa1 for*at and *aCe the selected colu*n *odifia.le. 5ou selected the 7it co**and .efore sa2ing an1 changes to the recipe. To sa2e 1our changes and =uit the Recipe Builder; select the 5es .utton. To =uit without sa2ing an1 changes; select the 6o .utton. To return to the Recipe Builder without =uitting; select the !ancel .utton. The Recipe Builder was una.le to start the te7t editor it uses to create and *odif1 recipe note files. !lose one or *ore applications and tr1 again. Df the pro.le* persists; restart the co*puter. 5ou atte*pted to enter data into the !alc 4al colu*n. This colu*n displa1s the 2alue of a recipe ite*@s or 2aria.le@s for*ula and cannot .e *odified directl1.

!annot set the interlock "Onl1 BE fields are allowed'

!annot write to clip.oard.

!hanging the for*ula or o2erride li*it will clear the o2erride 2alue. !ontinue3

!ircular reference detected.

!olu*n is not *odifia.le.

Do 1ou want to sa2e this recipe3

ditor spawn failed

rror number checCing this ite*: Bield cannot .e *odified

rror number checCing this 5ou entered a field t1pe that the Recipe Builder does not allow. ite*: Onl1 BE and AE fields are Use onl1 AE and BE fields for tagna*es 1ou add to the recipe.

Message allowed rror number checCing this ite*: Recipe is in TA(6AM MOD

Meaning and Action

5ou atte*pted to add or delete a recipe ite* or 2aria.le while the Recipe Builder is su.stituting tagna*es for s1*.ol na*es. -elect -how -1*.ols fro* the Aindow *enu and then add or delete the recipe ite*s and 2aria.les 1ou want. The Recipe Builder atte*pted to load a displa1 for*at file that contains the wrong 2ersion nu*.er or has .een corrupted. Recreate the file .1 custo*i>ing the displa1 for*at and sa2ing it to a file. 5ou entered a 2alue in the 4erif1 colu*n that the Recipe Builder does not recogni>e. T1pe O6 or OBB in an1 cell of this colu*n. 5ou atte*pted to add *ore than 8)$ recipe ite*s. Onl1 8)$ recipe ite*s can .e added to one recipe. The *essage also appears when 1ou search a recipe with 8)$ ite*s .ecause the Recipe Builder creates a te*porar1 entr1 in the spreadsheet during the search. -ince all rows are filled; the search generates the error. To a2oid the *essage; re*o2e one of the recipe ite*s. 5ou atte*pted to create a 2aria.le with a na*e that is reser2ed for a Ce1word. nter a different na*e and tr1 again. Bor a list of reser2ed Ce1words; refer to the Recipe Fe1words ta.le. 5ou atte*pted to create a 2aria.le or a recipe ite* with a na*e that is alread1 in use. nter a different na*e and tr1 creating the ite* again. 5ou entered a for*ula that does not confor* to the s1nta7 that the Recipe Builder recogni>es. Ret1pe the for*ula using the guidelines in the chapter AorCing with Bor*ulas. 5ou entered an o2erride li*it that does not confor* to the s1nta7 the Recipe Builder recogni>es. Refer to the section ntering O2erride +i*its and ret1pe the o2erride li*it. 5ou entered an o2erride 2alue that does not confor* to the s1nta7 the Recipe Builder recogni>es. MaCe sure an1 string 1ou enter is enclosed in =uotes and ret1pe the o2erride 2alue. +9!E: Bor*ulas; Ce1word; and 2aria.les cannot .e entered into the O2erride 4alue colu*n.

rror reading displa1 for*at file; checC 2ersion

rror number setting this ite*: Bad 2erif1 option "on or off' rror number setting this ite*: !annot add node.tag.field to recipe. ?as *a7i*u* nu*.er .een reached3

rror number setting this ite*: !annot use a Ce1word for a 2aria.le na*e rror number setting this ite*: Ddentifier is alread1 defined in the recipe rror number setting this ite*: D*properl1 for*ed for*ula

rror number setting this ite*: D*properl1 for*ed o2erride li*it rror number setting this ite*: D*properl1 for*ed o2erride 2alue

rror number setting this ite*: 6o calculated 2alue to .ase

5ou entered a relati2e percentage or a relati2e difference o2erride li*it for a recipe ite* or 2aria.le. ?owe2er; the Recipe Builder

Message o2erride li*it on

Meaning and Action cannot calculate the range of accepta.le 2alues for this colu*n .ecause the for*ula of the current recipe ite* or 2aria.le is e*pt1 or in2alid. !o*plete or correct the ite*@s for*ula and then enter an o2erride li*it. 5ou atte*pted to enter an o2erride 2alue when .oth o2erride li*its are set to R -TRD!T D. To change the 2alue of the recipe ite*; either change an o2erride li*it and then enter an o2erride 2alue or change the ite*@s for*ula. 5ou entered an o2erride 2alue that is greater than the o2erride high li*it allows. nter a lower o2erride 2alue to tr1 again.

rror number setting this ite*: O2erride 2alue cannot .e *odified

rror number setting this ite*: O2erride 2alue is a.o2e the o2erride high li*it rror number setting this ite*: O2erride 2alue is .elow the o2erride low li*it rror number setting this ite*: 4aria.le na*e *ust start with G and contain onl1 alphanu*eric and underscore characters rror number setting this ite*: 4aria.le na*e too long rror while reading tag group file

5ou entered an o2erride 2alue that is less than the o2erride low li*it allows. nter a higher o2erride 2alue to tr1 again.

5ou entered a *arC of punctuation for a 2aria.le na*e that the Recipe Builder does not recogni>e. Ret1pe the 2aria.le na*e starting it with a nu*.er sign "G' followed .1 no *ore than 14 alphanu*eric or underscore "E' characters. 5ou entered a 2aria.le na*e that is o2er 1) characters; including the nu*.er sign "G'. -horten and ret1pe the 2aria.le na*e. The tag group file assigned to the recipe is unreada.le. -elect a different tag group or recreate the tag group 1ou want to use. To create a tag group; refer to the chapter Using the Tag (roup ditor. 5ou ha2e a set of for*ulas that reference 2aria.les chained o2er 14 rows. Modif1 the for*ulas so that the1 reference few 2aria.les. 5ou selected a control recipe fro* the Open !ontrol Recipe dialog .o7 that does not e7ist or could not .e found. ither cop1 the control recipe into the !ontrol Recipe path or select a recipe fro* the list .o7. 5ou entered a negati2e nu*.er or nonnu*eric data in the (o To dialog .o7. Ret1pe the row nu*.er 1ou want to Hu*p to and tr1 again. The Ce1word in the for*ula does not ha2e a 2alue. Refer to the section Understanding Recipe Fe1words to learn how to set the 2alue of each Ce1word. ither 1ou entered a string constant into the for*ula or o2erride 2alue colu*n when the associated tagna*e references an BE field

7pression is too deepl1 nested Dn2alid entr1. ,lease enter the na*e of an ite* in the list .o7.

Dn2alid ite* nu*.er

Fe1word is not defined in recipe

Mis*atched datat1pe

Message

Meaning and Action or 1ou atte*pted to set an a.solute; percentage; or difference o2erride li*it for a string constant. To correct this; enter a for*ula or o2erride 2alue that e2aluates to a nu*eric 2alue and then enter the o2erride li*it.

6o colu*n selected

5ou selected a .utton on the -earch and Replace dialog .o7 without first selecting a colu*n. -elect the colu*n 1ou want to search and then clicC a .utton on the dialog .o7 to search for or replace data in the recipe. 5ou ha2e a for*ula that references a 2aria.le with no 2alue. Modif1 the for*ula of the appropriate 2aria.le so that the Recipe Builder can calculate it. 5ou selected the (o To Dte* .utton fro* an error list dialog .o7 without first selecting an ite* in the list .o7. -elect an error in the dialog .o7 and then clicC the (o To Dte* .utton.

6o for*ula to e2aluate

6o ite* selected in error list

6o tag group assign*ent or tag 5ou selected the -how Tagna*es co**and .efore creating or group file does not e7ist assigning a tag group to the recipe. To create the tag group; refer to the chapter Using the Tag (roup ditor. To assign the tag group; select Assign Tag (roup fro* the Options *enu and enter the na*e of the tag group in the dialog .o7 that appears. 6o 2alue entered for o2erride li*it 5ou selected an a.solute; a percentage; or a difference o2erride li*it fro* the O2erride dialog .o7 without entering a 2alue for the t1pe of li*it 1ou selected. !o*plete the field associated with the t1pe of li*it 1ou selected and tr1 again. The Recipe Builder could not locate the note file for the current recipe. -elect the 5es .utton to create the file and start 6otepad. -elect the 6o .utton to return to the recipe. 5ou entered standard .atch si>e that: Ds greater than &;&&&;&&&.$; Ds less than $.$$$$$$1; !ontains a negati2e nu*.er; or !ontains nonnu*eric data.

6ote file IfilenameJ not found. !reate it3

Out of range

Ret1pe the standard .atch si>e 1ou want and tr1 again. ,aste error for Ktagname@: text Feep this ite*; discard it or undo the paste3 5ou are pasting a recipe ite* or 2aria.le into the recipe that *a1 alread1 e7ist; does not ha2e a 2alid for*ula; or contains te7t in the 4erif1 colu*n other than 5 - or 6O. -elect the Feep Dte* .utton to retain the 2alid parts of the recipe ite* .eing pasted or select the Discard Dte* .utton to pre2ent the entire recipe ite* fro* .eing pasted into the recipe. To cancel the entire operation; select the Undo ,aste .utton.

Message ,rechecC did not co*plete "reason'

Meaning and Action The Recipe Builder could not co*plete its e7a*ination for errors during an upload or download. Restart 1our co*puter and tr1 again. The Recipe Builder@s startup file; R!,.D6D; contains a 2erification ti*e%out 2alue that: Ds greater than /))3); Ds less than 1; !ontains a negati2e nu*.er; or !ontains non%nu*eric data.

R!,.D6D contains a .ad 2erification ti*e%out 2alueL using default

Because the ti*e%out 2alue is in2alid; the Recipe Builder uses its default 2alue of 3$ seconds. To change the ti*e%out 2alue; edit R!,.D6D using the instructions in the section !hanging the 4erification Ti*e%out Dnter2al. Recalculation failed at Dte* Grow_number. rror number: text The Recipe Builder cannot calculate the 2alue of the for*ula in row row_number. 7a*ine this for*ula and *aCe sure it confor*s to for*ula s1nta7. Bor *ore infor*ation a.out for*ulas; refer to the chapter AorCing with Bor*ulas. 5ou atte*pted to upload or download while the spreadsheet was e*pt1. ither open a recipe or enter the tagna*es 1ou want to upload fro* or download to. The Recipe Builder is a.out to replace the specified search string with the specified replace*ent string. -elect the 5es .utton to replace each occurrence of the search string in the selected cell. -elect the All .utton to replace each occurrence of the search string in the selected colu*n. -elect the 6o .utton to stop replacing data. 5ou entered a row nu*.er in the (o To dialog .o7 that was greater than the last row in the spreadsheet. Ret1pe the row nu*.er 1ou want to Hu*p to and tr1 again. The Recipe Builder is a.out to replace the specified search string with the specified replace*ent string. ?owe2er; it located *ultiple occurrences of the search string. -elect the 5es .utton to replace each occurrence of the search string in the selected cell. -elect the All .utton to replace each occurrence of the search string in the selected colu*n. -elect the 6o .utton to stop replacing data. The Recipe Builder cannot locate the specified tag group file. ither the tag group does not e7ist or does not reside in the ,icture path. Tr1 cop1ing the file to this path or create it with the Tag (roup ditor.

Recipe has no ite*s

Replace te7t3

Row is .e1ond end of recipe

-earch string was found x ti*es. Replace each one3

Tag group file does not e7ist

Message Tagna*e does not e7ist. !ontinue3

Meaning and Action The Recipe Builder cannot locate the tagna*e 1ou want to add to the recipe in the specified data.ase. -elect the 6o .utton to a.ort the operation or select the 5es .utton to add the tagna*e. Df 1ou add the tagna*e; *aCe sure 1ou add the .locC to the data.ase or 1ou will .e una.le to download or upload the recipe. The Recipe Builder could not find the specified search string in the selected colu*n. 5ou entered a report colu*n width that: Ds greater than 1$$; Ds less than 1; !ontains a negati2e nu*.er; or !ontains nonnu*eric data.

Te7t not found

The colu*n width *ust .e .etween 1 and 1$$.

Ret1pe the colu*n width 1ou want and tr1 again. The editor is alread1 running 5ou selected the 6otes co**and while the te7t editor used to create and *odif1 recipe note files was alread1 in use. -elect the OF .utton on the *essage .o7L the Recipe Builder auto*aticall1 switches 1ou .acC to the te7t editor. Modif1 1our recipe note files as needed. To =uit the te7t editor and return to the Recipe Builder; select the 7it co**and fro* the Bile *enu. 5ou are atte*pting to scale the .atch si>e while one or *ore o2erride 2alues are in use. -elect the !ontinue .utton to proceed or select the !ancel .utton to a.ort the operation. To clear all o2errides and scale the .atch si>e; select the !lear All .utton. 5ou are deleting the current recipe identifier. This results in the deletion of the entire recipe ite* or 2aria.le. -elect the 5es .utton to delete the recipe ite* or 2aria.le. -elect the 6o .utton to a.ort the operation. 5ou atte*pted to enter data into a colu*n that is non%*odifia.le. To *aCe the colu*n *odifia.le; refer to the section Modif1ing a !olu*n. After *aCing the colu*n *odifia.le; tr1 entering data into the colu*n again. 5ou atte*pted to start the Recipe Builder without the securit1 rights to the Recipe De2elop*ent or the Recipe Operations windows. !onsult 1our s1ste* ad*inistrator .efore proceeding. The Recipe Builder is using the default displa1 for*at .ecause it could not find the file D BAU+T.RBT. To load this file on startup; *aCe sure the file resides in the +ocal path and restart the Recipe Builder.

There are recipe ite*s with O4 RRDD 4A+U -.

This change will destro1 this recipe ite*. !ontinue3

This colu*n can@t .e *odified. !hecC the displa1 for*at.

Unauthori>ed access atte*pted

Using internal displa1 for*at

Message

Meaning and Action

4aria.le is not defined in recipe 5ou entered a 2aria.le na*e in the for*ula colu*n that is not in the Ddentifier colu*n. !reate the 2aria.le .1 entering its na*e in a .lanC cell of the Ddentifier colu*n. 5ou can onl1 switch to the Operations window with a !O6TRO+ recipe 5ou atte*pted to displa1 the Recipe Operations window with an untitled recipe; a *aster recipe; a *aster te7t recipe; or a .acCup recipe open in the spreadsheet. ither open a control recipe or sa2e the current recipe as a control recipe .efore switching to the Recipe Operations window. 5ou specified a co**and line para*eter to open a *aster recipe or a *aster te7t recipe when the Recipe Builder starts. ?owe2er; the Recipe Builder is set up to auto*aticall1 displa1 the Recipe Operations window. To displa1 the specified recipe; select the OF .utton to open the Recipe Operations window and switch to the Recipe De2elop*ent window and open the recipe. To set up the Recipe Builder to auto*aticall1 displa1 the Recipe De2elop*ent window; switch to the De2elop*ent window and select the -tart in D 4 Aindow fro* the Aindow *enu. The Recipe Builder atte*pted to displa1 the Recipe De2elop*ent window. ?owe2er; 1our user account does not contain the necessar1 pri2ileges to displa1 this window. !onsult 1our s1ste* ad*inistrator .efore proceeding. 5ou atte*pted to download a recipe without the necessar1 securit1 rights to do so. !onsult 1our s1ste* ad*inistrator .efore proceeding. The Recipe Builder atte*pted to displa1 the Recipe Operations window. ?owe2er; 1our user account does not contain the necessar1 pri2ileges to displa1 this window. !onsult 1our s1ste* ad*inistrator .efore proceeding. 5ou atte*pted to sa2e a recipe without the necessar1 securit1 rights to do so. !onsult 1our s1ste* ad*inistrator .efore proceeding.

5ou can open onl1 !ontrol Recipes in the Operations window

5ou do not ha2e -ecurit1 ,ri2ileges to run R !D, D 4 +O,M 6T feature

5ou do not ha2e -ecurit1 ,ri2ileges to run R !D, DOA6+OAD feature 5ou do not ha2e -ecurit1 ,ri2ileges to run R !D, O, RATDO6- feature

5ou do not ha2e -ecurit1 ,ri2ileges to run R !D, -A4 feature

5ou do not ha2e -ecurit1 5ou atte*pted to create a report or sa2e a *aster te7t or control ,ri2ileges to run R !D, T MT te7t recipe without the necessar1 securit1 rights to do so. !onsult OUT,UT feature 1our s1ste* ad*inistrator .efore proceeding. 5ou do not ha2e -ecurit1 ,ri2ileges to run R !D, U,+OAD feature 5ou do not ha2e -ecurit1 ,ri2ileges to run this R !D, feature 5ou atte*pted to upload a recipe without the necessar1 securit1 rights to do so. !onsult 1our s1ste* ad*inistrator .efore proceeding. The Recipe Builder cannot co*plete the operation 1ou selected .ecause 1ou do not ha2e the necessar1 application feature in 1our user account. !onsult 1our s1ste* ad*inistrator .efore proceeding.

Message 5ou *ust ha2e at least one colu*n displa1ed

Meaning and Action 5ou atte*pted to re*o2e all the colu*ns fro* the displa1 for*at or fro* a report. The Recipe Builder re=uires at least one colu*n for displa1 for*ats and reports. 5ou are creating a report for an untitled recipe. To sa2e the report with the na*e U6TDT+ D; select the 5es .utton. To a.ort the process select the 6o or !ancel .uttons. +9!E: Df 1ou su.se=uentl1 na*e the recipe; the Recipe Builder will not .e a.le to locate the report 1ou created. To ena.le the Recipe Builder to locate the report; create a new report or rena*e the e7isting one so that the recipe na*e and the report na*e *atch.

5our untitled recipe report will .e sa2ed to Nuntitled.rcrN. !ontinue3

Uploading and Downloading Messages


Message Bad 2alue Action 5ou are downloading a 2alue to a field that cannot .e written to or the 2alue .eing written is in2alid. MaCe sure the field can .e written to and that the field e7ists. 5ou are downloading a 2alue to a field that cannot .e written to. Tr1 downloading to a different field. 5ou are downloading to a data.ase .locC that is in Auto*atic *ode. ,ut the .locC in Manual *ode and download the recipe again.

!annot write to this field !urrent .locC *ode does not allow writes Bield na*e returns wrong data t1pe Bield@s 2alue not Cnown

5ou are uploading or downloading a recipe with one or *ore s1*.ols defined and no tag group assign*ent. Assign the appropriate tag group and tr1 uploading or downloading the recipe again. The Recipe Builder cannot upload the recipe or 2erif1 the specified recipe ite* .ecause it cannot read a 2alue fro* the specified .locC. MaCe sure -A! and 1our DOO dri2er are running. Also *aCe sure the .locC is on scan. The data t1pe of the for*ula does not *atch the specified field. Bor e7a*ple; 1ou *a1 ha2e specified a string constant for a BE field. ither change the for*ula or the field 1ou are downloading to. ither the specified tagna*e cannot .e written to or it *a1 not e7ist. 4erif1 that the tagna*e e7ists and can .e written to. One or *ore recipe ite*s ha2e:

Dllegal option; ,lease re%enter

Tagna*e is not defined Undefined recipe ite*

Message

Action

A calculated or o2erride 2alue .ut no identifier; or An identifier .ut no for*ula or o2erride 2alue

!o*plete the identifier colu*n and either for*ula or the o2erride 2alue colu*n for the specified recipe ite*s. 4alue is not accessi.le fro* this plant area 5ou are downloading to a field that cannot .e written to or the necessar1 securit1 area rights are not assigned to the Recipe user account on the target -!ADA ser2er. !onsult with 1our s1ste* ad*inistrator and add the securit1 areas of the .locC 1ou are downloading to the Recipe user account. 5ou are downloading a 2alue that is greater than the .locC accepts. !hange the for*ula or o2erride 2alue of the specified recipe ite* and tr1 downloading the recipe again.

4alue out of range

Audit Trail for Recipe Builder


Message .ad co*pletion status flag Action The analog .locC defined as the co*pletion status indicator is undefined or cannot .e read fro* or written to. MaCe sure the .locC e7ists in the data.ase and that the .locC is in a *ode that allows it to .e read fro* and written to "for e7a*ple; Analog Dnput .locCs should .e in Manual *ode'. One of the following co**and line para*eters was not specified: !ontrol Recipe para*eter Master Recipe para*eter Master Te7t Recipe para*eter !ontrol Te7t Recipe para*eter

.ad error file na*e

Dnclude the appropriate co**and line para*eter and tr1 again. .ad or acti2e interlocC The upload or download interlocC specified for the recipe is acti2e or does not e7ist. MaCe sure the interlocC is inacti2e .efore 1ou tr1 again. Df the specified tagna*e does not e7ist; create the necessar1 .locC in the data.ase or specif1 a different tagna*e. The Recipe Builder does not recogni>e the co**and line para*eter specified in a script or a ,rogra* .locC. Refer to the chapter !o**and +ine ,ara*eters for a list of recogni>ed co**and line para*eters and *odif1 the script or ,rogra* .locC as needed.

.ad o2erride para*eter

.ad o2erride para*eter 2aria.le na*e cannot change .atch si>e in control recipe

The 2aria.le na*e specified in the co**and line does not e7ist in the recipe. Re%t1pe the co**and line and tr1 again. The Batch -i>e para*eter was specified in the co**and line while downloading a control or control te7t recipe. This co**and line para*eter can onl1 .e used with *aster and *aster te7t recipes. ither download a *aster recipe or o*it the Batch -i>e para*eter fro* the co**and line and tr1 again. The Tag (roup para*eter was specified in the co**and line while uploading or downloading a control or control te7t recipe. This co**and line para*eter can onl1 .e used with *aster and *aster te7t recipes. ither upload or download a *aster recipe or o*it the Tag (roup para*eter fro* the co**and line and tr1 again. The para*eter file specified in the co**and line does not e7ist or could .e opened. B1 default; the Recipe ,acCage assu*es the file resides in the +ocal path. ither create a para*eter file and sa2e it in the +ocal path or cop1 the para*eter file to this path. The Recipe Builder cannot open the specified recipe. MaCe sure 1ou specified the na*e of the recipe in the co**and line and tr1 again. Also *aCe sure the recipe e7ists in the correct recipe path. Df it does not; create it. The Recipe Builder cannot read the specified recipe. Tr1 specif1ing the .acCup 2ersion of the recipe. The Recipe Download or Recipe Upload s1ste* tasC cannot recalculate the for*ula of each recipe ite*. MaCe sure the s1nta7 of each for*ula is 2alid. Refer to the chapter AorCing with Bor*ulas for infor*ation on for*ulas. The Recipe ,acCage atte*pted to set the Batch DD. ?owe2er; it encountered a *e*or1 or internal error. 7it fro* an1 applications not in use and restart the Recipe Builder. The Batch DD para*eter was specified to the Recipe Upload s1ste* tasC. This tasC does not recogni>e this co**and line para*eter. O*it the para*eter and tr1 again. The Recipe Download s1ste* tasC cannot set the current recipe@s .atch si>e .ecause the .atch si>e: Ds greater than &;&&&;&&&.$; Ds less than $.$$$$$$1; !ontains a negati2e nu*.er; or !ontains non%nu*eric data.

cannot change tag group in control recipe

cannot open para*eter file

cannot open recipe file

cannot read recipe file

cannot recalculate recipe

cannot set .atch DD

cannot set .atch DD on upload

cannot set .atch si>e

Ret1pe the .atch si>e 1ou want and tr1 again. cannot set .atch si>e on upload The Batch -i>e para*eter was specified to the Recipe Upload s1ste* tasC. This tasC does not recogni>e this co**and line para*eter. O*it the para*eter and tr1 again. The Recipe Download s1ste* tasC cannot scale the recipe with o2erride 2alues in effect. !licC the !lear O2errides .utton to re*o2e all o2errides and tr1 downloading the recipe again. The Recipe Download s1ste* tasC cannot set one or *ore o2erride para*eters. The 2alues specified are out of range; do not confor* to a s1nta7 that the Recipe Download tasC recogni>es; or are the wrong data t1pe "for e7a*ple; entering string data for a BE field'. 4erif1 all the 2alues specified and tr1 to download the recipe again. One or *ore o2erride para*eters were specified to the Recipe Upload s1ste* tasC. This tasC does not recogni>e these co**and line para*eters. O*it the para*eters and tr1 again. The Recipe ,acCage atte*pted to set the download re*arCs for the specified recipe. ?owe2er; it encountered a *e*or1 or internal error. 7it fro* an1 application not in use and restart the Recipe Builder. The Download Re*arCs para*eter was specified to the Recipe Upload s1ste* tasC. This tasC does not recogni>e this co**and line para*eter. O*it the para*eter and tr1 again. The Recipe Download s1ste* tasC cannot locate the tag group assigned to the recipe or specified .1 the Tag (roup para*eter. MaCe sure the tag group e7ists in the director1 defined .1 the ,icture path. The Master Te7t Recipe or !ontrol Te7t Recipe para*eter was specified to the Recipe Upload s1ste* tasC. Master and !ontrol Te7t recipes cannot .e uploaded using this tasC. Upload the recipe fro* the Recipe Builder instead. The !o**and +ine Bile para*eter was included in the co**and line with other co**and line para*eters. Delete the !o**and +ine Bile para*eter or re*o2e the other co**and file para*eters fro* the co**and line. The specified recipe was uploaded .ut cannot .e sa2ed. MaCe sure there is enough space on the disC to sa2e the recipe and tr1 again. The Batch DD para*eter was specified without an identifier.

cannot set .atch si>e with o2errides

cannot set o2erride 2alue

cannot set o2errides on upload

cannot set re*arCs

cannot set re*arCs on upload

cannot set tag group

cannot upload to a te7t file

cannot use para*eter file with other para*eters

cannot write recipe file

*issing .atch DD

Dnclude a .atch DD and tr1 again. *issing .atch si>e The Batch -i>e para*eter was specified without including a .atch si>e. Dnclude the .atch si>e and tr1 again. The !o**and +ine Bile para*eter was specified without an acco*pan1ing file na*e. Dnclude the na*e of the para*eter file and tr1 again. One of the following co**and line para*eters was specified without an acco*pan1ing recipe na*e: !ontrol Recipe para*eter Master Recipe para*eter Master Te7t Recipe para*eter !ontrol Te7t Recipe para*eter

*issing para*eter file na*e

*issing recipe file na*e

Dnclude the na*e of the recipe 1ou want to upload or download and tr1 again. *issing re*arCs The Download Re*arCs para*eter was specified without an1 acco*pan1ing te7t. Dnclude the appropriate te7t and tr1 again. The Tag (roup para*eter was specified without a tag group file. Dnclude the na*e of the tag group file to use and tr1 again. The Recipe user account does not e7ist on the node 1ou are downloading fro*. !onsult 1our s1ste* ad*inistrator .efore proceeding.

*issing tag group file na*e

6o R !D, user found. Run the -ecurit1 !onfiguration progra* and add a user called KR !D, @ to this node and all referenced -!ADA nodes not a recipe file t1pe

The file specified is not a recipe. Re%enter the na*e of the recipe to upload or download and tr1 again. Df 1ou are using the Recipe Upload s1ste* tasC; *aCe sure it is a *aster or control recipe. The Upload tasC cannot upload *aster te7t or control te7t recipes.

recipe path not found

The Recipe ,acCage cannot locate the recipe path specified in the -!U. MaCe sure the *aster and control recipe paths e7ist or change the recipe paths to point to the directories where 1our *aster and control recipes reside. The for*ula for one or *ore recipe ite*s cannot .e e2aluated or the identifier has not .een entered. !o*plete the identifier and for*ula of each ite* and tr1 uploading or downloading the recipe again. The Recipe ,acCage does not recogni>e the co**and line para*eter specified in a script or a ,rogra* .locC. Refer to the

undefined recipe ite*

unCnown para*eter

chapter !o**and +ine ,ara*eters for a list of recogni>ed co**and line para*eters and *odif1 the script or ,rogra* .locC as needed.

Other Recipe
Df the Recipe Builder cannot recalculate a for*ula "for e7a*ple; when one or *ore 2aria.les referenced .1 the for*ula are undefined' an error *essage .o7 appears displa1ing the following te7t: Recalculation failed at ite* Gx. rror xxxx error_text The Recipe Builder also stops recalculating all for*ulas that co*e after the incalcula.le for*ula. 5ou cannot change a recipe ite* with a field t1pe of AE and a string for*ula to an BE field. Df 1ou atte*pt to do this; the following error *essage appears: !hecCing this ite*. Onl1 BE and AE fields are allowed.

Auto Alarm Manager


Message User 0ueue not found % Run AU- R01. M or AU- R0#. M . "olution The appropriate user =ueue could not .e found. 5ou do not ha2e AU- R01. M or AU- R0#. M running. nsure that 1ou ha2e the appropriate AU- R0 configured with the P01 or P0# co**and option. To do so; re2iew the co**and line options in the IAUTO A+ARM T!,D,J section of the BDM.ini. Bor descriptions of co**and line options and how to update the BDM.ini; refer to !o**and +ine Options for AAMT!,.e7e section. 5ou *ust ena.le BDM networCing to use Auto Alar* Manager for T!,OD,. The T!,OD, networCing feature *ust .e ena.led in the iBDM or BDM -!U. Bor instructions on how to ena.le T!,OD, networCing in iBDM; refer to the na.ling T!,OD, 6etworCing for the Auto Alar* Manager section. !an@t read Re*ote BDM configuration An error occurred when reading the Auto Alar* Manager fro* -!U. ?a2e 1ou configured configuration infor*ation. AAM in the -!U3 Dn the -!U; on the -ender and Recei2er node; checC the Auto Alar* Manager !onfiguration dialog .o7. nsure that all settings are configured properl1.

Message

"olution

Bor steps on how to configure the Auto Alar* Manager in the -!U; refer to the !onfiguring the Auto Alar* Manager in iBDM section. Auto Alar* Manager is not ena.led in the -!U. The AAMT!,.e7e shuts down if it is not configured in -!U to recei2e or send alar*s. Dn the -!U; on the -ender and Recei2er node; open the Auto Alar* Manager !onfiguration dialog .o7. nsure that the -end Alar*s or Recei2e Alar*s option is ena.led; along with the appropriate options. Bor steps on how to configure the Auto Alar* Manager in the -!U; refer to the !onfiguring the Auto Alar* Manager in iBDM section. rror in AcCnowledging alar*. 6o AA+ARM user found. iBDM or BDM securit1 is ena.led; .ut 1ou do not ha2e the necessar1 securit1 rights defined for the Auto Alar* Manager on 1our -ending nodes. Aithout these rights; iBDM cannot accept the Auto Alar* Manager@s acCnowledg*ents. 4erif1 that the AA+ARM account e7ists; and that it is ena.led for all securit1 rights. Bor *ore infor*ation; refer to the Before 5ou Begin: !onfigure -ecurit1 Rights. rror initiali>ing 6T securit1 attri.utes. A Aindows operating s1ste* error occurred. !hecC Aindows or 1our user access rights. Bor *ore infor*ation; refer to Aindows help. Bailed. The Auto Alar* Manager failed to initiali>e correctl1 .ecause this is a ,lantT4 node; and that t1pe of node not supported. !onfir* that iBDM started correctl1; and that networCing is ena.led and running. Bor instructions on how to ena.le T!,OD, networCing in iBDM; refer to the na.ling T!,OD, 6etworCing for the Auto Alar* Manager section. os7Egl.lEalloc"' of Manage*ent Buffer failed. Me*or1 could not .e allocated to run the Auto Alar* Manager. !hecC the following:

Bailed to post an nErecei2e"'.

Message

"olution

!onfir* that BDM or iBDM started properl1 and is running. nsure that 1ou ha2e enough free *e*or1 a2aila.le on 1our s1ste*.

-1ste* rror: !:Q,rogra* BilesQ( BanucQ,rofic1 iBDMQT!,TasC.e7e (etAllAin#FipAddrs"' P (etAdaptersDnfo-i>ing Bailed with rror

This is a non%fatal error. Dt occurs if 1ou ena.led T!,OD, networCing in iBDM and 1our co*puter does not ha2e an thernet card. Two of these error *essages appear when 1ou start iBDM. 5ou can safel1 acCnowledge .oth *essages. iBDM and the Auto Alar* Manager should still start properl1. Df not; checC 1our networC adapter. Dt@s possi.le that it does not ha2e the T!,D, protocol ena.led.

!o**on issues 1ou *a1 encounter when using Auto Alar* Manager; and their possi.le solution"s' are su**ari>ed .elow: Message 6o thernet !ard Bound "olution Df 1ou ena.led T!,OD, networCing in iBDM; and 1our co*puter does not ha2e an thernet card; two error *essages appear when 1ou start iBDM. 5ou can safel1 acCnowledge .oth *essages. iBDM and the Auto Alar* Manager should still start properl1. Df not; checC 1our networC adapter. Dt@s possi.le that it does not ha2e the T!,OD, protocol ena.led. Df 1ou start the -!U and recei2e the following *essage: !an@t find RA-A,D3#.D++; tr1 installing the Aindows Re*ote Access -er2ice software on 1our co*puter. Df the *ode* on the Recei2ing node does not hang up when the *ode* on the -ending node does; 1ou *a1 need to ena.le ?ardware Blow !ontrol and Mode* rror !ontrol in 1our RA- software. To ena.le ?ardware Blow !ontrol and Mode* rror !ontrol: 1. Bro* the Dnstall 6etworC -oftware list .o7; select Re*ote Access -er2ice. #. !licC !onfigure. 3. -elect the port 1our *ode* uses fro* the dialog .o7 and clicC !onfigure. 4. !licC -ettings. ). !licC the na.le ?ardware Blow !ontrol and na.le rror !ontrol checC .o7es. /. !lose all the open dialog .o7es; the 6etworC !ontrol ,anel; and

RA-A,D3#.D++ 6ot Bound

Mode* Does 6ot ?ang Up

Message

"olution

restart 1our co*puter to ensure that the changes taCe effect. Una.le to Add RA-er2er to -!U TasC +ist Df 1ou tr1 to add the RA- ser2er to the -!U tasC list so that it starts auto*aticall1 with iBDM; 1ou will not .e a.le to do so. The RA- ser2er cannot .e added to the -!U tasC list. Dnstead; configure the RA- ser2er to start auto*aticall1 through the Aindows -er2ices dialog .o7. To start the RA- ser2er auto*aticall1 using the Aindows -er2ices dialog .o7: 1. -elect Re*ote Access -er2er fro* the -er2ices dialog .o7 and clicC -tartup. The -er2ice dialog .o7 appears. #. !licC Auto*atic and close all the open dialog .o7es and the -er2ice !ontrol ,anel to sa2e 1our changes. 3. Restart 1our co*puter to start the RA- ser2er auto*aticall1. Bailure to !onnect Df the Auto Alar* Manager fails to connect; 1ou *a1 need to specif1 the na*e of a Aindows user account that has dial%in per*ission in the Ad2anced -end Alar* -ettings dialog .o7. Refer to the !onfiguring the Auto Alar* Manager to Run ,roperl1 as a -er2ice section for instructions.

!erminal "er#er
Message The Ter*inal -er2ices +icensing grace period has e7pired and the ser2ice is not registered with a license ser2er. A ter*inal ser2ices license ser2er is re=uired for continuous operation. A ter*inal ser2er can operate without a license ser2er for &$ da1s after initial startup. 6ode 6a*e Alread1 in Use "olution Df this *essage appears; Ter*inal -er2ices +icensing needs to .e installed fro* the !ontrol ,anel@s Add or Re*o2e ,rogra*s window; and then acti2ated. Dt is not enough to ha2e Hust Ter*inal -er2ices +icensing installedL it *ust .e acti2ated. Once acti2ated; use the Ter*inal -er2ices +icensing co*ponent; the +icensing Ai>ard; to install an1 needed T-!A+ toCens. Bor *ore infor*ation on Ter*inal -er2er licensing; refer to the +icensing Re=uire*ents section. This *essage can appear when 1ou atte*pt to start a new iBDM session and a session with that node na*e alread1 e7ists; or if 1ou do not ha2e correct per*issions set on the Ter*inal -er2er *achine. iBDM does not start in this instance. Df no other session is using the node na*e; the issue is *ost liCel1 due to a securit1 rights issue on the Ter*inal -er2er *achine "a non%ad*inistrator user is starting iBDM'. To resol2e the securit1 rights issue:

Message

"olution

1. +og onto the Ter*inal -er2er *achine as a user with Ad*inistrati2e rights. #. On the -tart .utton; point to Run. The Run dialog .o7 appears. 3. T1pe regedt3# and press nter. The Registr1 ditor appears. 4. -elect the ?F 5E!+A-- -EROOT folder. ). Aith the ?F 5E!+A-- -EROOT folder selected; on the dit *enu; clicC ,er*issions. The ,er*issions for ?F 5E!+A-- -EROOT dialog .o7 appears. /. Df the users or group that runs iBDM does not appear in the 6a*e list; add the* .1: !licCing Add. -electing the user na*e or group na*e fro* the do*ain and clicCing Add; and then OF.

R. !licC the Ad2anced .utton. 8. -elect the iBDM user or group fro* the list and clicC dit. The ,er*ission ntr1 dialog .o7 appears. &. Dn the ,er*ission list; for the -et 4alue; put a checC *arC in the Allow colu*n. Df a checC *arC alread1 e7ists; dou.le%checC that the correct users or group has .een selected in the 6a*e .o7. 1$. !licC OF for each dialog .o7 and close the registr1 editor.

"ecurit% "%nchroni&er
rrors are categori>ed into three le2els of se2erit1; listed here fro* highest to lowest: Application Errors P -ecurit1 -1nchroni>er ter*inates without perfor*ing or co*pleting s1nchroni>ation. rror codes range fro* #$$%#&&. ;ser Account Errors P rrors are encountered for indi2idual user accounts; .ut the s1nchroni>ation process co*pletes. rror codes range fro* 1$$%1&&. <eneral Errors P rrors such as the ina.ilit1 to write to iBDM data.ase tags are detected; .ut the s1nchroni>ation process co*pletes. rror codes range fro* 1%&&. 5ou *a1 encounter a fourth t1pe of error caused when an in2alid co**and line para*eter is passed to the -ecurit1 -1nchroni>er. This t1pe of error does not cause 2alues to .e written to the iBDM data.ase; .ut it does cause *essages to .e written to the securit1 log file and the iBDM alar* destinations.

5ou can configure error conditions to .e reported in the Alar* -u**ar1 or other alar* destinations through the use of iBDM data.ase tags. Df the O para*eter is used to specif1 an analog error tag; 1ou can configure that tag to alar* on the error 2alue. Bor e7a*ple; 1ou can configure an Analog Dnput .locC that recei2es the error 2alue to generate a ?D alar* when the error 2alue e7ceeds && or a ?D?D alar* when the error 2alue e7ceeds 1&&.

Application Error Codes (200 2!!"


The following ta.le lists the application error codes. These errors cause the -ecurit1 -1nchroni>er process to ter*inate without perfor*ing or co*pleting s1nchroni>ation. These errors ha2e the highest se2erit1. Application rror !odes Error Code #$1 Error Message

-ecurit1 -1nchroni>er: Una.le to perfor* securit1 s1nchroni>ation. BDM s1ste* is not running -ecurit1 -1nchroni>er: User has insufficient BDM pri2ileges to run -ecurit1 -1nchroni>er. -ecurit1 -1nchroni>er: Atte*pt to e7ecute s1nchroni>ation while alread1 running. -econd atte*pt a.orted. -ecurit1 -1nchroni>er: Bunction is not ena.led on this nodeL checC licenseOCe1. -ecurit1 -1nchroni>er: -ecurit1 !onfigurator is running. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: Dnsufficient *e*or1 to co*plete s1nchroni>ation process. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: -ource of Aindows securit1 not specified "Do*ain; +ocal'. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: Una.le to retrie2e securit1 info fro* Aindows Do*ain. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: Una.le to retrie2e Aindows securit1 infor*ation fro* local ,!. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: 6o group na*es found in Aindows that *ap to BDM pri2ileges. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: 6o Aindows users .elong to groups which *ap to BDM pri2ileges. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: Una.le to retrie2e BDM securit1 data. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: Una.le to retrie2e BDM securit1 Area data. -1nchroni>ation

#$#

#$3

#$4 #$) #1$

##$

#3$

#4$

#)$

#)1

#R$ #R1

a.orted. #R# -ecurit1 -1nchroni>er: Una.le to retrie2e BDM Application Beature data. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: Una.le to retrie2e BDM -ecurit1 (roup data. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: -ecurit1 paths una2aila.le or securit1 has .een ta*pered with. -1nchroni>ation a.orted.

#R3

#8$

User Account Error Codes (#00 #!!"


The following ta.le lists the user account error codes. These errors are encountered for indi2idual user accounts; .ut the s1nchroni>ation process continues. These errors ha2e *ediu* se2erit1. The Ss character used in the following list of user account error *essage is replaced .1 the appropriate string for each instance of the *essage: User Account rror !odes Error Code 1$1 1$# 11$ 1#$ 13$ Error Message

-ecurit1 -1nchroni>er: !an@t create account for Ss. 6a*e alread1 e7ists. -ecurit1 -1nchroni>er: !an@t create account for Ss. Dn2alid characters in na*e. -ecurit1 -1nchroni>er: !an@t sa2e changes to user Ss. rror writing to file. -ecurit1 -1nchroni>er: !an@t add BDM group Ss to user Ss "91#'. -ecurit1 -1nchroni>er: !an@t delete BDM user Ss. +ast user with access to -ecurit1 !onfig. -ecurit1 -1nchroni>er: !an@t re*o2e securit1 configuration rights fro* user Ss. -ecurit1 -1nchroni>er: !an@t re*o2e user S. User no longer e7ists in BDM securit1. -ecurit1 -1nchroni>er: !an@t delete user Ss. rror occurred writing to disC. -ecurit1 -1nchroni>er: rror sorting BDM securit1 users. Use BDM -ecurit1 !onfiguration progra* to sa2e configuration. -ecurit1 -1nchroni>er: Una.le to restore securit1 data due to disC pro.le*s. -ecurit1 *a1 .e corrupted. -ecurit1 -1nchroni>er: Una.le to .acCup securit1 data due to disC pro.le*s. 6o BDM users were deleted.

131 14$ 141 1)$

1/$

1/1

1/#

-ecurit1 -1nchroni>er: Una.le to sa2e securit1 data due to disC pro.le*s. 6o BDM users were deleted.

$eneral Error Codes (# !!"


The following ta.le lists the (eneral rror codes. These errors ha2e the lowest se2erit1. (eneral rror !odes Error Code #$ #1 ## 3$ 31 3# Error Message -ecurit1 -1nchroni>er: !an@t write to Analog rror tag Ss in BDM data.ase. -ecurit1 -1nchroni>er: !an@t write to Digital rror tag Ss in BDM data.ase. -ecurit1 -1nchroni>er: !an@t write to !o*pletion tag Ss in BDM data.ase. -ecurit1 -1nchroni>er: -ecurit1 Area na*e Ss does not e7ist in BDM securit1. -ecurit1 -1nchroni>er: application feature na*e Ss does not e7ist in BDM securit1. -ecurit1 -1nchroni>er: -ecurit1 (roup na*e Ss does not e7ist in BDM securit1.

Co%%and &ine 'ara%eter Errors


4alues are not associated with co**and line para*eter errors since 2alues are not written to the iBDM data.ase when these errors occur. These errors ter*inate the s1nchroni>ation process .efore it actuall1 .egins. These errors are detected onl1 when the -ecurit1-1nchroni>er.e7e progra* is running; and not when progra**ing to the -ecurit1 -1nchroni>er Auto*ation interface. Refer to the iBDM Auto*ation Dnterfaces ?elp file for *ore infor*ation on the Auto*ation interface. 5ou *a1 encounter one of these co**and line errors while running -ecurit1 -1nchroni>er: -ecurit1 -1nchroni>er: Dn2alid Aindows Do*ain na*e. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: Dn2alid +ogin Ti*eout 2alue. 4alue *ust .e .etween $ and 8/3&& seconds. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: Dn2alid MapMode 2alue. -1nchroni>ation a.orted. BOR BUTUR U- . -ecurit1 -1nchroni>er: Dn2alid Analog rror Tag s1nta7 "O '. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: Dn2alid Bailure Tag s1nta7 "OB'. -1nchroni>ation a.orted. -ecurit1 -1nchroni>er: Dn2alid !o*pletion Tag s1nta7 "O!'. -1nchroni>ation a.orted.

'istorical Assign
'istorical Assign Message !an@t add group. DisC *a1 .e full. !hecC disC. Action or Meaning !hecC disC space and delete unnecessar1 files.

'istorical Assign Message !annot sa2e a group with no tags. !lose dialog an1wa13 !onfiguration file write error. DisC *a1 .e full. nter a nodena*e.

Action or Meaning A group that contains no tags cannot .e sa2ed.

!hecC disC space and delete unnecessar1 files.

To use 3 support in the tagna*e field 1ou *ust first enter a node na*e in the 6ode field. MaCe sure 1our tagna*e has a BE field. 6ode na*e *ust start with a letter and .e less than & alphanu*eric characters. nter a li*it 2alue greater than or e=ual to $. !hecC disC space and delete unnecessar1 files.

Bield *ust .e floating point t1pe. Dllegal characters in nodena*e.

Dllegal li*it 2alue. Dnsufficient disC space to sa2e new configuration. Dnsufficient disC space to sa2e new group. Dn2alid autopurge ti*e entered. Dn2alid rate 2alue.

!hecC disC space and delete unnecessar1 files.

4alid autopurge range is fro* #%#$$ da1s. 4alid collection rates are: 1; #; 1$; #$; 3$ seconds 1; #; 1$; #$; 3$ *inutes

Dn2alid 2alue entered for phase.

,hase 2alues are in # second incre*ents fro* $%)8 seconds. Up to #)) collection groups can .e defined in ?istorical Assign. The node na*e entered is not 2alid. sta.lish a session with the node in the -!U. The ,hase 2alue *ust .e less than the Rate 2alue. 4erif1 that the entr1 is 2alid.

Ma7i*u* nu*.er of groups has .een reached. 6odena*e is not 2alid. -a2e an1wa13 ,hase *ust .e less than rate. This 6ode:Tag.Bield not found. Use an1wa13 This tagna*e is alread1 assigned to the group.

The tagna*e is alread1 entered for this group. 5ou cannot enter duplicate tagna*es into a collection group.

'istorical Assign Message This =ualifier is not a digital point. Use an1wa13

Action or Meaning 4erif1 the =ualifier .locC that 1ou entered. The =ualifier is usuall1 a Digital Dnput or Digital Output .locC. Df 1ou are not using a Digital .locC; a 2alue of $ stops collection and a 2alue other than $ starts collection.

'istorical Collect
'istorical Collect Message An o2errun has occurred. Action or Meaning An o2errun indicates that 2alues for so*e tagna*es in the group are not collected at the specified data collection rate. O2erruns can .e pre2ented .1 phasing this rate. Run ?T!E-!A6 fro* the iBDM Base path.

Data file write failure. DisC *a1 .e full. Una.le to read data file. 7isting data file corrupted. 7isting data file read failure. 6o groups defined for collection. -1ste* ti*e has .een changed. ?T! cannot continue. ?T! warning =ualifier not found. Use an1wa13 Una.le to open configuration file. Run ?TA.

Run ?T!E-!A6 fro* the iBDM Base path. Run ?T!E-!A6 fro* the iBDM Base path.

A collection group *ust .e defined in ?istorical Assign .efore starting ?istorical !ollect. The s1ste* date or ti*e has .een changed to a ti*e that precedes data collection for the file. -top ?istorical !ollect; reset the ti*e or date; and restart ?istorical !ollect. The =ualifier .locC 1ou entered for the collection group in the ?istorical Assign progra* does not e7ist in the data.ase. This *essage appears if the historical path was changed in the -!U. Run ?istorical Assign and *odif1 a tag in each collection group so that the new configuration can .e read. This *essage appears if a historical collection group was deleted out of the iBDM ?TR path .1 a *eans other than ?TA.

rror initiali>ing ?T!. -o*e .DAT files *a1 ha2e .een erased.

'istorical *ispla%
'istorical *ispla% Message A pen group *ust contain at least one pen. !annot find chart group. Action or Meaning 5ou cannot delete all the pens in the pen group.

!hecC if the chart group 1ou entered for the %!( co**and line para*eter e7ists. There is no +ABDATA.D B file in the su.director1 fro* where 1ou are i*porting la. data. A data dictionar1 file *ust e7ist in each su.director1 fro* where 1ou i*port la. data A-!DD files. !hecC if the pen group 1ou entered for the %,( co**and line para*eter e7ists. !hecC if the ti*e group 1ou entered for the %T( co**and line para*eter e7ists. (U definitions for a 2aria.le entered in the la. data A-!DD file are not defined in the +ABDATA.D B file. (U definitions *ust .e entered in the +ABDATA.D B file for each 2aria.le 1ou i*port. 4aria.le na*es *ust .e entered identicall1 in .oth the la. data A-!DD file and the +ABDATA.D B file. The la. data A-!DD file 1ou tried to i*port could not .e opened. !hecC that the file na*e and path are 2alid. 5ou *ust enter a 2alue .etween 1 and 13# in the !olu*n field of the ?eader Dte* !onfiguration dialog .o7. 4erif1 that BDM RROR.TO4 is in 1our iBDM 6+- path.

!annot find data dictionar1.

!annot find pen group.

!annot find ti*e group.

!annot find 2aria.le in dictionar1. +ine ignored.

!annot open la. data file.

!olu*n *ust .e .etween 1 and 13#. !ould not open all *essage files. Data not in chronological order. 4alue ignored.

The entries in the la. data A-!DD file are not in chronological order. ach line of la. data *ust .e sorted .1 increasing date and then .1 increasing ti*e. Dn the +ABDATA.D B file; a duplicate entr1 defining a la. data 2aria.le e7ists. The first entr1@s (U definitions are usedL an1 duplicate entries are ignored. Re*o2e duplicate entries fro* the +ABDATA.D B files. Dn the la. data A-!DD file 1ou i*ported; a duplicate 2alue e7ists for a 2aria.le. The first entr1@s 2alue is usedL all duplicate 2alues are ignored. Dn the % T co**and line para*eter; 1ou specified an

Duplicate dictionar1 entr1. ntr1 ignored.

Duplicate 2alue for 2aria.le. 4alue ignored.

nd Ti*e "% T' ti*e specified.

'istorical *ispla% Message Duration "%DU' 2alue ignored.

Action or Meaning ending ti*e .ut 1ou also specified ending ti*e using the %DU para*eter. 5ou cannot use .oth. The % T end ti*e taCes precedence. nter a node na*e in the Tagna*e field .efore 1ou use the =uestion *arC .utton to displa1 a list of tagna*es for the node. An error occurred while i*porting a la. data A-!DD file. !hecC the error"s' listed in the error file that is written to the su.director1 fro* where 1ou tried to i*port. 4erif1 that ?TD,RD6T. M is in the iBDM .ase path.

nter a node na*e first.

rrors encountered on D*port. -ee the error file for *essages.

rror e7ecuting ?TD,RD6T. !hecC paths. rror found on co**and line. rror writing to .inar1 file. !annot continue. 7ceeded *a7i*u* nu*.er of groups. (roup not added. BileO-a2e can onl1 *odif1 an e7isting chart. Dn2alid dateTti*e. Bor*at is MMODDO55T??:MM:--. Dn2alid Da1s Before 6ow. Da1s Before "%DB' ignored. Dn2alid dictionar1 entr1.

!hecC the accurac1 of 1our co**and line s1nta7. Bile *a1 .e corrupted.

A *a7i*u* of 1)$$ groups can .e defined in a chart; pen; or ti*e group file. -ince 1ou created the chart using the 6ew co**and; 1ou can onl1 sa2e it with a -a2e As co**and. The 2alue 1ou enter for the start ti*e "%-T' or end ti*e "% T' para*eter is not 2alid. The %DB para*eter 1ou su.*itted is not 2alid. 4alid 2alues range fro* $%&&&. An in2alid entr1 e7ists in the +ABDATA.D B file. !hecC the file for for*at errors or in2alid characters. The duration 2alue 1ou entered is in2alid. Ma7i*u* duration is &&:#3:)&:)&. Mini*u* duration is $$:$$:$$:1$. Bor*at is "Da1s:?ours:Minutes:-econds'. !hange the duration to 1$ seconds or greater.

Dn2alid duration. Bor*at is DD:??:MM:--.

Dn2alid duration. Mini*u* duration is 1 seconds. Dn2alid entr1 in data file.

Dn the la. data A-!DD file 1ou tried to i*port; there is an in2alid entr1. !hecC the file for for*at errors or in2alid characters. A 2aria.le na*e in the la. data A-!DD file 1ou are i*porting is in2alid. MaCe sure there are no in2alid

Dn2alid la. 2aria.le na*e.

'istorical *ispla% Message

Action or Meaning characters in the na*e. 4alid characters are A through U; through &; underscore " E '; and dash "%'.

Dn2alid Ti*e Before 6ow. Ti*e Before "%TB' ignored.

The %TB para*eter 1ou su.*itted is not 2alid. Bor*at is ??:MM:--. Mini*u* ti*e is $$:$$:1$. Ma7i*u* ti*e is #3:)&:)&. 5ou *ust enter a 2alue .etween 1 and 3& in the Ma7i*u* length field of the ?eader Dte* !onfiguration dialog .o7. ?istorical Displa1 re=uires the !?ART.?(,; , 6.?(,; and TDM .?(, files in order to run. The1 are located in the iBDM ?TR path. ?istorical Displa1 creates default files if there are no ?(, files.

Ma7i*u* length *ust .e .etween 1 and 3&. Missing an ?(, file. Delete e7isting ones or find the *issing ones.

Must pro2ide a la.el andOor ite*. Dn the ?eader Dte* !onfiguration; .oth the +a.el field and Dte* field cannot .e e*pt1. 5ou *ust enter a 2alid 2alue in at least one of the fields. 6a*e does not e7ist in 6etworC 6a*e Ta.le. !annot fetch li*its .ecause a session is not esta.lished with the specified node. sta.lish a session with the node in the -!U. The tagna*e =uer1 scans files created in the last 4$ hours. 6o tagna*es are a2aila.le .ecause no historical data files were created for the node in that ti*e period. Dn the %-T co**and line para*eter; 1ou specified a starting date .ut 1ou also specified starting date using the %DB para*eter. 5ou cannot use .oth. The %-T start date taCes precedence. Dn the %-T co**and line para*eter; 1ou specified a starting ti*e .ut 1ou also specified starting ti*e using the %TB para*eter. 5ou cannot use .oth. The %-T start ti*e taCes precedence. !hange the % T co**and line para*eter to .e greater than the %-T 2alue. !annot fetch li*its .ecause the tagna*e is not defined for the node. The group na*e entered is a duplicate. nter a uni=ue group na*e. A pen or ti*e group cannot .e deleted if it is part of an e7isting chart group. ither delete or redefine the chart group.

6o current data collect files a2aila.le to =uer1 for this node.

-tart Ti*e "%-T' date is specified. Da1s Before "%DB' 2alue ignored.

-tart Ti*e "%-T' ti*e is specified. Ti*e Before "%TB' 2alue ignored.

The end ti*e is less than the start ti*e. 4alues ignored. Tagna*e is not defined.

This description alread1 e7ists. ,lease rena*e. This group is referenced .1 !hart EEEEE and cannot .e deleted.

+et,ork Error Codes


The following sections list the error codes; *essages; and e7planations for the networC errors 1ou can encounter if 1ou e7perience pro.le*s with 1our networC.

(tartup Error Codes


Df a networC pro.le* occurs during startup; one of the error codes or *essages listed in the following ta.le *a1 appear. Error Code 1/13 Error Message *escription

Duplicate na*e in local na*e ta.le.

A na*e conflict e7ists in the +ocal 6a*e Ta.le within 6etBDO-. 7a*ine the na*es added .1 third%part1 networCing software to find the source of the conflict. This error can also occur if iBDM did not shut down properl1 prior to starting .acC up. Dn this case; restart the co*puter and iBDM.

1/##

6a*e in use on re*ote node. Underl1ing networC su.s1ste* not read1. T!,TA-F: Bailed to initiali>e networC su.s1ste*. Aindows -ocCets A,D 2ersion *is*atch.

The node na*e assigned to the node is currentl1 in use on another node. Rena*e one of the nodes to correct this conflict. T!,OD, is not installed properl1 or is *issing. Use ,D6( or T!,TA-F to 2erif1 that the underl1ing T!,OD, is set up .efore atte*pting to run iBDM.

8)$1 8)$#

8)$3

Ahen atte*pting to initiali>e the AinsocC T!,OD, interface; T!,TA-F detected that the AinsocC 2ersion is less than 1.1.

Run ti%e Error Codes


Df a networC pro.le* e7ists that pre2ents sessions fro* esta.lishing or causes sessions to .e ter*inated; one of the error codes listed in the following ta.le *a1 appear in the 6 TDDA( progra*. Error Code 1/$) 1/$8 Error Message *escription

!o**and ti*ed out. These errors occur when the re*ote node is down. Ahen the re*ote node is .rought .acC up; the !onnection Manager re% Dn2alid +ocal -ession esta.lishes the session. 6u*.er.

Error Code

Error Message

*escription

1/1$ 1/#4

-ession !losed. -ession nded A.nor*all1. !an@t find na*e called. The session cannot .e esta.lished .ecause either a re*ote node is not operating; a ca.ling pro.le* e7ists .etween the nodes; or the re*ote node na*e is not registered on the networC. 4erif1 .oth nodes are running co*pati.le networC software. Also; run 6BT -T as discussed in the section Trou.leshooting 6etBDOwith 6BT -T.

1/#$

1&14

!onnection 6OT esta.lished with node. BDM d1na*ic connection in progress. BDM has .een shut down on re*ote node.

The !onnection Manager has not 1et esta.lished a connection with the re*ote node. Aait for !onnection Manager to esta.lish the session. !onnection Manager is in the process of esta.lishing a d1na*ic connection with the re*ote node. Aait for !onnection Manager to esta.lish the session. !onnection Manager has detected that iBDM has .een shutdown on the re*ote node. This error code shows up te*poraril1 and then changes to 1&14.

1&/$

1&/4

8)1R

6ode not found in The node na*e that 1ou are tr1ing to connect to .e resol2ed to an T!, hosts data.ase. D, address. The na*e is pro.a.l1 not in the local hosts file or on the AD6- ser2er. O.tain the re*ote node@s D, address and add it to the ?O-T- file.

Application .alidator
The following list descri.es the audit *essages associated with the Application 4alidator. These *essages descri.e the e2ents that can occur "to the operator' when running the Application 4alidator: Application 4alidator P Baseline Bile has .een ta*pered withV Application 4alidator P !o**and%line: !reate Baseline Application 4alidator P !o**and%line: ,rint !o*parison Detail Application 4alidator P !o**and%line: ,rint !o*parison -u**ar1 Application 4alidator P !o**and%line: ,rint -ingle Baseline Application 4alidator P !o**and%line: -a2e !o*parison Detail Application 4alidator P !reate Baseline Application 4alidator P rror retrie2ing securit1 user Application 4alidator P rror with !o*pare Director1: Ss Application 4alidator P rror with Bill Baseline Detail: !hecCsu* difference for .aseline file: ISsJ. Ss

Application 4alidator P rror with Bill Baseline Detail: Bailed to read encr1pted .aseline file: ISsJ. Ss Application 4alidator P Bailed to start Application: Ss Application 4alidator P iBDM isn@t running Application 4alidator P Dnsufficient -ecurit1 Rights Application 4alidator P Dn2alid -ecurit1 Beature Application 4alidator P ,rint Baseline -tatusO!o*parison -u**ar1 Application 4alidator P Report !o*parison Detail Application 4alidator P Report !o*parison -u**ar1 Application 4alidator P Report ,rinted Application 4alidator P Report -a2ed Application 4alidator P Report -ingle Baseline Application 4alidator P -ecurit1 not ena.led Application 4alidator P User not logged in

+9!E: The Ss in these *essages is replaced with the actual the director1 na*e when the *essage appears.

Importing iFIX /ictures into /ro0ic% /ortal


5ou *a1 encounter *e*or1 errors while atte*pting to i*port either one 2er1 large file; or a series of files. Df this occurs; 1ou will recei2e a *essage stating that there has .een a *e*or1 error. An1 files that were selected for i*port .ut not processed appear light gra1 in the list. Dt is reco**ended that 1ou restart 1our we. .rowser after recei2ing this error. Df 1ou encounter the *e*or1 error; tr1 the following: Reduce the picture si>e or nu*.er of pictures: Df 1ou are i*porting *ultiple files; tr1 i*porting a s*aller nu*.er of files at a ti*e. Df 1ou are i*porting a single; large picture; in iBDM; edit the picture so that it contains fewer o.Hects. 5ou can then re%e7port the picture and tr1 the i*port again. Df 1ou are i*porting a single; large s1*.olOtag group file; then that file should .e .roCen up into *ultiple; s*aller tag group files and re%e7ported. Bor *ore infor*ation on using *ultiple s1*.ol files in a picture; refer to the iBDM lectronic BooCs symbols topics "tip: t1pe symbols in the lectronic BooCs Dnde7'. Dncrease the a*ount of *e*or1 a2aila.le to the Wa2a plugin. Dt is reco**ended that 1ou increase the Wa2a plugin *e*or1 on a te*porar1 .asis onl1; unless *e*or1 issues are persistent. To increase the *e*or1: 1. Open the Wa2a control panel. 2. -elect the Wa2a ta.. 3. !licC the Wa2a Applet Runti*e -ettings 4iew .utton. The Wa2a Runti*e -ettings dialog .o7 appears. 4. Dn the Wa2a Runti*e ,ara*eters .o7; add %M*7#)/*. +9!E: #)/ is a suggested nu*.er. Df the nu*.er is higher; depending on the operating s1ste*; the Wa2a plugin *a1 fail to load. o !licC OF twice to sa2e 1our changes and close the Wa2a control panel. Ahen the i*port is co*plete; re*o2e the %M*7#)/*.

+9!E: Dn so*e e7tre*e cases; the i*port will ne2er return "that is; the D*port utilit1 is unresponsi2e'. Df this occurs; cancel the i*port; restart 1our .rowser; and follow the sa*e steps to pre2ent the pro.le* "see pre2ious .ullet points'.

"12 !rigger Block Alarms and Block Errors


Alarm or Block *escription Error RROR -0+ +O( An undeter*ined error occurred. An error occurred and the -0+ application could not connect to the relational data.ase or 1ou lost a connection. An error occurred .ecause the application could not find the -0+ co**and or the co**and was too long. An error occurred while reading an iBDM field. An error occurred while writing to an iBDM field. An error occurred .ecause the nu*.er of 2alues in the -0+ co**and does not *atch the nu*.er of ite*s in the -0+ Data .locC. 6o error has occurred.

-0+ !MD

B+D R AD B+D ARDT DAT MAT!

OF

iFIX and FIX on the "ame Computer


An application error occurs when 1ou start up BDM R.$ as a ser2ice under Aindows after 1ou install iBDM. The error occurs .ecause .oth BDM R.$ and iBDM 4.$ use the sa*e Ce1 na*e "BDM' under the -er2ices Ce1 in the registr1. Therefore; when 1ou install iBDM 4.$; it o2erwrites the entr1 for BDM R.$. ach product needs to ha2e its own -er2ices Ce1. BDM R.$ runs correctl1 if it is not run as a ser2ice. The worCaround for this pro.le* is to edit the registr1 so that the -er2ices Ce1 points to the ser2ice e7ecuta.le in the correct path. The Ce1 is located in ?F 5E+O!A+EMA!?D6 Q-1ste*Q!urrent!ontrol-etQ-er2icesQBi7. -et the D*age,ath 2alue to the correct path for fi7sr2.e7e.

*atabase Manager
5ou can ensure a process data.ase contains no configuration errors .1 2erif1ing it. 4erif1ing a data.ase also ensures that iBDM can process each .locC and that the data.ase functions as 1ou intend. Ahile 2erif1ing a process data.ase; Data.ase Manager ensures that each .locC: Ds in onl1 one chain. Ds linCed to an appropriate .locC "for e7a*ple; a -tatistical !ontrol .locC can .e preceded onl1 .1 a -tatistical Data .locC'.

Ds used in the correct conte7t "for e7a*ple; as a stand%alone; a pri*ar1; or a secondar1 .locC'. Does not reference non%e7istent .locCs.

Df Data.ase Manager detects no errors; it displa1s a *essage .o7 to infor* 1ou. ?owe2er; if it encounters errors; the 4erif1 Data.ase dialog .o7 appears. This dialog .o7 lists each error and the .locC that contains it. The following ta.le lists the possi.le 2erification errors and how to resol2e the*. Resol#ing .eri0ication Messages =hen %ou see the message... tagname a:tagname b Tag is in *ore than one chain It means... !o correct this con0iguration...

The .locC; tagname b; has Re*o2e one or *ore linCs to tagname *ore than one upstrea* .locC b. linCed to it. Tagname a identifies one of these .locCs. 5ou *a1 ha2e a secondar1 Re*o2e the secondar1 .locC or add a .locC that is not in an1 chain or pri*ar1 .locC to the start of the chain. is the first .locC in a chain. The .locC; tagname; chains to a !reate a .locC with the na*e specified .locC that does not e7ist. in the 6e7t field or enter the na*e of a .locC that e7ists. The .locC; tagname; contains its own na*e in its 6e7t field. !hange the na*e in the 6e7t field or lea2e it .lanC. Df 1ou want to repeatedl1 perfor* a tasC; use a ,rogra* .locC instead. !reate the .locC or change the reference to a .locC that e7ists.

tagname:Tag is not in an1 chain

tagname: BlocC not found for 6 MT

tagname:!hains to itself

tagname: is not defined

The .locC; tagname; does not e7ist and another .locC references it. The field; fieldname; does not e7ist and it is referenced .1 a .locC in the data.ase.

fieldname 6o such field in BDT

!hange the reference to a field that e7ists.

7ceeding MAM chain si>e of 3$

The data.ase contains a chain Redesign this chain .1 .reaCing it into with *ore than 3$ .locCs. two s*aller chains or re*o2e an1 unnecessar1 .locCs.

5ou can correct an1 error .1 dou.le%clicCing it to displa1 the associated .locC configuration dialog .o7. To correct errors: 1. dit the .locC to correct the pro.le*. #. -a2e the .locC. 3. Re%2erif1 the data.ase.

Mission Control
AAM Ta)
The following ta.le details possi.le *essages that the Auto Alar* Manager *a1 displa1 during its operation; and lists potential solutions to the pro.le* that the *essages con2e1. These *essages appear in the top half of the AAM ta. in the Mission !ontrol window. !roubleshooting Auto Alarm Manager Messages in Mission Control Message !annot find the phone .ooC entr1 "olution The pri*ar1 or secondar1 contact specified in the -!U is not defined in the RA- phone .ooC. !reate a phone .ooC entr1 for each contact .efore continuing. Refer to 1our Microsoft *anuals for instructions.

?ardware failure in port or attached The Auto Alar* Manager cannot co**unicate with the de2ice local *ode*. 4erif1 that the ca.le connection .etween the *ode* and the co*puter is secure. Df the pro.le* persists; tr1 a different ca.le or *ode*. !annot detect carrier The Auto Alar* Manager could not esta.lish a connection to the Recei2ing node. MaCe sure the RA- ser2er is running. Also *aCe sure the local *ode* detects a dial tone when it dials the pri*ar1 or secondar1 contact. Do the following: 1. -elect the phone .ooC entr1 1ou want to edit. #. Bro* the Re*ote Access dialog .o7; clicC dit. !licC Ad2anced. Df the Basic .utton appears; proceed to the ne7t step. 3. !licC Mode*. 4. !lear the nter Mode* !o**ands Manuall1 checC .o7. ). !lose all open dialog .o7es and e7it the Re*ote Access progra*. The ne7t ti*e the Auto Alar* Manager dials; 1ou should not recei2e an error. Testing the connection... !onnection BAD After esta.lishing RA- and iBDM connections; the Auto Alar* Manager on the -ending node sent a test *essage to the Recei2ing node and did not get a response. MaCe sure that Auto Alar* Manager is running on the Recei2ing node. Df it is not; start it. The currentl1 logged in user or the na*e of the user account specified in the Ad2anced -end Alar* -ettings dialog .o7 does not ha2e the necessar1 rights to dial into

RRORED6T RA!TD4 EMOD

The account does not ha2e re*ote access per*ission

!roubleshooting Auto Alarm Manager Messages in Mission Control Message "olution the RA- ser2er. Use the RA- Ad*inistrator progra* on the ser2er node to grant dial%in rights to the necessar1 users. All AAM session atte*pts failed The Auto Alar* Manager could not co**unicate with the Auto Alar* Manager on the re*ote node. MaCe sure the following conditions e7ist: The na*es of the pri*ar1 and secondar1 contacts *atch the na*es of re*ote nodes associated with each RA- phone .ooC entr1. Df the1 do not; edit the entries. Refer to 1our Microsoft *anuals for *ore infor*ation. The Auto Alar* Manager is started with the correct co**and line para*eter on the -ending and Recei2ing nodes. Use the Oc para*eter on the -ending node and the Os para*eter on the Recei2ing node. Refer to the D*ple*enting Alar*s and Messages e%.ooC for *ore infor*ation. The -ending and Recei2ing nodes are not on the sa*e +A6.

rror 1311 setting e*ergenc1 tag

The Auto Alar* Manager could not set the specified *ergenc1 tag configured in the -!U. -o*e of the reasons for this could .e: The specified TA( does not e7ist in the data.ase. The specified 6OD does not e7ist or is not reacha.le.

rror 1311 setting recei2e tag

The Auto Alar* Manager could not set the specified Recei2e tag configured in the -!U. -o*e of the reasons for this could .e: The specified TA( does not e7ist in the data.ase. The specified 6OD does not e7ist or is not reacha.le.

Disa.le tag can@t .e read

The Auto Alar* Manager could not read the specified Disa.le tag configured in the -!U. -o*e of the reasons for this could .e: The specified TA( does not e7ist in the data.ase. The specified 6OD does not e7ist or is not

!roubleshooting Auto Alarm Manager Messages in Mission Control Message "olution reacha.le. Df 1ou get this error; the AAM will Ceep running; and it cannot .e disa.led. +9!E": The AAMT!,.e7e can onl1 read fro* or write to a data.ase tag on a local iBDM node. 5ou cannot read or write to re*ote nodes. Dn other words; 1ou cannot disa.le the Auto Alar* Manager fro* a tag on a re*ote nodeL it will alwa1s .e running. 5ou cannot set an *ergenc1 tag or Recei2e tag on a re*ote node. Dt has to .e on the sa*e "local' node which the AAMT!,.e7e is running on. 5ou cannot acCnowledge an alar* that co*es fro* a re*ote node. Bor the alar* to .e acCnowledged; it has to .e fro* the sa*e "local' node that the AAMT!,.e7e is running on. Df it is not; the alar* will still .e sent to the Recei2er node; .ut will not .e acCnowledged .1 the -ender node.

(*& Ta)
5ou can displa1 the setup and status of iBDM ODB! in Mission !ontrol. ach status field is descri.ed in the following ta.le. -1ste* TasC -tatus !odes "tatus Code *escription Alar* adi De.ug adi Displa1s the ena.led alar* areas. Displa1s the ena.led de.ug areas.

Alar* screen Dndicates whether alar* *essages are sent to the -0+ tasC. 5es < send *essagesL 6o < send no *essages. De.ug screen -=l c*d t.l Dndicates whether de.ug *essages are sent to the -0+ tasC. 5es < send *essagesL 6o < send no *essages. 6a*e of the -0+ +i.rar1 Ta.le.

-1ste* TasC -tatus !odes "tatus Code *escription -=l err t.l 6a*e of the -0+ rror +og Ta.le.

-=l c*d d.id 6a*e of the Data.ase Ddentifier specified in the -!U@s -0+ TasC !onfiguration. ,ri* file -econd. file +ogin dela1 ,ri*ar1 .acC%up file. -econdar1 .acC%up file. 6u*.er of seconds to wait .efore atte*pting to login once a connection is lost. The default is 3$$ seconds. Ma7i*u* -0+ co**and length. 6a*e of the local node. Ddentifies the status of the -0+ tasC. This field can displa1 whether the -0+ tasC is logged onto one or se2eral relational data.ases. -tatus of -0+ caching.

Ma7 s=lc*d 6odena*e !urrent status !aching status

"12 "er#er
+i.rar1 and rror ta.les can .e created fro* the client or the ser2er using nterprise Manager or D-0+. Use the following ta.les in this section as guides for the -0++DB and -0+ RR ta.les. Microsoft -0+ -er2er -0++DB Ta.le Field +ame s=lna*e s=lc*d *atat%pe +otes

2archar; si>e 8 2archar; si>e 1$$ % #))

!reate a uni=ue inde7 on this field. Df an1 of 1our -0+ co**ands are longer than #)) characters; *aCe this field a Te7t field. This allows o2er # .illion characters.

Microsoft -0+ -er2er -0+ RR Ta.le Field +ame td node *atat%pe dateti*e 2archar; si>e 8

Microsoft -0+ -er2er -0+ RR Ta.le Field +ame tag s=lna*e s=lEerr fi7Eerr progEerr *atat%pe 2archar; si>e 1$%3$ 2archar; si>e 8 2archar; si>e #)$ 2archar; si>e 1$$ 2archar; si>e 1$$

+9!E: -0++DB and -0+ RR are the default na*es for the ta.les. 5ou can na*e the* an1thing 1ou wish as long as those na*es are reflected in the -!U. ?owe2er; the field "colu*n' na*es *ust .e entered e+actl, as shown. Use the following co**ands to create the +i.rar1 ta.le; Dnde7; and rror +og ta.le if using D-0+:

*isco#er% And Auto5Assembl% Component 6*AC7


Bro,se Failure Df all *ethods were successful; then a co*plete list of the ser2ers found on the *achine is displa1ed. Df no ser2ers were found on the *achine; the *essage N6o ser2ers were found on the *achineN is displa1ed. 5ou *ust then 2erif1 that either the correct *achine na*eOT!,OD, address was entered in the pre2ious page or that the O,! ser2er"s' are correctl1 installed on the gi2en *achine. Df one or *ore *ethods fail; a *essage .o7 is displa1ed indicating the *ethods that were used and which ones succeeded or failed. Dt also displa1s an error *essage indicating the reason for failure; as returned .1 the s1ste*. An1 ser2er"s' found are listed. 5ou can select a ser2er fro* the list or re*ed1 the reason for the failure and rerun the search.

**E
The following ta.le descri.es the errors; associated *essages; and corresponding e7planations associated with the DD !lient tasC. These *essages appear in the +ast rror fields on the DD !lient TasC dialog .o7 and in the configured *essage destinations. Communication Messages Message 6one !annot esta.lish con2ersation. -er2er reHected re=uest. E>planation 6o co**unication pro.le*s ha2e occurred. Df the connection is local; the error indicates that either the ser2er is not running or the topic does not e7ist. iBDM pro*pts 1ou to start the ser2er the first ti*e this error is detected.

Communication Messages Message E>planation

Df the connection is through 6etDD ; this error *a1 indicate a networC pro.le*. !annot esta.lish con2ersation; cannot create ad2ise list. The s1ste* has run out of *e*or1 while the DD !lient TasC is atte*pting to *aCe a connection to a ser2er.

!annot esta.lish The s1ste* has run out of *e*or1 while the DD !lient TasC is con2ersation; cannot add atte*pting to *aCe a connection to a ser2er. to list. !annot start ad2ise loop; The con2ersation with the DD ser2er has started .ut there is a pro.le* ser2er reHected re=uest. with the ite*. !annot start ad2ise loop; The s1ste* has run out of *e*or1 while atte*pting to esta.lish cannot add to list. co**unication. !annot start ad2ise loop; The ser2er reHected the initial re=uest for data *ade .1 the client. The ser2er reHected data ad2ise loop has .een successfull1 esta.lished .ut the ser2er refuses to re=uest. pass data .acC to the client. This *a1 indicate the ser2er is o2erloaded. !annot start ad2ise loop; The ser2er tooC too long to acCnowledge a re=uest .1 the client to start re=uest ti*ed out. an ad2ise loop and the client ti*ed out. This indicates the ser2er is te*poraril1 o2erloaded. !annot e7ecute The DD client atte*pted to e7ecute a co**and on the ser2er. co**and; re=uest ti*ed out. -er2er is .us1. +ow on *e*or1. The ser2er was o2erloaded while a DD transaction was atte*pted. The ser2er was low on *e*or1 while a DD transaction was atte*pted.

Me*or1 allocation failed. The ser2er was low on *e*or1 while a DD transaction was atte*pted. User does not ha2e rights to shut down the DD !lient TasC. The user atte*pted to shut down the DD !lient TasC .ut does not ha2e sufficient securit1 rights to do so. The user *ust ha2e the BacCground TasC 7it application feature in his user profile in order to shut down the DD !lient TasC. The user has entered an in2alid character or a 2alue out of range in the Ma7i*u* +inCs field. The 2alid range is 1 % 1$$$. The user has entered an in2alid character or a 2alue out of range in the Access ,eriod field. The 2alid range is $ to 1R#8$$ seconds.

Dn2alid Ma7i*u* +inCs.

Dn2alid access period.

Communication Messages Message !annot create DOO list "checC *e*or1'. !annot create ad2ise loop list. E>planation The s1ste* has run out of *e*or1 while esta.lishing co**unication with a ser2er. The s1ste* ran out of *e*or1 while the user was opening the Acti2e Ad2ise +oops dialog .o7.

The following ta.le descri.es the s1ste* *essages and corresponding e7planations associated with the DD ser2er. **E "%stem Messages Error Code E>planation 11)$ 1#$& 1#1# 1#13 1314 1/$8 1/#$ 1/#4 1R)$ #$$) #3$# 1/#$ 3 1$$ %13 RROR:&& iBDM is not running. Dn2alid field. Bield@s 2alue not Cnown or .locC *a1 .e off scan. Dn2alid field. Dn2alid field. 6etworC%related pro.le*. -ession not esta.lished. !annot find re*ote node. -ession with re*ote node has .een lost. Tag is not defined in the data.ase. 6etworC%related pro.le*. ither waiting for data or node na*e is not in the networC ta.le. -ession not esta.lished. !annot find re*ote node. Dn2alid node; tag; or field entered; or pro.le* returning data. 6o co**unication esta.lished with DD . Dn2alid node; tag; or field entered; or pro.le* returning data.

The following ta.le descri.es the *essages and corresponding e7planations that can occur when starting the DD !lient TasC. The error will .e displa1ed in the Runti*e rror field and the configured *essage destinations. **E Client "tartup Messages Message !annot initiali>e DD M+ E>planation A connection could not .e *ade to the DD M+.D++ file. ither the file does not e7ist or it is not in the Aindows search path. The s1ste* ran out of *e*or1 tr1ing to set up the con2ersation list.

!annot create con2ersation list "!hecC *e*or1' Out of ti*er resources

There are too *an1 tasCs running si*ultaneousl1. 5ou should shut down a tasC to free up a ti*er for the DD !lient tasC ti*er.

Access
iBDM pro2ides the -0+ RR.TMT te7t file; located in the !:Q,rogra* BilesQ( BanucQ,rofic1 iBDMQApp director1; to help 1ou trou.leshoot co**unication errors fro* 1our relational data.ase. This file contains co**unication error nu*.ers. Ahen a co**unication error occurs; iBDM displa1s T s1*.ols ".1 default' in a data linC to indicate the pro.le*. Df 1ou are using Access; so*e of the sa*e error nu*.ers listed in the -0+ RR.TMT file are used to indicate relational data.ase errors. As a result; 1ou *a1 see T s1*.ols in the run%ti*e en2iron*ent when no co**unication error has occurred. To correct this pro.le*; delete the -0+ RR.TMT file.

'istorian "er#er
During a failed write atte*pt to the ,rofic1 ?istorian -er2er; the iBDM AorC-pace .eco*es inacti2e. 5ou can control how long this lasts .1 setting the nu*.er of seconds 1ou allow for the connection ti*e%out. The default is &$ seconds. To configure the ti*e%out; add this setting to the Bi7User,references.ini file in the iBDM +ocal folder: I?istorianJ Ti*eout-ecs<1$ ?ere; the ti*e%out is set to 1$ seconds. The 2alid range is ) to 3$$ seconds; though not enforced.

.isiconX
Dn the runti*e en2iron*ent; the Data !ontrol displa1s !onnection rror. MaCe sure the ta.le in the =uer1 is accessi.le. !reate a =uer1 using the Ta.le co**and and run the =uer1 again. Df the *essage reappears; the ta.le is not accessi.le.

!hecC 1our user pri2ileges. 5ou *a1 not ha2e the necessar1 pri2ileges to access the ta.le. Re2iew the data source and data con2ersion selected for all o.Hects and ani*ated =uer1 properties.

-1ste* Messages

"%stem Messages
-1ste* *essages pro2ide infor*ation a.out co*pleted tasCs and errors. iBDM generates a s1ste* *essage when: A data.ase finishes loading. The state of a networC session changes. An DOO dri2er detects an error. The -can; Alar*; and !ontrol "-A!' progra*: -tarts up. !o*pletes a specific tasC. ncounters specific data.ase .locC or chain errors. ncounters run%ti*e or s1ste* errors.

9/C Errors
ach ani*ated o.Hect in a picture uses O,! protocols to recei2e data and report errors. The ani*ation error preferences define the default error strings and 2alues that the o.Hect uses when an error occurs. Bor e7a*ple; .1 default; when a co**unication error occurs; Data linCs displa1 the te7t NTTTTN. 5ou can custo*i>e the ani*ation error defaults .1 entering new 2alues in the Ani*ations Data rror Defaults ta.. B1 changing the defaults; 1ou *aCe the default error *essages *ore intuiti2e for 1our industr1. Bor e7a*ple; when a co**unication error occurs; 1ou can ha2e Data linCs displa1 the following te7t .1 entering it into the !o** field of the Bor*at Ani*ation O.Hect Defaults area: !annot co**unicate with ser2er

Alarming
no destination is currentl% a#ailable to dispatch the alarm Df 1our s1ste* is networCed; .e sure that the Alar* 6etworC -er2ice is alwa1s ena.led. Df the Alar* 6etworC -er2ice is disa.led; 1ou *a1 recei2e an error *essage stating that no destination is currentl1 a2aila.le to dispatch the alar*. +9!E: Df the local co*puter does not ha2e a configured session with a re*ote -!ADA ser2er; the local co*puter does not recei2e alar*s or *essages fro* the re*ote -!ADA ser2er.

iFIX 9*BC
*ata source name not 0ound and no de0ault dri#er speci0ied. Dn order to run the -0+ tasC "A-0+OD!. M ' as a ser2ice; 1ou must use s1ste* data sources. Df 1ou atte*pt to use a user data source; 1ou will get an error si*ilar to the one a.o2e.