Worksite 8.2 SP1 + Office 2007

Hi all

I am currently testing Worksite 8.2 SP1 P4 (field test version) and have found the following integration problems with Office 2007:

1) Control + S shortcut does not bring up a Worksite Save dialog. You can only invoke it by going to the Ribbon --> Save. We dont want our users to be be able to save anything outside the Worksite system and hence this is a hole in the system for us.

2) In FileSite, I cannot view my worklist. I get the error: "The messaging interface has returned an unknown error. If the problem persists, restart Outlook.'

Has anyone experienced such problems in Worksite 8.2 SP1 and Office 2007?
And would you know of any workarounds for this?

Thanks

Find more posts tagged with

Comments

jny

Hi all

I am currently testing Worksite 8.2 SP1 P4 (field test version) and have found the following integration problems with Office 2007:

1) Control + S shortcut does not bring up a Worksite Save dialog. You can only invoke it by going to the Ribbon --> Save. We dont want our users to be be able to save anything outside the Worksite system and hence this is a hole in the system for us.

2) In FileSite, I cannot view my worklist. I get the error: "The messaging interface has returned an unknown error. If the problem persists, restart Outlook.'

Has anyone experienced such problems in Worksite 8.2 SP1 and Office 2007?
And would you know of any workarounds for this?

Thanks

1) The current IManO2k.Dot has to be modified to work in 2007 for hijacking the integrated keyboard keys. I think it will be released for 8.5.

2) You might want to check with WorkSite Tech Support.

dannyjak

Thank you. Here are steps from the vendor RE MS Word:

The keyboard shortcuts are assigned by the imanO2k.dot file in the the Word startup directory. If Ctrl-S or F12 do not function as expected in Word 2007, please try the following:

a) Confirm iManO2K.dot is installed in the correct location
It should be in Office12\STARTUP and check within Word Options|Advanced|File Locations that it is pointing to the correct startup folder

b) Reset the keyboard shortcuts
In Word, click on the Office button at the top left; select the Word Options button, then Customize in the left pane and the Customize button at the bottom. Then select Normal.dotm in the Save changes in drop down box and click Reset All.

The keyboard reset should be the solution to your problem, however we are finding that for a number of clients, once Word is restarted, the Ctrl-S and F12 keys stop working again. If this is the case, the workaround is to do execute the keyboard reset as above, but then to close Word, go in the \startup folder and remove the imanO2k.dot file before Word is launched again. From this point onwards, Ctrl-S and F12 should continue to display the Worksite dialog.

There is still the problem in EXCEL, and that OUTLOOK error though

jny

Thank you. Here are steps from the vendor RE MS Word:

The keyboard shortcuts are assigned by the imanO2k.dot file in the the Word startup directory. If Ctrl-S or F12 do not function as expected in Word 2007, please try the following:

a) Confirm iManO2K.dot is installed in the correct location
It should be in Office12\STARTUP and check within Word Options|Advanced|File Locations that it is pointing to the correct startup folder

b) Reset the keyboard shortcuts
In Word, click on the Office button at the top left; select the Word Options button, then Customize in the left pane and the Customize button at the bottom. Then select Normal.dotm in the Save changes in drop down box and click Reset All.

The keyboard reset should be the solution to your problem, however we are finding that for a number of clients, once Word is restarted, the Ctrl-S and F12 keys stop working again. If this is the case, the workaround is to do execute the keyboard reset as above, but then to close Word, go in the \startup folder and remove the imanO2k.dot file before Word is launched again. From this point onwards, Ctrl-S and F12 should continue to display the Worksite dialog.

There is still the problem in EXCEL, and that OUTLOOK error though

The manual, adhoc changes you described are not all-emcompassing to resolve the issue.

The code to the imano2k.dot needs to be rewritten to take on different Office Object Model methods to accomdodate 2007. This revised .dot will be slated for inclusion in the future 8.5 release.

dannyjak

I have also found the following inconsistencies:

- Word/Excel documents do not all check in until Word/Excel is closed. (e.g. when creating a new version, version 1 wont check in until you close version 2 and Excel completely)

- Even with the correct database filters installed for Office 2007 documents, invoking a “File  Save As” then selecting to save as a .xlsx file, the document is given an application of “EXCEL” instead of “EXCELX”. What this the means is that when opening the document, you get a type and extension mismatch error. Even actions such as exporting the document, do so with a .xls extension.

- With the database filters, 2007 documents are also not indexed (could be a server side issue, we are on Indexer 8.2 and Worksite Server 8.3)

jny

I have also found the following inconsistencies:

- Word/Excel documents do not all check in until Word/Excel is closed. (e.g. when creating a new version, version 1 wont check in until you close version 2 and Excel completely)

- Even with the correct database filters installed for Office 2007 documents, invoking a “File  Save As” then selecting to save as a .xlsx file, the document is given an application of “EXCEL” instead of “EXCELX”. What this the means is that when opening the document, you get a type and extension mismatch error. Even actions such as exporting the document, do so with a .xls extension.

- With the database filters, 2007 documents are also not indexed (could be a server side issue, we are on Indexer 8.2 and Worksite Server 8.3)

These appear to be usability issues - and possibly functionality problems - that should be assisted by Tech Support.

dannyjak

Dear all

I have found that the full release of 8.2 SP1 P4 has resolved all the issues mentioned.

The issue of Save As not saving as Excel 2007 documents was rectified by deleting the TypeMap.xml file so that Worksite would re-generate the latest ones (once the database filters have been added to the database)

Hope this helps