Forums

Hi,

Can anyone tell me if the joob.ini is really supposed to be jade.ini in the system folder (i.e. c:\jade7\system\jade.ini) ?

Error I'm seeing in Visual Studio 2012 connecting to Jade 7.0 database is:
SetUp : JadeSoftware.Joob.Exceptions.JoobConfigurationFileNotFoundException : The specified or default JOOB INI file does not exist
JOM exception code = '125'


I'm testing some various non-prod 7.0 and 7.1 configurations with C#.

Thanks

Rob,

It will be looking for whatever file name you have specified as the ConfigFile in the ConnectionString setting for your app config.

The following page from the .Net developers guide may help provide some more info:
https://www.jadeworld.com/docs/jade-70/ ... config.htm

Cheers,
BeeJay.

Thanks, BeeJay.

The App.config has the following relevant section in the connectionString:
ConfigFile=C:\Jade7\system\Jade.ini;

I've verified that this file exists already. I'm thinking this could be a red herring as far as errors go.
It is bound to be a config issue though, as this solution is running on other devs PCs - which eliminates code as the culprit. I'll keep hunting.

I noticed that the backslashes used in paths were forward slashes in the example for connectionString but not for joob defaultConnection. Changing them as follows made no difference.

<connectionStrings>
<add name="myDefault" providerName="JadeSoftware.Joob.JoobConnection"
connectionString="DataSource=C:/Jade7/system;
ConfigFile=C:/Jade7/system/Jade.ini;
SingleUser=False;
Schema=ZZZZZ;
Application=YYYYY;
IntegratedSecurity=True" />
</connectionStrings>

*** SOLVED ***

So it turns out that the values in the App.config file were overwritten by an IoC (Inversion of Control) container.

By inspecting the Stack Trace further, it mentioned several links to code.
Clicking on those links takes you to the code in Visual Studio.
Place a break point in the code at those points.
Run your integration test in Debug.
Inspect the ACTUAL connection string will give you the full name and path of the INI file it really is looking for.
Ctrl-Shift F brings up the Global Search in Visual Studio and you can isolate the real culprit.

Hope this helps somebody else who strikes a similar issue.