Hi Cristian.

Thanks for your tip. This i printed in my Log file:

2009-01-08 09:35:31,227 5080 EPiServer.ShellTools FileSaveDialog: Starting wizard
2009-01-08 09:35:31,249 5080 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 09:35:31,249 5080 EPiServer.ShellTools ConnectionManager: No ticket could be established
2009-01-08 09:35:31,249 5080 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 09:35:31,250 5080 EPiServer.ShellTools ConnectionManager: No ticket could be established
2009-01-08 09:35:31,250 5080 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 09:35:31,250 5080 EPiServer.ShellTools ConnectionManager: No ticket could be established
2009-01-08 09:35:31,250 5080 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 09:35:31,250 5080 EPiServer.ShellTools ConnectionManager: No ticket could be established
2009-01-08 09:35:33,452 5080 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 09:36:12,108 5080 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 09:36:14,143 5080 EPiServer.ShellTools Progress: Vent litt, klargjør neste trinn i veiviseren ...
2009-01-08 09:36:14,145 5080 EPiServer.ShellTools Progress: Vent litt, klargjør neste trinn i veiviseren ...
2009-01-08 09:36:14,146 5080 EPiServer.ShellTools Progress: Vent litt, klargjør neste trinn i veiviseren ...
2009-01-08 09:36:14,146 5080 EPiServer.ShellTools Progress: Vent litt, klargjør neste trinn i veiviseren ...
2009-01-08 09:36:15,127 5080 EPiServer.ShellTools Progress: Vent litt, klargjør neste trinn i veiviseren ...
2009-01-08 09:36:43,795 5080 EPiServer.ShellTools Progress: Konverterer til EPiServer CMS-format
2009-01-08 09:36:44,485 5080 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 09:36:44,601 5080 EPiServer.ShellTools FileProcessor: Creating convert module
2009-01-08 09:36:44,602 5080 EPiServer.ShellTools DataManager: Creating module base on URL: {script:http://mysite.no/UI/OfficeIntegration/Components/EPiServer.Word.wsc}
2009-01-08 09:36:44,648 5080 EPiServer.ShellTools DataManager: Failed creating module based on URL {script:http://mysite.no/UI/OfficeIntegration/Components/EPiServer.Word.wsc} [0x800C0006]

Do you know what can be wrong?

BR, Tore Gjerdrum

It seems that MS Word fails load the conversion script. The error code you get is INET_E_OBJECT_NOT_FOUND.

Which response do you get if you try to download the script with your browser?

Hi Stefan.

I get "The page cannot be found". But the UI url works for edit and admin mode. And the file exists on disk in the UI/OfficeIntegration/components folder. But in the log it says Components with a capital C. Is is case sensitive? Or maybe it can be MIME types in the IIS?

 BR, Tore

Fist of all, if the site is upgraded from CMS 5 R1 it's probably a known issue. Go to the bug list http://world.episerver.com/en/Support/Bug-List/ and search for "upgrade", the bug in question is "#14708:   HTTP 404 error is reported when clicking the Help button after upgrade site from 5.1 SP2"

If it's not an upgraded site I'm not sure why you can't download the file, but chances are that the fix stated in the bug report still applies. Revise the <httpHandlers> section in the <location path="UI"> section and make sure that there's a wildcard mapping to EPiServer.Web.StaticFileHandler, otherwise there's no handler that will serve the script component.

Hi Stefan.

Just thought of the same isse my selv. When I check the web.config for an upgraded site, the Ursl are siteUrl="http://mysite.no/" uiUrl="http://mysite.no/UI/" utilUrl="http://mysite.no/Util/", but for an R2 site it are siteUrl="http://mysite.no/"
uiUrl="~/ui/" utilUrl="~/util/". I have upgraded the site from 5.1 SP3 to 5.2, so that has to be the issue.

Thanks for your help!

BR, Tore Gjerdrum

Hi agian Stefan.

I did the changes to web.config that as described in the bug, but now I get this error: can`t upload files to EPiServer CMS.

The log file looks like this:

2009-01-08 12:41:55,013 4584 EPiServer.ShellTools FileSaveDialog: Starting wizard
2009-01-08 12:41:55,020 4584 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 12:41:55,707 4584 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 12:41:55,707 4584 EPiServer.ShellTools ConnectionManager: No ticket could be established
2009-01-08 12:41:55,707 4584 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 12:41:56,229 4584 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 12:41:56,229 4584 EPiServer.ShellTools ConnectionManager: No ticket could be established
2009-01-08 12:41:57,432 4584 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 12:41:59,112 4584 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 12:42:01,151 4584 EPiServer.ShellTools Progress: Vent litt, klargjør neste trinn i veiviseren ...
2009-01-08 12:42:01,153 4584 EPiServer.ShellTools Progress: Vent litt, klargjør neste trinn i veiviseren ...
2009-01-08 12:42:01,154 4584 EPiServer.ShellTools Progress: Vent litt, klargjør neste trinn i veiviseren ...
2009-01-08 12:42:01,155 4584 EPiServer.ShellTools Progress: Vent litt, klargjør neste trinn i veiviseren ...
2009-01-08 12:42:06,580 4584 EPiServer.ShellTools Progress: Konverterer til EPiServer CMS-format
2009-01-08 12:42:07,114 4584 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 12:42:07,236 4584 EPiServer.ShellTools FileProcessor: Creating convert module
2009-01-08 12:42:07,236 4584 EPiServer.ShellTools DataManager: Creating module base on URL: {script:http://acta.epinova.no/customUI/OfficeIntegration/Components/EPiServer.Word.wsc}
2009-01-08 12:42:07,245 4584 EPiServer.ShellTools FileProcessor: Calling convert module
2009-01-08 12:42:07,245 4584 EPiServer.ShellTools ConvertScript: Entering Word Convertor (script file)
2009-01-08 12:42:08,379 4584 EPiServer.ShellTools ConvertScript: Leaving Word Convertor (script file)
2009-01-08 12:42:08,379 4584 EPiServer.ShellTools FileProcessor: Found and added file C:\Users\TORE~1.GJE\AppData\Local\Temp\Hei på deg din knall_docx\page.html
2009-01-08 12:42:08,380 4584 EPiServer.ShellTools Progress: Laster opp filer til EPiServer CMS
2009-01-08 12:42:08,380 4584 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 12:42:08,381 4584 EPiServer.ShellTools DataManager: Open a internet session
2009-01-08 12:42:08,381 4584 EPiServer.ShellTools DataManager: Open a internet connection to acta.epinova.no
2009-01-08 12:42:08,381 4584 EPiServer.ShellTools DataManager: Opening request to upload file page.html
2009-01-08 12:42:08,381 4584 EPiServer.ShellTools DataManager: Send Request
2009-01-08 12:42:08,388 4584 EPiServer.ShellTools DataManager: Upload to server returned status code: 302 

Any clue what I have to do now?

BR, Tore Gjerdrum

Getting a 302 response indicates a redirect. My guess is that you for some reason are getting redirected to the login page when trying to upload the document content.

I assume you've changed web.config according to the section "Enabling Office Integration in web.config" in the Office tech note http://world.episerver.com/en/Documentation/Items/Tech-Notes/EPiServer-CMS-5/EPiServer-CMS-5-R2/Microsoft-Office-Integration/ 

Can you check with Fiddler [http://www.fiddlertool.com/] where the redirect points to?

Hi Stefan.

I have enabled officeintegration in web.config.

The redirect point to http://mysite.no/UI/OfficeIntegration/HandleUpload.aspx?id=1001_4049&index=0&islastbits=1&filename=page.html.The EPiServerLog does not log anything interessting.

BR, Tore Gjerdrum

Is that the URL getting redirected, or are you getting redirected to that URL (in that case from which URL).

Continuing through the usual suspects before we dig any deeper; have you enabled "publish pages from Microsoft Office" from Permissions to functions in admin mode? You may have to enable "advanced upload of files" as well, but I'm not about that.

Hi again.

I have installed the MicrosoftOffice-add in and enabled it in functions in admin mode. I have also enabled my user for advanced upload, but I have not installed the client components. But do you need the client components to publish from office? It works fine on other sites on the same server(that is R2 by installation and not by upgrade) without the client components installed.

I don`t get redirected at all.I just get an errormessage in Word. The converting is now fine, but when the status bar in office goes to "Uploading files to EPiServer CMS", I get an errormessage stating "Can`t upload files to EPiServer CMS". And the last thing I see in Fiddler is a 302 to this url: http://mysite.no/UI/OfficeIntegration/HandleUpload.aspx?id=1004_4052&index=0&islastbits=1&filename=page.html.

And the Log.txt states this:

2009-01-08 16:28:16,472 6644 EPiServer.ShellTools FileSaveDialog: Starting wizard
2009-01-08 16:28:16,479 6644 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 16:28:16,526 6644 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 16:28:16,526 6644 EPiServer.ShellTools ConnectionManager: No ticket could be established
2009-01-08 16:28:16,526 6644 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 16:28:16,542 6644 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 16:28:16,542 6644 EPiServer.ShellTools ConnectionManager: No ticket could be established
2009-01-08 16:28:18,311 6644 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 16:28:19,570 6644 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 16:28:25,271 6644 EPiServer.ShellTools Progress: Konverterer til EPiServer CMS-format
2009-01-08 16:28:25,691 6644 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 16:28:25,717 6644 EPiServer.ShellTools FileProcessor: Creating convert module
2009-01-08 16:28:25,718 6644 EPiServer.ShellTools DataManager: Creating module base on URL: {script:http://acta.epinova.no/customUI/OfficeIntegration/Components/EPiServer.Word.wsc}
2009-01-08 16:28:25,722 6644 EPiServer.ShellTools FileProcessor: Calling convert module
2009-01-08 16:28:25,722 6644 EPiServer.ShellTools ConvertScript: Entering Word Convertor (script file)
2009-01-08 16:28:27,005 6644 EPiServer.ShellTools ConvertScript: Leaving Word Convertor (script file)
2009-01-08 16:28:27,005 6644 EPiServer.ShellTools FileProcessor: Found and added file C:\Users\TORE~1.GJE\AppData\Local\Temp\Hei på deg din knall_docx\page.html
2009-01-08 16:28:27,006 6644 EPiServer.ShellTools Progress: Laster opp filer til EPiServer CMS
2009-01-08 16:28:27,006 6644 EPiServer.ShellTools ConnectionManager: Loading ticket
2009-01-08 16:28:27,007 6644 EPiServer.ShellTools DataManager: Open a internet session
2009-01-08 16:28:27,007 6644 EPiServer.ShellTools DataManager: Open a internet connection to acta.epinova.no
2009-01-08 16:28:27,007 6644 EPiServer.ShellTools DataManager: Opening request to upload file page.html
2009-01-08 16:28:27,007 6644 EPiServer.ShellTools DataManager: Send Request
2009-01-08 16:28:27,017 6644 EPiServer.ShellTools DataManager: Upload to server returned status code: 302

BR, Tore

I'm a bit confused about the 302 response you're getting. The only reason for a 302 to occur, as I can see, is that you're getting redirected to the login page when trying to upload the files via HandleUpload.aspx.

The Office Integration is a bit tricky when it comes to forms authentication. Since forms authentication is based on a redirect to a html login form where credentials are entered and posted to the server it's not feasible to handle in the upload component. Instead the authentication is done by a web service which returns a forms cookie which the upload component uses when uploading the data.

Since HandleUpload.aspx checks permissions to functions and will use the standard authentication methods (redirect) if publish from office isn't enabled I wanted to make sure that this wasn't the problem.

Can you try to re-activate the site from the Office Add-In tab in edit mode. The activation sets a shared key in registry and in your profile in the database. It might be that the key hasn't survived the upgrade.

Hi Stefan.

I have now removed my user from the permissions to functions, disabled the office add in, uninstalled the office add in, restarted my computer, installed the office add in, activated the office add in, added my user to permissions to functions, created a new word document, but I still get the same error. Do you know where in the registry and where in the database the shared key is stored? Maybe I can try to delete them from there and try another time.

BR, Tore

Hi,

In the registry all registered sites are stored below:
HKEY_CURRENT_USER\Software\ElektroPost\EPiServer.ShellTools

In the database it's stored in the aspnet_Profile table.

/Stefan

Hi,

I have now deleted the key form the registry and the database. When I enabled the office add in, a key was created in the registry and in the database. But I still get the same error as before.

Now I am beginning to run out of ideas. Do you have any more tips I can try out?

BR, Tore

I'm running out of ideas as well. My suggestion is to compare the http traffic with a working site using Fiddler. Specifically the authentication cookies and the authentication with the web service.
I know there's been problems when using Web Services Enhancements on the site since the Office Add-In can't handle the additional soap headers and fails to decode the response.

/Stefan