MS-Word 2003 Add-In Login Problem

[marc1911]

I've succesfully installed the MS-Word 2003 plugin into my MS-Office 2003 (Dutch version). When after configuring it I try to start it, I'm getting a login dialog that seems to stuck in some kind of a code execution loop. I'm not able to enter any login name and password at that moment because the plugin behaves erratic and it seems that it wants to enter something by itself. Spooky!! Weird ha? This are the settings I used to configure the plugin:

Webclient URL: http://19x.1xx.xxx.115:8080/alfresco/
WebDAV URL: http://19x.1xx.xxx.115:8080/alfresco/webdav/
CIFS server: \\19x.1xx.xxx.114\

Authentication: <blank
Password: <blank>

Ofcourse I tried it also with a valid password username combination.
I use the latest version of Alfresco Community Edition v2.1.0 on OpenSuse 10.2, use the Dutch version of MS Office 2003 and downloaded alle the MS plugins from Sourfeforge (http://sourceforge.net/project/showfiles.php?group_id=143373) in the section "Office Integration".

Before I forget, I also use a proxyserver to get out on the internet and because the Alfresco logo is in the dialog I always need to enter my proxy account. Could there be something wrong with the plugin on this front or perhaps with the dutch version of Office?

[schneika]

I also have tried a fresh and clean V2.1.0_24-07-2007-Installation without success:

\\servername\alfresco

Cifsprobe is ok:

Tests starting…
PASS: destination folder accessible
INFO: Root path is \\servername\alfresco
PASS: FSCTL_ALFRESCO_PROBE result
INFO: authTicket= TICKET_86c2c6b7c6344c5631139a505e899fadddbf5d36
Tests complete.

With direct usage of the navigation-url from above authTicket-URL

http://servername:8080/alfresco/wcservice/office/myAlfresco?p=&e=doc&ticket=TICKET_86c2c6b7c6344c563...‍

i can get direct access to the addin-Servlet without error.

But the Office-Plugin itself fails with Endless-Loop.

Are there any fixes in the upcoming V2.1.1 CE?

[mikeh]

Hi,

Yes, as I said above, improvements have been made to the v2.1 Enterprise branch. I'm not exactly sure what our plans are for a v2.1.1 release, but I'll find out.

In the meantime, you could try using the client parts from the v2.1E release to see if your problem is solved.

Thanks,
Mike

[schneika]

Thanx for reply.
The V2.2dev-AddIn 29-7-2007 has the same error.
But where can i get the V2.1E-AddIn, from which download-Area? I see in the download-Area only the V2.0E ist available?

[mikeh]

Yes, the code hasn't been merged to HEAD from the v2.1 Enterprise branch yet. 2.1E is due to be released imminently - apologies,  thought it was available.

Did mapping a drive not work for you to fix this in the meantime?

Mike

[durianwool]

Hi,

Did this problem get fixed finally? I've upgraded to Alf2.1 and the Office add-in and very strangely, I didn't get the problem above but 2 of my colleagues do.

I am not using CIFS - just the http and webdev settings - and it all works fine, so it shouldn't be due to CIFS.


BR,

Durian

[mikeh]

Yes - it's fixed in versions after v2.1 community. That means v2.1 Enterprise or v2.9 Labs.

You can download just the the v2.9B client add-ins from SourceForge if you like. Additionally, if this isn't a critical system, you could also upgrade your Alfresco server to v2.9B which will also give you document tagging via the Office add-in.

Thanks,
Mike