| Author |
Message
|
| gdiehl |
 Posted: Tue Apr 15, 2008 6:31 am Post subject: FMC00012E Incorrect Password errors after WBM <-> WF i |
 |
|
Novice
Joined: 03 Oct 2007
Posts: 15
Location: Binghamton, NY
|
I'm afraid I shot myself in the foot. I'd appreciate any recovery suggestions, short of completely reinstalling Workflow.
In order to get familiar with exporting FDL from the WS Business Modeler and importing it to Workflow, I did the following:
1) Imported my currently running Workflow FDL file into WBM. At a cursory level, all processes looked fine in WBM.
2) Exported from WBM to new a FDL file
3) Imported FDL from step 2 to Workflow BT and then exported to RT
4) Imported to RT via fmcibie. Got some FMC21730W messages about bogus processes created by WBM not having any executables but no severe errors. RT database updated.
Now the trouble started. I could no longer logon via WebClient using any of the userIDs. All failed with the FMC00012E errors. Nor could I logon to Admin utility or import any new FDL via fmcibie. All login attempts fail with Incorrect Password.
I'd appreciate any suggestions regarding specifcaly what may have been corrupted and how I might recover. An old post mentioned importing incorrect System or Group names but both of these look OK in the imported FDL file.
Thank you
_________________
Keep 'em in the short grass
Gary |
|
| Back to top |
|
 |
| hos |
| Posted: Wed Apr 16, 2008 12:34 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Never change ADMIN without having a fallback!
You have different options:
- find out and use the admin password that you modeled in WBM
- manually modify the password field in the RT DB using an encrypted value
where you know its clear text
- contact IBM support. They have a password repair tool.
GOOD LUCK! |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Apr 16, 2008 5:19 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Once you recover, I would strongly recommend that you add the following user only to your Runtime database, this way you will not have to worry about any buildtime exports overlaying it.
| Code: |
PERSON 'EMERGENCY'
DESCRIPTION ""
AUTHORIZED_FOR STAFF
AUTHORIZED_FOR AUTHORIZATION
AUTHORIZED_FOR OPERATION
AUTHORIZED_FOR TOPOLOGY
AUTHORIZED_FOR PROCESS_MODELING
AUTHORIZED_FOR PROCESS_CATEGORY ALL AS_ADMINISTRATOR
AUTHORIZED_FOR WORKITEMS_OF ALL
IS_NOT_ABSENT
DO NOT RESET_ABSENT
END 'EMERGENCY'
|
This should be a requirement in every RTDB. Note that in the above with No system group and no system it will import fine into any RTDB as it will use the default values for that RTDB, and you will have a properly encrypted password of "password".
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| gdiehl |
| Posted: Mon Apr 21, 2008 4:08 am Post subject: SOLVED: FMC00012E Inc. PW errors after WBM <-> WF imp |
|
|
Novice
Joined: 03 Oct 2007
Posts: 15
Location: Binghamton, NY
|
Thanks all. Finally got my toes re-attached. I ended up deleting and recreating the RT database. I also added that EMERGENCY userid like you suggested, John, because since I'm not exactly sure why this happened, I expect it will happen again.
_________________
Keep 'em in the short grass
Gary |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Apr 21, 2008 6:23 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Gary:
The key thing is to not put this Emergency id into any BT database. In my experience this happens when someone does an export of all staff out of BT.
Glad to hear you are back up and running
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
