We have recently begun experiencing a problem upon launch of ProComm, where we get various errors, all which reference our connection directory:
Error writing to File...
Error reading File...
Error allocating memory for...
The problem is that we are NOT USING the connection directory when launching ProComm under these circumstances -- our app is pulling phone # and other data directly from our database, creating and compiling a script with this info and then launching ProComm to run the script. We have no need to use the connection directory in this case.
This is a significant problem because it requires user intervention (OK'ing the error message) in order for ProComm to continue, and our automated process runs over night.
Is there a setting that controls how frequently ProComm attempts to read/write to the Connection Directory associated with a given computer? Or, does anyone know why this would be happening? We have been running ProComm successfully for almost 2 years without this problem. It only started recently.
Thanks.
Error writing to File...
Error reading File...
Error allocating memory for...
The problem is that we are NOT USING the connection directory when launching ProComm under these circumstances -- our app is pulling phone # and other data directly from our database, creating and compiling a script with this info and then launching ProComm to run the script. We have no need to use the connection directory in this case.
This is a significant problem because it requires user intervention (OK'ing the error message) in order for ProComm to continue, and our automated process runs over night.
Is there a setting that controls how frequently ProComm attempts to read/write to the Connection Directory associated with a given computer? Or, does anyone know why this would be happening? We have been running ProComm successfully for almost 2 years without this problem. It only started recently.
Thanks.