DSML Provider, Status - Failed.

[element4749]

Was hoping someone could help me out. I had some bugs with One-X Portal, I decided to reinstall.

Prior to reinstall, I had no issues synchronizing the directories, the two IPO's that I have were communicating just fine with the DSML Provider.

After I reinstalled, now the provider can only see one of my IPO's. The IPO that the DSML provider cant communicate with is reachable through the diagnostics > IPO Connections.

I have left the default passwords on everything.

Any ideas?

 

[element4749]

tlpeter,

http clients only is off.

When I rebooted the IPO last night, the provider became available - it allowed me enough time to import the directories before failing again. So at least that is good. However I came in this morning, and it is back on failed.

Appreciate the assistance

 

[tlpeter]

I would try a default ipo and a couple of users with 1XP and see what happens.
It is done quick and dirty


When you pay peanuts, you get monkeys!

I'm not insane, my mother had me tested!

 

[element4749]

Haha, I wish it were that easy. I need another IPO to do that... I might just get on that though....

You know, normally I would be fine with this. I can deal with rebooting overnight and resynching just to get new users in and out. - It's just that some 1XP users are experiencing some oddities with 1XP, for example when there is a voicemail left for the user, its not sending the message to 1XP, but for everyone else it is just fine. So if I clear their profile, I would need to reboot a production system etc, etc.

 

[hairlessupportmonkey]

what happens if you configure LAN2 onto the same network and connect 1XP to that?

ACSS - SME

 

[element4749]

I will try to connect directly to LAN2. That was actually one of the test that I was going to do this morning. You think there might be something wrong on the NIC on the IPO?.. I am lost at this point. Ill let you know what I find.

 

[tlpeter]

you could be right.
I have seen bad NIC's on the IPO before so i would not be surprised


When you pay peanuts, you get monkeys!

I'm not insane, my mother had me tested!

 

[element4749]

Okay, so it is certainly not the NIC or any firewall issue.

I have narrowed it down to a problem with the IPO itself regarding the HTTP server.

It appears that the DSML service needs an HTTP connection with the IPO. When I check the 1XIPODirServiceRollingFile log in the tomcat logs, it is showing that the connection is failing to the IPO, when I reboot the IPO the HTTP becomes available for a short while and the provider can connect and synchronize the directories.

I am trying to pinpoint why the HTTP service would be failing on the IPO after a while. There is not much documentation on the HTTP server, or for that matter why the DSML service needs it.

To help clarify, after a reboot on BOTH of my IPO's the HTTP server becomes immediately available, and connectable. It stays up for a good while... long enough where I dont feel like watching it fail. When it does eventually fail, I am no longer able to even connect to Embedded File Management, I get a 503 error through manager.

The only thing that I can think of is a problem with the SD card, this morning I came in early to power it off and reseat the SD card on my one unit. However a part of me does not think that it is the SD card because it's happening on both of my IPO's. What are the chances it would happen to both?

Anyone know anything more about the HTTP server or why this might be happening?

Thanks,

 

[element4749]

Okay, so it is certainly not the NIC or any firewall issue.

I have narrowed it down to a problem with the IPO itself regarding the HTTP server.

It appears that the DSML service needs an HTTP connection with the IPO. When I check the 1XIPODirServiceRollingFile log in the tomcat logs, it is showing that the connection is failing to the IPO, when I reboot the IPO the HTTP becomes available for a short while and the provider can connect and synchronize the directories.

I am trying to pinpoint why the HTTP service would be failing on the IPO after a while. There is not much documentation on the HTTP server, or for that matter why the DSML service needs it.

To help clarify, after a reboot on BOTH of my IPO's the HTTP server becomes immediately available, and connectable. It stays up for a good while... long enough where I dont feel like watching it fail. When it does eventually fail, I am no longer able to even connect to Embedded File Management, I get a 503 error through manager.

The only thing that I can think of is a problem with the SD card, this morning I came in early to power it off and reseat the SD card on my one unit. However a part of me does not think that it is the SD card because it's happening on both of my IPO's. What are the chances it would happen to both?

Anyone know anything more about the HTTP server or why this might be happening?

Thanks,

 

[element4749]

bah, sorry for the double post.