Notifications
Clear all
Topic starter
Has anyone else seen this problem? our entire staff is seeing an error when they log in to CPS that says:
Faxcom API Error:
Error in CountFaxErrorsThread
Com Error Definition: Unkown error 0x800A04CE
you can click through it, but then another error harrases the user whenever they go to a different screen. the new error says "user-so-and-so is currently deleting fax status messages"
the user will be a random name of one of our staff who is doing nothing of the sort. Ususally rebooting the fax server solves this problem, but this time it is not!
Any insight would be appreciated. we have a ticket in with GE, but no response yet. we are running CPS 12.0.10 on a Citrix environment.
--------------------------------------------------------------------------------------------------------------------------
update 11-18-2015:
Thank you all for your responses! It looks like the error went away eventually overnight, but I'm sure we will be seeing it again at some point.
I will be sure to try the fixes suggested here, as well as contact Biscom to get to the bottom of what happened.
Thank you again for your awesome support! You guys make CHUG such an amazing resource!
Posted : November 17, 2015 12:28 pm
We had this recently. It was a corrupt location of care. Basically dig through the fax client to find the location that will not open, it will take a long time then error. Have to un-share the LOC in the fax client then rebuild it (with alot of help from our VAR). May check with them before going to deep.
Posted : November 17, 2015 1:02 pm
Here is what one of our technicians has used in the past. I do not know SQL myself so I cannot explain any of it, but you might find it helpful as a starting point.
*************
There can be a situation where the faxcom fax status table gets a loglock due to DTS or user activity. To identify and remove the lock use the following SQL:
Identify all locks that are not equal to 0 (or no lock)
select faxdeletelock from LOGLOCKS where FAXDELETELOCK != 0
This returns a PVID capture that PVID and run the following to remove
Example result: 1541507449050900
update loglocks set faxdeletelock = 0 where faxdeletelock = 1541507449050900
Posted : November 17, 2015 1:29 pm
Call Biscom support. They're usually more responsive than GE and can always fix things like this. Anne McCroskey is the expert.
Posted : November 18, 2015 3:14 am
i think jbell nailed it but just in case, go to the faxcom settings area in centricity under administration and make sure your faxcom server isn't greyed out and make sure the path is in there.
Posted : November 18, 2015 3:54 am
