Tried out 11.0.3.29 connector - CAUTION

[asd_itops]

I tried out the new connector on a test machine.... and every single time it errors out during the install:

Error Signature:
AppName: setup.exe
ModVer: 0.0.0.0
AppVer: 11.0.3.29
ModName: Unknown
Offset: 332e302e

This is the contents of the standard "Windows Error Report". Anyone else?

Windows 2003, fully patched, Outlook 2003, fully patched
Server is Scalix 11.0.2.1

[jaime.pinto]

Alright! 11.0.3 is out!!!!

Let's play a bit. Send in your notes, observations, experiences, etc.
Jaime

[jaime.pinto]

Scalix connector upgrade experience:
So far Thumbs up!

I hope this sequence of events will help some of you with Blackberry.

STEP 1) just upgrade the connector.
Server 11.0.2
Connector: 11.0.2 -> 11.0.3 upgrade
BBDM 4.1
Smartcache OFF (from before)
Stand-alone home system. No windows Domain.
ISP: broad-band, very fast.

1) Just an *upgrade* of the connector on the Windows client made the connector setup.exe crash at the end of the installation.
2) So I stopped the blackberry sync manager, removed any connector, rebooted the PC and installed the connector again, as a “fresh installâ€

[dougp23]

Nice post Jaime. I have yet to roll out the connector. But I also have a second Scalix box that I use as a test server, so I may try and use the connector and Outlook to that and see how it goes.

[florian]

Hi Jaime,

Thanks for the feedback also on my side and thanks for the exhaustive test notes; maybe we should hire you into our QA department as you seem to find a couple of things we didn't see....

Couple items/remarks:

Crash on install exit (Scalix Connect):
1. Did you start the Installer (setup.exe) right out of the "zip" folder, i.e. the virtual folder that you get for a zip in WinXP? If so, that's a known issue (see Release Notes). To avoid this crash, you must first extract setup.exe out of the folder (i.e. use WinZip or similar or drag&drop it out)
2. If that's not it, can you try to use the MSI-based installer? you get that by running setup.exe with the -e (or /e) switch from a Windows command line (sorry, just don't know which and too complex to try now) and should get an embedded MSI. Try that for Installation

Crash on exit (Outlook/Scalix Connect)
3. We've found a couple of causes and eliminated those, they should be very rare. However, we still have some work items open there and should have that ready for the next release. Tell us how it goes in the meantime.

BBDM Sync
4. I would be very interested to learn about the exact circumstances of this, it hasn't done that in our verification testing (the plugin patch was developed by Intellisync/Nokia), so maybe you can provide some more information about size of mailbox, types of items, etc., because I assume it must be related to help.
5. I doubt that Optimize for Mobile would have improved it, because what it does is to limit sync to a couple of more important folders, so if anything, BBDM would see more incomplete data sets.

All-in-all, I'm glad that the connector works better for you now - based on the issues we have identified and fixed, it should; we're much happier with it than before.

Cheers, great weekend,
Florian.

[swordfish]

I also installed the 11.0.3 connector against 11.0.1 server. First I removed the previous Outlook profile and uninstalled the connector. Then deleted the old scalix profile files. Created an MSI and installed from it. No crash at the end of the installation but anyway on this PC I never had a crash at the end of the install from MSI for any version of the 11.x.x connector. Only had crashes before running the install from the setup file. Outlook syncs fine. With the previous version of the 11.0.2.1 connector I had Outlook crash after the first I opened it with the connector. This time it didn't happen anymore. My smart cache is enabled. Have to play around a bit more and test on more PCs now.

[yuceli]

We also upgraded our Scalix Connector for Outlook (11.0.3.29) and all of our problems seem to go away (crash on exit, lost connection to server, not showing new mails, etc.). Thanks to all who contributed for this upgrade.

Yucel

[apatel]

We upgraded to 11.0.3.29 and we get random results with the "error" at the end of the connector install. Some get this, other didn't when using the exe. We didn't get any errors for the people using the msi for the upgrade, but this was done with a logon script, so it was installed before any other process had a chance to come online that might cause the exception.

So far, we are only 5 hours into the new connector, and initial feedback is good.

Thanks for the work you guys put into this!

Regards,
Anish

[William]

The issue of crashing on install of connector 11.0.3.29 occurs here, also a crash occurs after making a profile.

I uninstalled the Scalix 10 connector and removed the profile from outlook. I also renamed this folder to remove it from the equation:
C:\Documents and Settings\username\Local Settings\Application Data\Scalix
I then restarted and installed.
At the end of the install a crash occurs.

Here are the install crash details:

AppName: setup.exe AppVer: 11.0.3.29 ModName: setup.exe
ModVer: 11.0.3.29 Offset: 00004800







