Hi Robert

Thank you for sending through the file though.

Kind regards

Elissa

Thanks Elissa, I've sent my machineconfig.xml to your support team.

I feel it may be an issue with the server components however, as when I run the licence configuration tool on the server itself it comes up with a 404 error again. However, as its a clientonly install, it should be touching the server components.

Many thanks.

Hi Robert

Thank you for your response.

It appears you have set up the licencing correctly, apologies for any confusion.

Could you please email the users config.xml file to mailto:support@scinaptic.com and I will be happy to review the file.

Kind regards

Elissa

Thanks Elissa, though I'm confused about "needs to be set to the Licence URL set on your SharePoint server. " Is there somewhere else I need to set the licence URL?

I've created the licence list, added the licence file, then set the Licence List URL on the clients to this new list location. Is this not all thats required?

Thanks for your help.

Hi Robert

There are no calls, however the licence on the client location on the client (OnePlaceMail Settings --> Licencing) needs to be set to the Licence URL set on your SharePoint server.

Please refer to the following KB: [Client Configuration] http://www.scinaptic.com/support/0068.html

Could you please check that the correct licence location has been set here?

If you have many users, the correct licence location can be set via a config_update.xml process.

Please let me know how you go.

Kind regards

Elissa

Thanks for getting back to me Elissa.

The problem is that, as mentioned above, we have set the ForceClientOnly flag to true. It was my understand from James' response that with v6.x the server install is no longer required.

Are there still calls to the server components even when this flag is set?

Thanks.

Hi Robert

Thanks for your inquiry.

Please find information regarding the error you are receiving in the following article: http://www.scinaptic.com/support/0024.html

Regarding your name appearing in the licence list - when users first use OnePlaceMail, their credentials will be automatically added to this list. This assists with tracking the number of licences used. You will not need to add their names here.

I hope this helps, and please do not hesitate to get in touch should you have further queries or issues.

Kind regards

Elissa

James,

One issue we're coming up with. When users save to SharePoint from desktop for example, and navigate to a folder, they are presented with this error:

"An error has occurred connecting to the license server."

"Error: The request failed with HTTP status 404: Not Found."

However, this works as for me.

I've also noticed that in the new licence list for v6.x, my username is in there along wih the licence file. Will we have to create a new entry for all users in this list?

Thanks.

James, thanks for all your help. I'll be in touch if there's anything else.

Great support all round from your company.

Regards,

Rob.

Yes, that will achieve the same thing. Keep in mind end user security to update this file in the program files location may be restricted... otherwise, this is the value the switch is setting. .

I've updated the machingconfig.xml to set the ForceClientOnly to true in the following folder:

C:\Program Files\Scinaptic\Scinaptic OnePlaceMail

Is this an ok solution?

Attachment uploading now works fine with this set.

Thanks.

One final question, is it possible to set the client version to "Client Only" post install?

Thanks.

Thanks James, looks like we're going to redeploy to the small test user group with the ForceClientOnly="true" switch. This makes the server component upgrade requirement moot.

On a side note, we upgraded to the new licence structure earlier in the year, but just upgrading the software now.

Thank you for all your assistance. Top support.

On SP2010 and SP2013, it offers the following:

- External Data Column support/BCS

- List Level Validation

- Formula validation on Columns (not to be confused with normal required column as this is support with the client only)

On Office 365 they are not applicable and on SP 2007 they are required.

note: If you install the R6.x client you won't need a license key for 30 days (the software is fully functional). In your case (given you have a legacy server component) you will need to install via the msi with the ForceClientOnly="true" switch, otherwise the client will want you to upgrade the server.

We're happy to talk about your specific environment etc... offline, but generally we recommend running in client only mode/without installing anything on the server. As this provide for simpler upgrades and same capabilities regardless of your servers being on-premise or in the cloud/Office 365.

Just fro clarity, if you didn't have the server component already installed you would not need to worry about the ForceClientOnly switch.

Thanks very much James.

I've emailed your support team, however this pretty much answers my questions.

Can you confirm what the 6.x server components offer? I will need to make a call on whether we bother having them installed.

Thanks.

Hi Robert,

The server component is only required if you're running SP 2007.  If you have SP 2010, 2013 or Office 365, you may like to consider deploying the 6.x client with the ForceClientOnly="true" switch - see:  http://www.scinaptic.com/support/0069.html .  With this switch, the OnePlaceMail will ignore the serve component.  After you've tested R6.x and deployed to all machines in this mode, you can simply remove the old server component as it's no longer required.

Note: You will require a new license key when upgrading to R6.x.  Assuming you have current support/maintenance, there is no cost as support/maintenance includes all minor/major upgrades.  Please complete the step in the following kb:  http://www.scinaptic.com/support/0068.html  to request a new license key. We recommend creating a new list in SharePoint/Office 365 for the 6.x key.

Note: when deploying OnePlaceMail as per the article:  http://www.scinaptic.com/support/0069.html  you can include a LicenseLocation switch for the new license list url.

Running a R6.x server with a 4.x client is not part of our test scripts.  So i cant confirm this would work. However, the intention is for the server to be backward compatible.

I hope you enjoy R6.6. 

Regards,
James