Unsolved
This post is more than 5 years old
4 Posts
0
20385
December 11th, 2003 16:00
Client Initialization Error
I am a first time user of Network Manager. Below is the description of my problem:
After starting the client and logging to the client, I get the error:
(OWBOMAPIException) Could not create bomclient
Error running in Application
Followed by several pages of Trace information. At this point, the Lava login page closes and the DOS window remains open but does nothing.
My Setup:
I performed the server+client setup on my WinXP Pro. 2.66 P4 512 RAM 80 GB
I'm currently reinstalling the app, but am anticipating the same result. Any help would be appreciated.
Adam
No Events found!
adammichael
4 Posts
0
December 11th, 2003 20:00
After the reinstall I am still generating the same error. Any help is appreciated.
Adam
Kyon1
1 Rookie
•
6 Posts
0
December 12th, 2003 20:00
adammichael
4 Posts
0
December 15th, 2003 15:00
Yes, the monitor was green before I tried to access the login. I gave up on it since I can't get it to work. I was only trying the product as a recommendation from a S&P salesman. I only have unmanaged switched anyhow. He was thinking the product could possibly be used to monitor them. I would be interested in finding out if this product can do that though. If it can, I would be willing to give the install another shot. What do you think?
Adam
Andrew_Hicks1
2 Intern
•
169 Posts
0
December 15th, 2003 19:00
Since the unmanaged switches have no means of setting SNMP community names or hosts, they are not supported by the Dell OpenManage Network Manager product.
pphan
1 Message
0
January 23rd, 2004 15:00
Hello,
I have the same issue and the Network Manager system tray icon shows "appserver: ready" when I move the mouse over it. I'm running Windows 2000 pro on a P4 2.4GHz machine with 768MB of RAM and over 30GB free space.
I have Dell managed switches.
Thanks for any help.
Pierre
bcharamu
16 Posts
0
February 18th, 2004 00:00
You should copy the trace information and post it here.
That's why it was printed, to aid in the debugging of problems.
The trace may be included in a file in the {PRODUCT_INSTALL_FOLDER}/owareapps/redcell/logs folder,
e.g. client-admin-1070924744515.log. Basically, you can't connect to the database, but the reason why
is in the trace.
bcharamu
16 Posts
0
February 19th, 2004 01:00
A similar issue reported here was diagnosed via the database log files located at:
{INSTALL_DIR}\oware3rd\versant\VERSANT.LOG
and
{INSTALL_DIR}\oware3rd\versant\db\busdb\LOGFILE
In that case, they indicated that a database process failed to allocate heap space.
Please see the thread "Install Error Seeding Data" for information as to the location of the database logs, and post them here. You may be having a very similar problem. Also include information on the amount of RAM installed, size of the swap file, free disk space, and any memory-intensive programs that may be running on the box.
The simplest solution may be to ensure that you have around 1024MB of swap space.