C:\DOCUME~1\username\LOCALS~1\Temp\c9ca_appcompat.txt

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="Setup.exe" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="Setup.exe" SIZE="11984952" CHECKSUM="0x8B3247A0" BIN_FILE_VERSION="11.0.3.29" BIN_PRODUCT_VERSION="11.0.3.29" PRODUCT_VERSION="11.0.3.29" FILE_DESCRIPTION="Scalix Connector for Outlook" COMPANY_NAME="Scalix Corporation" PRODUCT_NAME="Scalix Connector for Outlook" FILE_VERSION="11.0.3.29" ORIGINAL_FILENAME="MakeSFX.exe" INTERNAL_NAME="Scalix Connector for Outlook" LEGAL_COPYRIGHT="Copyright © 2005-2007 Scalix Corporation" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xB7178F" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="11.0.3.29" UPTO_BIN_PRODUCT_VERSION="11.0.3.29" LINK_DATE="04/14/2005 00:01:34" UPTO_LINK_DATE="04/14/2005 00:01:34" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="983552" CHECKSUM="0x4CE79457" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFF848" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:56:36" UPTO_LINK_DATE="08/04/2004 07:56:36" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

Here are the crash details that happens at the end of the profile creation process:








C:\DOCUME~1\username\LOCALS~1\Temp\an-error-file.txt

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="SYSTEM INFO" FILTER="GRABMI_FILTER_SYSTEM">
<MATCHING_FILE NAME="advapi32.dll" SIZE="616960" CHECKSUM="0x8E9BCF02" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="Advanced Windows 32 Base API" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="advapi32.dll" INTERNAL_NAME="advapi32.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xA0DE4" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:56:23" UPTO_LINK_DATE="08/04/2004 07:56:23" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="gdi32.dll" SIZE="278016" CHECKSUM="0xA35EEC2E" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="GDI Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="gdi32" INTERNAL_NAME="gdi32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x4B007" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:56:07" UPTO_LINK_DATE="08/04/2004 07:56:07" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="kernel32.dll" SIZE="983552" CHECKSUM="0x4CE79457" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFF848" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:56:36" UPTO_LINK_DATE="08/04/2004 07:56:36" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="ntdll.dll" SIZE="708096" CHECKSUM="0x9D20568" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="NT Layer DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="ntdll.dll" INTERNAL_NAME="ntdll.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xAF2F7" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:56:36" UPTO_LINK_DATE="08/04/2004 07:56:36" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="ole32.dll" SIZE="1281536" CHECKSUM="0x8DD3141B" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="Microsoft OLE for Windows" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="OLE32.DLL" INTERNAL_NAME="OLE32.DLL" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1441FE" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:57:38" UPTO_LINK_DATE="08/04/2004 07:57:38" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="oleaut32.dll" SIZE="553472" CHECKSUM="0x4155D7D" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" COMPANY_NAME="Microsoft Corporation" FILE_VERSION="5.1.2600.2180" INTERNAL_NAME="OLEAUT32.DLL" LEGAL_COPYRIGHT="Copyright © Microsoft Corp. 1993-2001." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x96957" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:57:39" UPTO_LINK_DATE="08/04/2004 07:57:39" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="shell32.dll" SIZE="8384000" CHECKSUM="0x42386D21" BIN_FILE_VERSION="6.0.2900.2180" BIN_PRODUCT_VERSION="6.0.2900.2180" PRODUCT_VERSION="6.00.2900.2180" FILE_DESCRIPTION="Windows Shell Common Dll" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.00.2900.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="SHELL32.DLL" INTERNAL_NAME="SHELL32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x80CC14" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="6.0.2900.2180" UPTO_BIN_PRODUCT_VERSION="6.0.2900.2180" LINK_DATE="08/04/2004 07:56:39" UPTO_LINK_DATE="08/04/2004 07:56:39" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="user32.dll" SIZE="577024" CHECKSUM="0xF5C0D45B" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="Windows XP USER API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="user32" INTERNAL_NAME="user32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x9CA60" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:56:40" UPTO_LINK_DATE="08/04/2004 07:56:40" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="wininet.dll" SIZE="656384" CHECKSUM="0xC19365D6" BIN_FILE_VERSION="6.0.2900.2180" BIN_PRODUCT_VERSION="6.0.2900.2180" PRODUCT_VERSION="6.00.2900.2180" FILE_DESCRIPTION="Internet Extensions for Win32" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.00.2900.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="wininet.dll" INTERNAL_NAME="wininet.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xA24BD" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="6.0.2900.2180" UPTO_BIN_PRODUCT_VERSION="6.0.2900.2180" LINK_DATE="08/04/2004 07:57:08" UPTO_LINK_DATE="08/04/2004 07:57:08" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="winsock.dll" SIZE="2864" CHECKSUM="0x73AE8088" BIN_FILE_VERSION="3.10.0.103" BIN_PRODUCT_VERSION="3.10.0.103" PRODUCT_VERSION="3.10" FILE_DESCRIPTION="Windows Socket 16-Bit DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows(TM) Operating System" FILE_VERSION="3.10" ORIGINAL_FILENAME="WINSOCK.DLL" INTERNAL_NAME="WINSOCK" LEGAL_COPYRIGHT="Copyright © Microsoft Corp. 1981-1996" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10001" VERFILETYPE="0x2" MODULE_TYPE="WIN16" S16BIT_DESCRIPTION="BSD Socket API for Windows" S16BIT_MODULE_NAME="WINSOCK" UPTO_BIN_FILE_VERSION="3.10.0.103" UPTO_BIN_PRODUCT_VERSION="3.10.0.103" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

