IE 7 beta 2 will cause OL/SC to crash.

[brwatters]

Are there any updates on this issue as we are dead in the water with any further use of Scalix 11 .. We fully understand this is a beta product and all of the caviots that go with using betas in production ..

That said some insight as to fixes and availabled to said fixes would be great .. I know one more beta appears to be ready to make it out the door and from what I have learned it could be this week ..

My reasons for asking is we are fighting some major issues with Outlook 2003 and the plugin

BRW

[jaga0]

Great Job in keeping up scalix: http://blog.myarchive.us/?p=558

[vlaurenz]

Are there any updates on this issue as we are dead in the water with any further use of Scalix 11 .. We fully understand this is a beta product and all of the caviots that go with using betas in production ..

That said some insight as to fixes and availabled to said fixes would be great .. I know one more beta appears to be ready to make it out the door and from what I have learned it could be this week ..

My reasons for asking is we are fighting some major issues with Outlook 2003 and the plugin

BRW

We do NOT understand since we are NOT using a BETA product and are paying for Scalix. This needs to be addressed immediately.

[brwatters]

>????

[vlaurenz]

>????

My post wasn't directed at you. I was merely reminding Scalix that this is an issue affecting paying users, BETA users, and community users.

[brwatters]

Got ya .. yes we have payed for this service as well .. so I am onboard with you there ..

BRW

[ScalixSupport]

The Scalix Connect 10.0 patch that fixes Bug 11319 (see the text below) is now available for download at:

http://www.scalix.com/files/scalix_conn ... .0.366.zip

You can use the Auto-Upgrade capabilities of Scalix Connect to automatically upgrade your users to this release. Please see the "Automatically Upgrading Scalix Connect for Outlook" section of the Scalix Installation Guide for details.

The Release Notes for Scalix 10.0 includes a list of Known Issues and Workarounds for Scalix Connect. These same Known Issues and Workarounds apply to this release, with the obvious exception that this release can be used with Microsoft Internet Explorer 7.

Thank you,
The Scalix Team


Bug 11319: With IE 7 loaded, running Outlook with the Scalix connector, if you create a meeting invitation and add others, when you hit Send, Outlook crashes. We have identified the likely root cause of this problem and are working diligently on a fix. Please stay tuned as we should have an update soon.

[vlaurenz]

The Scalix Connect 10.0 patch that fixes Bug 11319 (see the text below) is now available for download at:

http://www.scalix.com/files/scalix_conn ... .0.366.zip

You can use the Auto-Upgrade capabilities of Scalix Connect to automatically upgrade your users to this release. Please see the "Automatically Upgrading Scalix Connect for Outlook" section of the Scalix Installation Guide for details.

The Release Notes for Scalix 10.0 includes a list of Known Issues and Workarounds for Scalix Connect. These same Known Issues and Workarounds apply to this release, with the obvious exception that this release can be used with Microsoft Internet Explorer 7.

Thank you,
The Scalix Team


Bug 11319: With IE 7 loaded, running Outlook with the Scalix connector, if you create a meeting invitation and add others, when you hit Send, Outlook crashes. We have identified the likely root cause of this problem and are working diligently on a fix. Please stay tuned as we should have an update soon.

Thanks!

What process on the Scalix server should I be looking at to see the auto upgrade happen? I've never used mapi.cfg before.

[vlaurenz]

Is there a way to force the auto upgrade? I don't like that it prompts the user and asks if they want to upgrade.

[mephisto]

There is an article in the knowledgebase that talks about this. The upgrade should be automatically.

[vlaurenz]

There is an article in the knowledgebase that talks about this. The upgrade should be automatically.

From the Install Guide:

Automatically Upgrading Scalix Connect for Outlook
Once Scalix Connect is installed on the PC’s of your “Premiumâ€

[jaga0]

Thank you for making the patched connect client available, it does appear to fix the issue.

[Mouseclone]

Even in beta2 the 10.0.0.366 will work and stop Outlook from crashing.

[vlaurenz]

Scalix, please do something about these spam messages to the forums. I'm getting email notifications on topics I watch due to the spam...

[vlaurenz]

I'm having an issue that I can only attribute to the new plugin. For random events in Outlook, I seem to lose connectivity to the server. This usually seems to happen when I have an 'Untitled Message' window open. Is it possible that the new client is not playing well with MS Word?

See this snippet from fatal.log:

Code: Select all

SERIOUS ERROR           Remote Client (U/I Access    ) Tue Nov 14 15:16:16 2006
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 11214
Procedure trace follows:
  <- pc_sendmessage
  -> pc_recvmessage
  -> pc_recv_logical_block
  -> sck_raw_read
  <- sck_raw_read
  -> sck_raw_read
  <- sck_raw_read
  <- pc_recv_logical_block
  <- pc_recvmessage
  -> ual_SendMessage
  <- ual_SendMessage
  -> ual_RecvReply
  -> ual_DirEntry
  -> ual_GetUserCharSet
  <- ual_�
  -> ual_ConvDirEnt
Pid of logging process: 11214


SERIOUS ERROR           Remote Client (U/I Access    ) Tue Nov 14 15:16:16 2006
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x174f06]
/opt/scalix/lib/libom_er.so[0x1751d6]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x17537f]
/lib/tls/libpthread.so.0[0x418898]
/opt/scalix/lib/libom_ual.so(ual_ConvDirEntry+0x9b)[0x61d23f]
/opt/scalix/lib/libom_ual.so(ual_DirEntry+0x2fe)[0x61da54]
/opt/scalix/lib/libom_ual.so(ual_RecvReply+0xc8a)[0x649dc9]
/opt/scalix/lib/libom_ual.so(ual_ProcessCommands+0xcd)[0x654109]
/opt/scalix/bin/ual.remote[0x804dec9]
/lib/tls/libc.so.6(__libc_start_main+0xd3)[0x433de3]
/opt/scalix/bin/ual.remote[0x8049a5d]
Pid of logging process: 11214