Resolving Common Integration Issues in Condor for Intergraph 2013
Integrating Condor workflow management with Intergraph 2013 suites often introduces compatibility, licensing, and data synchronization bottlenecks. Resolving these friction points requires systematic troubleshooting across database connections, API configurations, and user permissions. Below is a guide to diagnosing and fixing the most frequent integration errors. 1. Database Connection and Schema Mismatches
Intergraph 2013 relies heavily on precise Oracle or Microsoft SQL Server database schemas. Condor workflows will fail if data types or naming conventions diverge during runtime execution.
Symptom: “ORA-00942: table or view does not exist” or “SQL Server Error 208” during workflow execution.
Root Cause: Condor service accounts lack adequate schema permissions, or the Intergraph 2013 upgrade altered table prefixes. Resolution Steps:
Verify that the Condor database user has explicit SELECT, INSERT, UPDATE, and DELETE permissions on all Intergraph project schemas.
Check the db_owner or schema mapping settings within the Intergraph Administrator console.
Update the Condor connection string to explicitly define the schema provider (e.g., matching the exact Oracle TNSNAMES entry used by Intergraph). 2. Version-Specific API and DLL Conflicts
Condor triggers Intergraph commands using dynamic link libraries (DLLs) and COM interfaces. Intergraph 2013 introduced updated APIs that may conflict with legacy Condor custom plugins.
Symptom: “ActiveX component can’t create object” or “Class not registered” errors when Condor initiates an Intergraph process.
Root Cause: 32-bit versus 64-bit architecture mismatches, or unregistered Intergraph COM libraries on the Condor automation server. Resolution Steps:
Determine if your Condor instance is running in a 32-bit or 64-bit application pool. Intergraph 2013 server components require matching environment architectures.
Manually re-register the critical Intergraph DLLs using the command line:regsrv32.exe [Intergraph-Install-Path]\Bin[TargetLibrary].dll
If utilizing custom Condor scripts, recompile the source code against the official Intergraph 2013 SDK assemblies. 3. Coordinate System and Data Exchange Failures
When Condor automates spatial data extraction or bulk ingestion into Intergraph 2013 (such as G/Technology or GeoMedia), spatial reference identifier (SRID) mismatches can halt the process.
Symptom: Features pass through the workflow pipeline but fail to render, or throw coordinate transformation errors.
Root Cause: Condor’s XML or JSON payload structure does not explicitly pass the correct EPSG or custom Intergraph coordinate system code. Resolution Steps:
Open the Intergraph coordinate system file (.csf) assigned to your active project.
Validate that the Condor transformation parameters exactly match the projection, datum, and units defined in that .csf file.
Inject an explicit SRID validation step into your Condor workflow prior to executing the Intergraph data writer component. 4. Distributed Transaction Coordinator (DTC) Timeouts
Condor often manages long-running transactions that cross multiple servers. Intergraph 2013 handles complex asset relationships that require strict transactional integrity.
Symptom: Workflows time out, resulting in partially committed data or orphaned records in the Intergraph database.
Root Cause: Network latency or restrictive timeout thresholds inside Microsoft Distributed Transaction Coordinator (MSDTC). Resolution Steps:
Open dcomcnfg on both the Condor and Intergraph database servers.
Ensure “Network DTC Access”, “Allow Inbound”, and “Allow Outbound” are enabled under MSDTC security settings.
Increase the transaction timeout value within your Condor configuration file (web.config or app settings) to accommodate complex Intergraph geometric calculations. 5. Authentication and Security Token Failures
Intergraph 2013 utilizes strict role-based access control (RBAC). If Condor attempts to execute automated jobs under a generic system account, Intergraph security protocols will reject the request.
Symptom: “401 Unauthorized” or “Access Denied” logged within Condor job histories.
Root Cause: The Condor service account is not mapped to an active Intergraph seat license or domain group. Resolution Steps:
Add the Condor execution service account to the specific Windows Active Directory group controlling Intergraph access.
Ensure the account possesses valid privileges within the Intergraph Security Manager utility.
If your environment uses token-based authentication, verify that the token expiration window leaves enough time for heavy Condor batch processes to complete.
By isolating issues into database, API, spatial, transactional, or security categories, system administrators can quickly pinpoint where the handoff between Condor and Intergraph 2013 breaks down. Maintaining matched architecture profiles and explicit permissions across both platforms will prevent the vast majority of integration errors.
To help tailor this information to your specific technical environment, please consider the following next steps.
Do you need help diagnosing a specific error code or log message that you are currently encountering during integration?
Leave a Reply