When sending an invitation, there is no warning that the user (e-mail) already exist in the database. The user then gets an invitation, tries to register, and gets an error that the user name (email) is already in use. If he tries to access the site for which he was invited, he then gets an access denied message.
How can we avoid this issue? Is it a configuration issue or is it limitations on the software?
ExCM versions 1.0.9166.1 and later support existing user registration. The user can access the registration page in one of two ways: Anonymous, Logged In. When the user accesses the page anonymously there will be a link that says 'Register with Existing Account'. When the user clicks this link they will be asked to login before completing the registration. If the user navigates to the registration page while logged in they will be taken to an existing user registration page which can be completed with the existing account.
You can check your version number by navigating to Site Actions -> Delegation Settings -> Modify All Delegation Settings -> Delegation Status. In later version you can just navigate to /_layouts/SPSolutions/Delegation/DelegationStatus.aspx.
You can download the latest bits from the Software Add-Ons section of our site. Click the Try Now link.
Here are the upgrade instructions...
One more question regarding this upgrade.
Do we need to do anything about the license? Reinstall, upgrade, nothing at all?
Your existing license should work with the upgraded bits. No license actions should be required during the upgrade process.
No luck. During System Check I get "The Windows SharePoint Services Timer service is NOT started!"
I check the service and the service IS running. I have tried restarting the service and even restarting the server with the same result.
Any ideas or pointers on how to troubleshoot this will be really appreciated. The solution would be even better :)
The Configuration Wizard will automate the installation of the ExCM .wsp package. You can also perform a manual installation using STSADM.
During the manual installation you will add the .wsp package to your SharePoint solution store then deploy your package with Central Administration UI to your target web applications. If there is an issue with your timer service you will probably get a failure during the deployment step. If the manual installation goes well we can investigate your issue in more detail.
How do I extract the .wsp package from the .exe downlload? Or is there another way to get it?
I recently added and deployed several .wsp packages to this Farm without any issues.
In case it helps to know, we are using Windows 2008 64 Bit.
You can get the .wsp package by running the .exe file. This will fire up an installation menu, click Install Extranet Collaboration Manager. After the installation completes you can find the SPSolutions.SharePoint.Delegation.wsp file in 'C:\Program Files\SharePoint Solutions\Site Provisioning Assistant\Packages' directory. Our product should have no issues with 32-bit or 64-bit platforms.
Darn, I feel dumb.
After I ran the installation the upgrade went very well. I went back to the instructions to see what I was missing and it turns out that I missed the part that says "before you upgrade'; especially the part where it says "... perform the steps ...".
Thank you for your assistance a patience.