Unsolved
This post is more than 5 years old
1 Rookie
•
106 Posts
0
1998
September 12th, 2012 04:00
Has anyone seen this Solutions Enabler (SYMAPI) error?
"Storage Agent for Symmetrix failed to establish a session on Host=localhost due to Error=SYMAPI_C_DB_FILE_TOO_NEW"
This is via ECC 6.1UB12, Solutions Enabler 7.4 on a Windows Server 2008 (x64). Not sure why I am getting that error and I cannot seem to find the issue posted on Powerlink anywhere.
No Events found!
jarbarian
1 Rookie
•
106 Posts
0
September 12th, 2012 04:00
By the way this is in relationship to a VMAX as I am not getting updated data anymore in ECC on the VMAX since this error popped up.
jarbarian
1 Rookie
•
106 Posts
0
September 12th, 2012 05:00
I can try doing that. There are no local device groups on this particular server that I know of so I will check them first and try your options. Yes, the Symmetrix Agent (and all hosts with ECC agents) have been patched/updated. Thank you, let me give that a whirl.
PedalHarder
3 Apprentice
•
465 Posts
0
September 12th, 2012 05:00
Try renaming the symapi_db.bin file then do a symcfg discover to recreate it. If you have device groups defined locally on the host you will need to export them first and import them into the new symapi_db.bin.
Bounce the symmetrix agent after you have done this and check if the errors are still there.
BTW, has the symmetrix agent been upgraded to UB12?
Sam Claret
86 Posts
0
September 12th, 2012 06:00
When you renamed the symapi_db.bin did you rename the symapi_topology.xml if not you may want to do that as well.
When you do this please stop all ECC agents and SMC services and stop any SE daemons (stordaemon list and note the running daemons * next to them. Then stordaemon shutdown ALL –immediate)
Then rename the 2 files
Then symcfg discover
Restart any daemons you had before that are not running now – storapid should restart as soon as you run the symcfg disco.
Restart ECC.
If you don’t stop the daemons and associated ECC/SMC services you will be unable to rename the symapi_db.bin.
Sam Claret
Technical Support Engineer III
Worldwide Technical Support – OSAPI Windows
Office Hours: Rotating shift, 7AM – 4PM GMT
Office #: +353 21 494 5981
jarbarian
1 Rookie
•
106 Posts
0
September 12th, 2012 06:00
So far no-bueno. I decided to upgrade to 7.4.0.6 hoping that might fix the issue. I am bouncing the servers now and yes I did run a backup of the device groups just to be safe and renamed the old SMAPI_DB.BIN file to OLD so I had a copy of that if necessary.
jarbarian
1 Rookie
•
106 Posts
0
September 12th, 2012 08:00
Ok Sam thanks for that, I will try it again using this option. Appreciate the advice!