I started Outlook and got an error about the Rules wizard not working :

Scalix Rules Wizard failed to load

Looking in the rules wizard I see no rules there, it is the Outlook Rules wizard. How do I get back my rules and the Scalix Rules Wizard?

and also an error about the reminder service not working occurs when Outlook is started up:

Cannot start the reminder service. Unable to show reminders. The connection to the the network server could not be made so the provider was not logged successfully

This error screen does not allow copy and pasting of the top content:


Server Version 11.0.1.11
Desktop OS XP SP2
Outlook version 2000

I now have a nice new icon in the right hand corner of the screen.


Upon using Outlook a little further the following error messages are abundant in all personal folders and previewing all emails.





This error popped up whilst clicking between personal folders.


And doubleing clicking an email to see it gets this message:



Additionally the Public folders seem to have been relocated to a root node in the outlook folderlist, unlike where they are normally situated in the 'Outlook Today' root node in the folder list.

So in all I will have to go back to the trusty version 10 of the connector after another wasted morning trying to get version 11 of the scalix connector working.


EDIT-------

http://bugzilla.scalix.com/show_bug.cgi?id=15360

For the time being it seems the issue is solved by removing the AVG Outlook Plugin part of the AVG software.

-------/EDIT

[swordfish]

William,

Create an msi installation file from the connector - setup /e, install from the msi file and see if you run into the same errors.

[William]

I tried what you suggest with 11.0.1 and 11.0.2 connectors, both of which did not have nearly this many problems, and yet those times it still ended in failure. So the chances of this being the solution are nil in my opinion. However I will have a try asap.

There has been no mention of fixes introduced to handle the crashing and other problems I encountered in 11.0.1/2.

[jaime.pinto]

So here is some feedback after one week using 11.0.3 connector:

A) At first I didn't realize we needed to unzip the connector twice to use it. Once I did it, there hasn't been any crashes after the install anymore.

B) I tried every combination possible, i.e., upgrade connector and BBDM, remove old connector install it again and upgrade the BBDM, remove the old BBDM and install it again and upgrade the connector, remove both and install both, in addition to having smartcache ON and OFF before this exercise plus removing/adding profile. I also added to the mix windows Domain, local/roaming profile.The result is always the same:
When smartcache was OFF before the upgrade and remains OFF after, any combination of the upgrade will always work 100%, i.e., no crash of the BBDM initially.
When smartcache is set ON with the new profile there is always a couple of crashes with the BBDM, but after a day or so that all goes way.

C) As far as some of the annoyances I listed in the post viewtopic.php?t=6833&highlight= things have improved substantially as well.
1) BLACKBERRY: 10 users and so far not a single report of choking during sync with BB.

2) OUTLOOK CRASHES ON QUIT: still happens, but rarely.

3) WINMAIL.DAT masking attachments or inline email threads: all fixed.

So I want to thank and congratulate the fellows at scalix for such a great job in such a short time. With the 11.0.3 release the connector for OL2003 reached acceptable levels of usage.

Jaime

[William]

William,

Create an msi installation file from the connector - setup /e, install from the msi file and see if you run into the same errors.

I encounter the same problems _exactly_ except there is no crash at the end of the connector install process.

[dougp23]

Just rolled it out to two test users.
So far so good.

Crash after install, but being windows, we're pretty use to crashes!

Looks good for mails, contacts, meeting invites, etc.

[Alik]

Strange!

6 PCs with 100% same hardware. winxp deployd with imaging software.

Same insallation method of scalix connector, 3 of them were crashed on the end of install and 3 were fine.

I thought Scalix wanted to kill this bug with the 11.03.?