Print

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

[crashpolo]

Hi Bob

But ICE is causing the problem we have monitored your software as closely as we can and when OUTLOOK and DLO all both in use ... ICE cannot connect to svchost.exe. I presume its how you call it and ICE then just crashes out.

Telnet works fine as does every other emulator but I have a 1000 users to work on so dont want to have to buy another emulator.

Im betting a 16bit version would work as it runs in its own memory space but I dont have a 16bit version to try.

Im quite happy to send screen shots if needed to try and prove what I say

[Bob]

It's simply possible that DLO is blocking a service that telnet doesn't use and the PLUS does.

The 16 bit version is on your CD. I suspect that they might work as well because the 16 bit tcp/ip stack in windows is totally separate from the 32 bit stack.

[crashpolo]

Hi

Can you list what services ICE requires and I can pass this on to Syamntec to see what they can find ...

Ill try and dig out the cd but if you can point me to a trial version of a 16 bit versionf or testing that would be ideal....

Can you see what im getting at here....if ICE and DLO are fighting then someone needs to fix it and I think altering ICE would be the easier option...plus I do think its ICE which is primarily at fault

If you could release a patch then a lot of customers would be happy including bruno !

[Bob]

Hi

Can you list what services ICE requires and I can pass this on to Syamntec to see what they can find ...

Ill try and dig out the cd but if you can point me to a trial version of a 16 bit version for testing that would be ideal....

Since the 16 bit version was removed from support in 2004, it's not available as a trialware version any more.
All of the CD's have the 32 bit version as well as the 16 bit version and even a dos version on them.

Can you see what im getting at here....if ICE and DLO are fighting then someone needs to fix it and I think altering ICE would be the easier option...plus I do think its ICE which is primarily at fault

If you could release a patch then a lot of customers would be happy including bruno !

A) Maybe ICE would be easier to change, maybe not.
B) Since this is the only time I've EVER seen anything like this and since we are NOT hooking the OS in any intrusive way I see little reason to believe that Ice is the most likely to be at fault.
C) I will look into the exact calls we are using with the TCP/IP stack and let you both know as soon as I can.

[crashpolo]

Hi

I can understand what you say but when your users are saying it is ICE casuing the problem and we are doing all the investigating maybe there is a little truth in it....im gonna run a process dump of the crashing deja32.exe and ill let you know what I find

[crashpolo]

ICE windbg.exe report

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.

*** wait with pending attach
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
ModLoad: 00400000 00496000   C:\Program Files\J River\ICETCPPLUS\deja32.exe
ModLoad: 7c900000 7c9af000   C:\WINDOWS\system32\ntdll.dll
ModLoad: 7c800000 7c8f6000   C:\WINDOWS\system32\kernel32.dll
ModLoad: 71ad0000 71ad9000   C:\WINDOWS\system32\WSOCK32.dll
ModLoad: 71ab0000 71ac7000   C:\WINDOWS\system32\WS2_32.dll
ModLoad: 77dd0000 77e6b000   C:\WINDOWS\system32\ADVAPI32.dll
ModLoad: 77e70000 77f02000   C:\WINDOWS\system32\RPCRT4.dll
ModLoad: 77fe0000 77ff1000   C:\WINDOWS\system32\Secur32.dll
ModLoad: 77c10000 77c68000   C:\WINDOWS\system32\msvcrt.dll
ModLoad: 71aa0000 71aa8000   C:\WINDOWS\system32\WS2HELP.dll
ModLoad: 7e410000 7e4a1000   C:\WINDOWS\system32\USER32.dll
ModLoad: 77f10000 77f59000   C:\WINDOWS\system32\GDI32.dll
ModLoad: 73000000 73026000   C:\WINDOWS\system32\WINSPOOL.DRV
ModLoad: 5d090000 5d12a000   C:\WINDOWS\system32\COMCTL32.dll
ModLoad: 76390000 763ad000   C:\WINDOWS\system32\IMM32.DLL
ModLoad: 629c0000 629c9000   C:\WINDOWS\system32\LPK.DLL
ModLoad: 74d90000 74dfb000   C:\WINDOWS\system32\USP10.dll
ModLoad: 10000000 10017000   C:\WINDOWS\system32\APSHook.dll
ModLoad: 5ad70000 5ada8000   C:\WINDOWS\system32\uxtheme.dll
ModLoad: 71a50000 71a8f000   C:\WINDOWS\system32\mswsock.dll
ModLoad: 662b0000 66308000   C:\WINDOWS\system32\hnetcfg.dll
ModLoad: 71a90000 71a98000   C:\WINDOWS\System32\wshtcpip.dll
ModLoad: 74720000 7476c000   C:\WINDOWS\system32\MSCTF.dll
ModLoad: 755c0000 755ee000   C:\WINDOWS\system32\msctfime.ime
ModLoad: 774e0000 7761d000   C:\WINDOWS\system32\ole32.dll
(3518.36c0): Break instruction exception - code 80000003 (first chance)
eax=7ffdf000 ebx=00000001 ecx=00000002 edx=00000003 esi=00000004 edi=00000005
eip=7c90120e esp=00a1ffcc ebp=00a1fff4 iopl=0         nv up ei pl zr na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000246
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\ntdll.dll -
ntdll!DbgBreakPoint:
7c90120e cc              int     3

[Bob]

Crash, I sent you an email.

The dbg dump isn't really useful to us. I have something you could try that might narrow the problem down.
It'd require downloading the PRO demo and running it with a TERMINAL SERVER demo key (on a normal XP machine) then using remote desktop to connect to that XP machine and see if you still have the connect problem.

Check my email first though, it might be easier to try that test.

[Bob]

I got the Backup exec 12 trialware.

What do I need to install to duplicate your environments?

The server on one machine and the remote option on the PC to test??

[crashpolo]

Windows Server 2003 fully up to date

a windows xp machine fully up to date

office 2003 sp3

[Bob]

Ok, we were able to reproduce this.
It looks like DLO is blocking some messages to outlook and when we send a font change message it's getting blocked because of the DLO/Outlook blocking problem. My supposition is that it is a bug in DLO.

We're coding a workaround.

[Bob]

After I registered and updated outlook the problem went away!

I see you are on version 11.8169.8172
I ran microsoft update to get to 11.8217.8202

Can you check this on your side as well??

[bbenhamou]

Hello,
For me on my desktop my Outlook version is 12.0.6300.5000.

Regards,

Bruno.

[Bob]

Bruno,
Is that the latest version of 12? The fixes could have been done to the different versions in parallel (I assume you've got office 2005 or something else newer than 2003).

[bbenhamou]

This is the Office 2007 version of Outlook. We have the same problem with Office 2003 on our company.

[Bob]

This is the Office 2007 version of Outlook. We have the same problem with Office 2003 on our company.

I understand that. I'm trying to verify that you have the latest version of each (2003 and 2007).
When I installed the lastest version of 2003 as indicated by the post above the problem vanished.

Please at least check the version of one of your non-working machines with 2003 on it to my version:
11.8217.8202

I have a workaround that should do the job but I'd rather not correct a Microsoft error if it's not necessary.