Hi Freddox,
First, I would like to explain that this issue must be caused by a Groove
BUG. In Groove V3.1, "Send to Groove" button may be not able to integrate in
Outlook. This is a known bug that is not going to be fixed until 4.0.
I think you can try the following steps to see whether we can resolve this
issue:
Step 1: Re-register the GrooveOnRamp.dll
====================================
Based on my further research, some of this kind of issue is caused by the
GrooveOnRamp.dll file is not registered. Therefore, please perform the
following steps to see whether we can resolve our issue in this way:
First, please perform a Search on the customer's computer to locate the
GrooveOnRamp.dll file. Record the effective path of the .dll file. Then,
perform the following steps:
1. Click Start -> Run...
2. Type "regsvr32 "the effective path of the file"" and click OK. (Without
the red quotation marks).
For example, on my computer, the file is in the following path: "C:\Program
Files\Groove networks\Groove\Bin\GrooveOnRamp.dll"
Therefore, I run the following command in the Run dialog box:
Regsvr32 "C:\Program Files\Groove networks\Groove\Bin\GrooveOnRamp.dll"
Can you re-register the dll file? What's the result? If this issue still
persists, please perform next step:
Step 3: Over install Groove to reset the button
======================================
Please try an over install of Groove from an administrative account of the
customer's computer and then a reboot in that administrative account. If your
company has your own Enterprise Management Server to manage Groove Accounts,
please contact your Groove Admin to send the installer to you. If your Groove
account is un-managed, please download the setup.exe file from the following
URL:
http://components.groove.net/Groove/DailyBuilds/latest/OCI/Setup.htm
Over installing will not remove any licenses nor will it remove any account
or space data. There is also no need to uninstall first. Upgrade to this
version of Groove Virtual Office and let me know if this resolves your
problem.
Restart the customer's computer and test this issue again. Is this issue
resolved?
Let me know the result~