ODBC Scheduled Agent Crash After Upgrading to Domino 14.0.x

Mindwatering Incorporated

Author: Tripp W Black

Created: 01/13 at 01:39 PM

 

Category:
Domino Server Issues Troubleshooting
Server Crashes

Issue:
ODBC call in Domino 14 in a scheduled agent may hang both the agent and that Agent Manager thread until the Domino server services are restarted. The hang occurs at the connection moment.


Cause:
The long used internally in LotusScript cannot contain the ODBC 64-bit pointers. See the session.UseDoubleAsPointer Designer help document.


Solution:
Note:
Credit to Christian Gravgaard for posting the issue and the notes.ini solution, which after a search shows two solutions (as of Domino 12.01)

Option 1:
Add the following entry to the server notes.ini:
LS64BITCCALLOUTPointerSupport=1

This will apply to all agents running on the server - all internal C pointers are stored as Doubles.

Option 2:
Starting with Domino 12.01, HCL added:
Call session.UseDoubleAsPointer=True

This performs the same function, but only increases the C pointers for this specific agent.

Note:
From the help document, if using the s.UseDoubleAsPointer on a local Notes client agent run, all agents afterwards will share the new setting. Set back to false at the end of the agent run.
Call session.UseDoubleAsPointer=False
Exit Sub




previous page

×