Insight Remote Support
1752809 Members
6151 Online
108789 Solutions
New Discussion юеВ

Re: invalid url in emails from ISEE

 
Rich Kloempken
Contributor

invalid url in emails from ISEE

I've installed ISEE 3.00.026 on 3 different servers. When an incident occurs, the emails I receive have badly formed urls that have either the literal "null" or the address "0.0.0.0" instead of the server name.

either this:

http://null:5060/swizzle/cmd/ui/takeMeThere?incidentId=null&vendorId=HP_Services

or this:

http://0.0.0.0:5060/swizzle/cmd/ui/takeMeThere?incidentId=1754967171.1@devsyb2&vendorId=HP_Services

Of course, these links don't work. Just wondering if anyone else has seen this behavior?


Thanks,

Paul DILorenzo
Fixing bugs only reveals larger bugs that were hidden by the current bug
3 REPLIES 3
Frauke Denker_1
New Member

Re: invalid url in emails from ISEE

Hello,
if there are several IP addresses assigned to one system, this problem occurs sometimes. I do not know which mechanism ISEE uses to select the IP addess for the emails. If you have a look at the link you will see the hostname, so if you just replace the 0.0.0.0 by the fully qualified hostname, the link will work.
I already asked for further information to understand the way the IP address is selected, but did not recieve an answer by now.
Regards
Frauke
Owen Campbell
Occasional Advisor

Re: invalid url in emails from ISEE

Hi Paul,

This is a known problem with the ISEE client 3.00 for when there are multiple IP's configured on a host. This is a problem with the ISEE software and will be resolved in later releases of the software.

As mentioned before, just replace the invalid IP address of 0.0.0.0 with the correct IP address of your server as the current work around.

Regards
Owen
Rich Kloempken
Contributor

Re: invalid url in emails from ISEE

Thanks very much for the replies. That will work only if I know which server is experiencing the incident. The ones with the 0.0.0.0 may or may not have the server name later in the url. The ones that come in with the word "null" give no indication of which server it is.

Thanks again,

Paul DiLorenzo
Fixing bugs only reveals larger bugs that were hidden by the current bug