by Mike.Sheen » Mon Feb 04, 2019 1:03 pm
That's odd.
When Jiwa.exe is first loaded, we read the JiwaConnections.xml from the users %appdata%\Roaming\Jiwa Financials\Jiwa 7\%version% folder.
If that file does not exist, we check to see if JiwaConnectionsTemplate.xml is present in the Program Files (x86)\Jiwa Financials\Jiwa 7 folder.
If that also does not exist, only then we will try creating a new JiwaConnections.xml and setting up a localdb database by copying JiwaDemo_Primary.mdf from the Program Files (x86)\Jiwa Financials\Jiwa 7\Data Files folder to the C:\Users\%username%\AppData\LocalMicrosoft\Microsoft SQL Server Local DB\Instances\mssqllocaldb folder.
The log entry you are seeing is the failure to copy to the C:\Users\%username%\AppData\LocalMicrosoft\Microsoft SQL Server Local DB\Instances\mssqllocaldb folder because the JiwaDemo_Primary.mdf file already there - but we check immediately before copying it to see if it is present - that's how we know whether to copy it or not.
It might be a permission issue on that file or folder - try manually copying the JiwaDemo_Primary.mdf file from the Program Files (x86)\Jiwa Financials\Jiwa 7\Data Files folder to the C:\Users\%username%\AppData\LocalMicrosoft\Microsoft SQL Server Local DB\Instances\mssqllocaldb folder - it might be enough to get it to skip the setting up of the localdb database.
Mike Sheen
Chief Software Engineer
Jiwa Financials
If I do answer your question to your satisfaction, please mark it as the post solving the topic so others with the same issue can readily identify the solution