imanager seems to be a no-go

[Russ Oliver]

I'm running NW6 SP3. At some point in the distant past, I thought iManager
was working properly and I never really thought much about it. I never
really used it but I wanted to do so recently and discovered it wasn't
working. I poked around a bit and couldn't figure out what the problem was
so I decided to upgrade to 2.01, while also upgrading Tomcat to version 4.

So, I'm running iManager 2.01, Tomcat 4, Apache 1.3, NW6 SP3. iManager
still does not work at all. I've always been able to run the remote manager
and can get into iMonitor and the like, but iManager won't do a thing.
These are the addresses I've tried:
https://server/nps/iManager.html 404
http://server/iManager 404
https://server:2200/eMFrame/iManage.html Error 500 Internal Servlet
Error with a "NoSuchMethodError" and a list of java stuff

I've checked "java -show" and tomcat is listed as running, but I'm
questioning the level of running quality. With the limited amount of info
on troubleshooting iManager available, I just can't find anything that will
help. It may also be an Apache configuration I'm not sure about. Anyone up
to the task?

Thanks,
Russ Oliver
ti...@uwyo.edu
Systems Programmer
College of Engineering
University of Wyoming

[Timothy Leerhoff]

What about https://server:2200

Is port 2200 being listened to as seen in TCPCON?

Please check if the following ports are being listened to:

80
81
389
524
636
2200
2211
8008
8009
51080
51443
52080
52443

--
Timothy Leerhoff
Principal Consultant
Independant Experts
Novell Support Forums Sysop

[Timothy Leerhoff]

Also is you do a NVXADMDN then a NVXADMUP what errors do you see on the
server console AND on the logger screen

[Russ Oliver]

I think I got it working. I installed iManager 2.0.2 and managed to go to
https://server:51443/nps/iManager.html without any problems. I changed the
adminserv.conf in the apache configuration to reflect http://server/imanage
and when I restart that, I'm hoping that'll take effect.

In response to your questions, 81, 52080, and 52443 are NOT listed in
TCPCON. And your other message... When running nvxadmdn, it states that
MDBLIB is NOT loaded. No errors when running nvxadmnup. After doing that,
though, I still can't just put in http://server/imanage and get to imanager.
Here is the line I put in the virtualhost section of the adminserv.conf:
Redirect /iManage https://<server IP>:51443/nps/iManager.html

I'll know for certain Monday morning when I reboot the server, but for now,
it seems odd the redirect doensn't come up. Is there something else I have
to do to reset the reading of that config file?

Thanks for your help, it's very much appreciated.

Russ Oliver

College of Engineering
University of Wyoming

"Timothy Leerhoff" <tleer...@SPAMqwest.net> wrote in message
news:bI%Rb.2520$Wh....@prv-forum2.provo.novell.com...

> What about https://server:2200
>
> Is port 2200 being listened to as seen in TCPCON?
>
> Please check if the following ports are being listened to:
>
> 80

> 81*

> 389
> 524
> 636
> 2200
> 2211
> 8008
> 8009
> 51080
> 51443

> 52080*
> 52443*

[Timothy Leerhoff]

The urls are case sensitive. You had a cap in teh line posted and not
in the url you tried.

[Russ Oliver]

yeah, I'd tried that, too. I tried all variants that I have in the
adminserv.conf file, still nothing. Even so, I don't believe it's case
sensitive because netware isn't case sensitive. Putting in either
https://server:51443/nps/iManager.html or
https://server:51443/nps/imanager.html works just fine, and I do not have
two files by the same name.

Either way, adhering to the case sensitivity doesn't seem to make a
difference, I still get a 404 error.

Thanks,
Russ Oliver

[Joseph Moore [SysOp]]

Russ Oliver:

> Is there something else I have
> to do to reset the reading of that config file?
>

nvxadmdn
nvxadmup

should cause Apache to unload then reload :)

Joe Moore
Novell Support Connection Volunteer Sysop
http://just.fdisk-it.com
for an e-book on NetWare Enterprise Web Server,
see http://www.caledonia.net/nesadmin.html

NO EMAIL PLEASE!!!!!

[Russ Oliver]

yeah, I realize that, I just wanted to make sure there wasn't another step
that this didn't take care of.

I rebooted the server this morning and I still can't enter
http://<server>/iManage in a web browser to get to imanager. Any thoughts?

Thanks,

[Joseph Moore [SysOp]]

Russ Oliver:

> http://<server>/iManage
>

it is possible that you did the redirect wrong - what exactly did you
put in adminserv.conf?

[Russ Oliver]

> it is possible that you did the redirect wrong - what exactly did you
> put in adminserv.conf?

Well, I'd say it's entirely possible I did more than just the redirect
wrong. Apache isn't my strong suit, I must say. I listed this earlier, but
I'll go into more detail:

In the adminserv.conf, under the section:
<VirtualHost server:2200>

I entered the following three lines:
Redirect /iManage/ https://<ipaddress>:51443/nps/iManager.html
Redirect /iManage https://<ipaddress>:51443/nps/iManager.html
Redirect /iManager https://<ipaddress>:51443/nps/iManager.html

This was basically a modification from what was originally there. The
original lines had something to do with
https://<ipaddress>/eMFrame/iManage.html
The line immediately following these three is:
Include "SYS:/webapps/eMFrame/WEB-INF/eMFrame-apache.conf"

That was automatically put there at some point, not my doing. Am I missing
something from somewhere that I'm just not looking? Apache is loaded with
the following line from nvxadmup.ncf:
load apache -s -f sys:\apache\conf\adminserv.conf

Thanks for any help,