Word merge time

tford

We are experiencing VERY long times to accomplish Word merge with this configuration:

AwareIM version 5.1 - build 1451
Word 2010
Windows server 2008 R2 (64 bit operating system)

It's taking about 30 seconds per instance to be merged when I use DISPLAY DOCUMENT ... MERGE INTO ONE.

Question 1) Is anyone else doing Word merge with build 1451 & could share their merge times?

When I did mail merge previously with AwareIM with much faster times, it was using Word 2003 and an older build of AwareIM on a different server. So now, I am trying to isolate which component is causing the increased times.

In this post, AwareIM stated they version 5.1 updated the Jacob DLL that is used to accomplish word mail merge:

aware_support

1) Please try the latest build first
2) For 64 bit Windows the jacob-1.15-M4-x64.dll should be used. Please delete the other one

c:\Windows\SysWOW64 folder is where the installation puts these files by default for the 64-bit system and it's probably OK - you don't need to copy it anywhere else.

Only one dll should be used and it should be the right one. Problem is that if other dll's are located in the Windows default dll folder, it's unpredictable which library Windows will load (at least, that's how I interpret the problem), so:

1) jacob.dll - is the old library and should be deleted from everywhere
2) jacob-1.15-M4-x64.dll should be used for 64-bit systems
3) jacob-1.15-M4-x86.dll should be used for 32-bit systems

aware_support

Also, if deleting 32-bit library doesn't help, try installing 64-bit Java - there should be a forum post somewhere how to do this. I am not sure if it has anything to do with the problem, but running 32-bit Java that comes with Aware IM by default with 64-bit OS can be a problem in theory for a sensitive area like this one.

tford

I just discovered the server is 64 bit, but Word installed on the server is 32 bit.

I also found this by Microsoft on that combination:
http://office.microsoft.com/en-us/word-help/choose-the-32-bit-or-64-bit-version-of-microsoft-office-HA010369476.aspx

Can you clarify whether your DLL instructions deal with the specs of Windows or the specs of Word.

aware_support

Not sure, actually. Maybe worth trying both.

tford

But only 1 should exist at a time, right?

aware_support

Yes

aware_support

Actually after double checking it turns out that the Jacob library is supposed to pick the correct dll automatically based on the platform, so both dlls should be present in the system folder.

tford

Ok, I will put both of them back into c:\Windows\SysWOW64

Is it Ok that they are also in: c:\AwareIM\Tomcat\shared\lib
or should these DLLs be deleted from this folder?

aware_support

It's OK

rocketman

Tom, Some times for comparison.

Server 2008 web edition
AwareIM V 5.2 (just updated)
Office 2007 on the server, OpenOffice on my laptop

IE7 DISPLAY DOCUMENT MERGE INTO ONE

8 seconds to the Open/Save dialog box (so thats the merge and download complete) plus another 7 seconds or OpenOffice to fire up.

Google Chrome 9 seconds to complete the download For once ie wins - just

It's a simple letter with address and opening salutation tag elements

All this over the internet, not LAN

tford

Rocketman,

Can you clarify:
1) Is your server is 32 bit or 64 bit?
2) Is your Word version 32 bit or 64 bit?

Thanks!

rocketman

server 2008 64 bit
Office 2007 - 32 bit
Java is the standard 32bjt shipped with AwareIM.

As per my other post. still can't get Word merge to work when runningnas a service

tford

Thanks Rocketman.

The only difference is we are running Office 2010 32 bit. Maybe I should try to find Office 2007 to see if that makes a difference. We are not running AwareIM as a service either.

IS ANYONE RUNNING OFFICE 2010 ON A SERVER SUCCESSFULLY?

tford

Finally got this solved!

It turned out to be Kaspersky anti-virus causing the huge slow down. NOT Office 2010 or any server settings.

We had tried disabling Kaspersky & still experienced very slow merge times. In a last ditch effort, we uninstalled Kaspersky & found that it solved our problem.

ninap

tom,

in our history - we had similar issues with 2007 Office

our solution was to create "Exceptions" on DLL's , System Folders or Applications so that the EPS (End Point Security) did not actively scan during the processes.

While this is working and tested with other EPS apps, we do not have any installations with Kaspersky.

But perhaps work a try

txs, nina 🙂