RightSignature Error “Document Limit Reached” (RS4)

The purpose of this message is to inform the user that they have crossed the threshold for the number of documents their license provides.

RightSignature 4 accounts provide 100 documents per month per user. A 5 user RightSignature 4 account will have a maximum monthly document quota of 500 documents.

An individual user is not capped at 100 documents; they can send more by clicking the “X” in the top right of the browser window to bypass the message, however as they continue to send more documents the remaining users on the account will no longer have their fair share of 100 documents each.

If you receive this error after verifying that you have sufficient licenses, attempt the same action in an alternate web browser. If the message still displays in the alternate browser, please reach out to support for assistance.

Related:

  • No Related Posts

Using REST API to delete a client

I need a solution

Hi. I need to find the clientid to delete a known client as part of an automated decommissioning workflow.

I’m finding that returning all of the clients from the server (https://localhost:8446/sepm/api/v1/computers?pageSize=100) to then search the JSON payload and grab the clientid seems really inefficient and takes a huge amount of time (I have over 2000 SEP clients)

Can anyone suggest a better way of doing this?

Thanks, 

-Matt

0

Related:

  • No Related Posts

Apache HTTP Server (32 bit) service reports high cpu usage

I need a solution

Hello,

We are experiencing Apache HTTP Server (32 bit) service high cpu usage [75% approx] which raises the overall CPU utilization to 100% constantly after upgrading SEPM 14.2RU1  Version: 14.2.3332.1000 on Windows 2016 Servers Virtual Machines. However, the physical machines are working fine.

The Virtual Machines configuration is – Windows Server 2016 @2.00GHz  – 6 processors, 32GB RAM. The previous SEPM version 14.2MP1 didn’t have this issue.

Appreciate your thoughts.

Thank you.

0

Related:

  • No Related Posts

“Time out reached while waiting for …. SepMasterService” error, causing virtual machine freezes?

I need a solution

i have a Windows Server 2012 virtual machine that will freeze up and require a full system restart every few days. Before the freeze up occurred,  errors in Event Viewer show “A time out (30000 milliseconds) was reached while waiting for a transaction response from the SepMasterService service.”

what is causing this error, and could it be resulting in a system freeze?

Could it also interfere with the operation of other programs on my machine? Because at other times, a web server program will cease working properly and will need to be restarted. The web server’s TCP port is seen as open, but any attempt to access the web page it services results in a blank screen. 

This series of errors appears to be the only troubleshooting clue in Event Viewer.

i saw a closed topic similar to this one posted last year  here: 

https://www.symantec.com/connect/forums/timeout-60000-milliseconds-waiting-transaction-response-sepmasterservice-service-0

although a tech support person from Symantec comments in the thread, the solution is not mentioned. Anyone else seen this issue and have a fix for it?

0

Related:

  • No Related Posts