When installing a supported version of ibaAnalyzer on the same system as where ibaDatCoordinator is installed it should automatically detect. Make sure that during the installation of ibaAnalyzer/ibaDatCoordinator you have administrator rights on that server! 


- Is the error produced locally or could there be an issue with the network configuration? Check the accessibility of network directories. Try using the IP address rather than the PC name when accessing a network location.

- Try the configuration in a local environment.

- Check the ibaDatCo configuration, all files and fields correctly used?

- Is ibaDatCo automating a certain ibaAnalyzer task? Does it work when executing the task in ibaAnalyzer manually? 

If yes --> ibaDatCo configuration, permissions or additional plugins are causing the error.

If not --> Troubleshoot ibaAnalyzer (license available, OS compatibility (check dongle and version compatibility), report troubleshooting, extraction to db?) (tabblad te maken)


- Depending on the executed task, optimize the system recources and click "transfer ibaAnalyzer settings" and restart the ibaDatCo service.


- Error: "no momentary acces to *dat file"
--> are the *dat files used by another application?

--> does ibaDatCoordinator have acces permissions to the directory?

--> *dat files accesible by another application? 


- Try running the ibaDatCoordinator service under a specified account rather than the local account. One that  has read/write rights. This could solve permission problems. 


The user might have reading rights, but check if the user has writing rights as well on this remote location, ibaDatCoordinator also writes some information back into the dat-files to indicate they have been treated correctly.


FR: Windows > services > ibaDatCo > propriétés > connexion > 'Ce compte' (--> compte avec des droits d'administrateur), au lieu du compte système local.
EN: Windows > services > ibaDatCo > properties > log on > 'This account' (--> an account with administrator rights) instead of the 'local system account'.


- Is there a similar system that uses the same *dat files/directories/configuration/ibaAnalyzer .pdo that does not show this issue?

- When using the extraction task and the license would cause issues: is the license used via a dongle server/ibaLicenseService or directly in the system? The license could be used by another system or network issues could cause interruptions in the license availability.

- Try using a different task on the same files (.pdo, *dat files).


ibaDatCo DB extraction task. What the workflow looks like:

1.       Start with local data files

2.       Create an analysis file to do the database connection (see note below)

3.       Use ibaDatCoordinator to push local datafiles into DB according to analysis file’s setup

 

If it's not possible to create the necessary computed collumns, there are 3 possible reasons:
- You don't have sufficient database rights
- The name of your computed column contains illegal charachters (characters allowed by ibaPDA/Analyzer but not by the database, e.g. '=' or '(' or ')' )
- You haven't created the necessary tables yet


If the tables are created, make sure you have transaction enabled if they are supported by your database.



- Install ibaDatCo as a standalone executable

Stand-alone executable: ibaDatCo is installed as a separate program that does not have a service running in the Windows environment but rather a local process. This can be useful for troubleshooting. ibaDatCoordinator must be run for jobs to be executed.