
-
Support November 9th, 2020 @ 9:00 am
Reposting answer provided to include missing elements in previous answer:
It might be a problem related to the TLS version of the host not being correct. First, check the installed version by running the following command:[Net.ServicePointManager]::SecurityProtocol
Setting TLS 1.2 is done by this command:
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12;
For more details, you can check these posts:
View Comment
https://powershell.org/forums/topic/is-it-possible-to-enable-tls-1-2-as-default-in-powershell/
https://johnlouros.com/blog/enabling-strong-cryptography-for-all-dot-net-applications
If the above is not working, check your certificates using this URL:
https://www.ssllabs.com/ssltest/analyze.html?d=YOURCRMURL
-
Documentation November 3rd, 2020 @ 1:35 pm
Hi again Dwight,
Sorry! It looks like our reply text was incomplete. The html message must have parsed out the commands we were trying to give you. I'll try to paste it here once more and if unsuccessful we will be sending you an email with additional information.
It might be a problem related to the TLS version of the host not being correct. First, check the installed version by running the following command:
[Net.ServicePointManager]::SecurityProtocol
Setting TLS 1.2 is done by this command:
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12;
For more details, you can check these posts:
https://powershell.org/forums/topic/is-it-possible-to-enable-tls-1-2-as-default-in-powershell/
https://johnlouros.com/blog/enabling-strong-cryptography-for-all-dot-net-applications
If the above is not working, check your certificates using this URL:
https://www.ssllabs.com/ssltest/analyze.html?d=YOURCRMURLAdditionally, is the sweetersync service running on a different system than the one on which SuiteCRM is running? Are they both running on TLS 1.2?
Thanks,
diligent team
View Comment
-
Support October 27th, 2020 @ 9:40 am
Hi Dwight,
It might be a problem related to the TLS version of the host not being correct. First, check the installed version by running the following command:
Setting TLS 1.2 is done by this command:
For more details, you can check these posts:
https://powershell.org/forums/topic/is-it-possible-to-enable-tls-1-2-as-default-in-powershell/
https://johnlouros.com/blog/enabling-strong-cryptography-for-all-dot-net-applications
If the above is not working, check your certificates using this URL:
https://www.ssllabs.com/ssltest/analyze.html?d=YOURCRMURL
We hope this helps, otherwise let us know and we'll be happy to continue the assistance.
Best,
View Comment
diligent team
-
Support September 17th, 2020 @ 10:23 am
Hello christopherkunz,
we will gladly revist your case whenever it suits you. Our offer for a webmeeting as communicated via e-mail still stands.
Thanks,
View Comment
diligent Team
-
Support September 17th, 2020 @ 10:08 am
Hello,
this issue was addressed and resolved via e-mail.Thanks,
View Comment
diligent Team
-
Support September 17th, 2020 @ 10:05 am
Hello FibreCRM,
as also communicated via E-Mail on the 14th of June 2019, you can always come back to us once you have time to tackle the issue!
Best regards,
View Comment
diligent Team
-
Support July 23rd, 2020 @ 9:32 am
Hello christopherkunz,
we presume this to be a server configuration error. Most likely the database user couldn’t create the needed data table (as the error we are seeing relates to non existing tables, which should have been created at the installation time). Try increasing your database user permissions to cover creation of new tables within the datbase SuiteCRM uses.
If that still does not work, you can reach out to us and send us the install logs at support@dtbc.eu
Thanks,
View Comment
diligent team
-
Support July 23rd, 2020 @ 6:55 am
Dear christopherkunz,
we will look into this and get back to you ASAP. We'll contact you here in case there are any questions from our side.Thanks,
View Comment
diligent team
-
Support July 22nd, 2020 @ 10:55 am
The client uses 7.10.22
View Comment
Thanks a lot for your quick response! Looking forward to an update.
-
Support July 22nd, 2020 @ 9:42 am
Hello again,
one of our client uses your Plugin in his productive environment now and we sadly have an issue with the roles.Our example user has no right to export, therefore he cannot use the bulk action to factory export any contact. The button for Suite2Excel, however, is available and functional for that user. Hence he can export contacts even though the role matrix states no rights to do so.
I attached screenshots for the role matrix, showing NONE for Contacts,
and for the list view showing no export in bulk action but the Suite2Excel button.
Clicking the latter will export the shown 8 contacts with all details.We already ran a role repair and quick repair. What did we miss here for it to work as described?
Thanks,
View Comment
diligent Team
-
Support June 17th, 2020 @ 9:01 am
Perfect! Thank you very much for the immediate reply.
View Comment
-
Support August 30th, 2019 @ 12:01 pm
Hi there,
any estimation on when a fix can be expected?
Kind regards.
View Comment
-
Support August 20th, 2019 @ 7:33 am
Hello,
thank you very much for your fast reaction and confirmation. We're looking forward to the results of the investigation.
Kind regards.
View Comment
-
Support May 22nd, 2019 @ 3:06 pm
Sure, we can help you setting it up through a remote session.
View Comment
We'll be contacting you shortly to arrange a meeting.
Thanks!
diligent
-
Support May 22nd, 2019 @ 2:44 pm
Hi Peter,
this is strange, as the manifest should be in there.
The SweeterSync zip you downloaded from the store is called "SweeterSync_3_0_68_complete.zip". Please, make sure that the zip folder you are trying to upload on the module loader is the one contained within the aforementioned. The folder you need to upload is called "SweeterSync_3_0_68.zip" (without complete in the name).
Let us know if this solves your issue!Best regards,
View Comment
diligent
-
Support May 21st, 2019 @ 9:56 am
Hello FibreCRM,
have you already put in the SweeterSync configuration the target domain as https://suite.mydomain?
If yes, please try also with http://suite.mydomain.
We'll be also contacting you in private to request some details on the case immediately.Thanks!
View Comment
diligent Team
diligent has not rated any add-ons.
diligent has not verified any add-ons.
diligent has not created any Wanted Add-ons.