04-16-2013 07:55 AM
Hello,
I have an archive that is stopped and when i try to delete it I get the following error
BmsArchiveDao::archiveStop() called with null name
All that it says in the viewable archives listing is Name= 0 and N/A on everything else except there is no experation and the archive state is stopped. I am going to have to dump this from console login aren't I? Has anyone seen this before?
Thanks
06-12-2014 12:23 PM
I haqve same problem when I try to syncronizate videosurveillance server
02-10-2015 09:35 AM
I opened TAC Case Enginner goes to database, I dont know what he does but fixes this problem.
Unfortunatelly this server becames very slow, and we need to reinstall it from begining.
06-13-2014 05:43 AM
Hi Dean,
Which version of VSM are you working with? Also, is it safe to assume VSOM and VSMS are co-located on the same server instance?
06-13-2014 08:29 AM
06-20-2014 06:19 AM
I just took a second, closer look at your screenshot and noticed you are attempting to administer VSM from within a VNC session to the server(?) using the Firefox browser. This absolutely will not work. I'd say first step is to retry administrating VSM from a supported IE browser. If that doesn't get you anywhere, you'll likely have to dig deeper (old BWT pages via the VSMC page), or open a TAC case.
Cheers,
01-18-2015 08:05 AM
Was this ever resolved? If so, how? I am having the same issue and support for VSM is very lacking.
01-19-2015 05:52 AM
I do not know, as the original poster stopped providing feedback. I can certainly try to assist, but I'll need some information regarding your situation first. Namely, version of VSM you are trying to administer, and the browser version you are trying to use.
02-10-2015 07:34 AM
We are using VSM 6.3.1 with IE. 10.
The VSMS server which hosted the null name archive actually crashed and was rebuilt, but had to be rejoined using a different name as the null name archive prevents the deletion of the old VSMS server.
When trying to delete the null name archive I get the following:
02-11-2015 09:37 AM
I'm fairly certain that only IE 8 is supported on that version of VSM. This is likely what led to the original problem.
Unfortunately, it appears as though some VSOM records have ended up in a somewhat inconsistent state and the UI doesn't know how to process them properly. Chances are this will likely require some manual cleanup/manipulation of the VSOM mysql DB.
Unless you feel like some exploration/revengineering in mysql, my recommendation would be to open a Cisco TAC case and have them guide you in the cleanup of the DB.
Best of luck!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide