Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Allison A]

We are having problems with ICE.TCP Pro 4.4 which is installed on a Windows 2000 machine.  What happens is that when we run Outlook 2003, and then synchronize the folders (this is a laptop in a docking station), then ICE.TCP will "break".   We can no longer connect to any server with ICE.TCP, in fact, the program appears to lock up when you run it.  Reboot does not clear.  Only a re-install will fix the problem, and you have to reboot before you can re-install.

One interesting aspect of this is that after ICE.TCP has been affected, we can still use Windows telnet to get to the remote server just fine, so it does not appear to be a problem with the network stack or any type of network connection.  It appears confined to ICE.TCP itself.

Any suggestions?  Unfortunately, it's the president of our company who is having this problem so we are under some pressure to get this resolved.

Allison Andrews
Unix Administrator
Epson Portland Inc.

[Bob]

We are having problems with ICE.TCP Pro 4.4 which is installed on a Windows 2000 machine.  What happens is that when we run Outlook 2003, and then synchronize the folders (this is a laptop in a docking station), then ICE.TCP will "break".   We can no longer connect to any server with ICE.TCP, in fact, the program appears to lock up when you run it.  Reboot does not clear.  Only a re-install will fix the problem, and you have to reboot before you can re-install.

One interesting aspect of this is that after ICE.TCP has been affected, we can still use Windows telnet to get to the remote server just fine, so it does not appear to be a problem with the network stack or any type of network connection.  It appears confined to ICE.TCP itself.

Any suggestions?  Unfortunately, it's the president of our company who is having this problem so we are under some pressure to get this resolved.

Allison Andrews
Unix Administrator
Epson Portland Inc.

If a reinstall of 4.4 makes it work again we can assume that the sync is overwritting some files that 4.4 needs. The most likely candidates are the icetcp.ini file in the windows system directory or one of the dll's that 4.4 uses. It seems unlikely that the sync would make any modificatiions to the registry or the 4.4 directory but it would be good to check the 4.4 install directory (usually c:\program files\j river\icetcp4) for files with recent dates (indicating a change).

While this depends on what version of 4.4 you are using, the list of dlls used in the current version are:

ADVAPI32.DLL
COMCTL32.DLL
GDI32.DLL
KERNEL32.DLL
MPR.DLL
MSVCRT.DLL
NTDLL.DLL
RPCRT4.DLL
USER32.DLL
WINSPOOL.DRV
WS2HELP.DLL
WS2_32.DLL
WSOCK32.DLL

You should check to see if that dates/size of any of these are changing between the time 4.4 is working and not working.

Let us know what you find and we can try to pin down the problem...