Hello all,

I'm experiencing an issue with Adagio I'm hoping someone can shed some light on. I've been going back and forth with the vendor but haven't made any real progress towards a solution.

Adagio Ledger has started throwing a "Adagio Ledger data was not found." error whenever we attempt to access information from our servers. This started suddenly and for a while was worked around by creating a backup of the file then putting that on our servers.

Discussions with our vendor have had her pointing towards a permissions issue, I have explored this possibility thoroughly and can rule it out. This is occurring in one single office which has an identical permission structure to 4 others that are running without issue.

If there's anymore information I can provide please let me know.

Further to this, I identified that when a backup is restored (extracted) to a folder the server...a "Ledger data not found" error happens when the dataset is attempted to be opened.

If the dataset is first extracted to a folder on the local machine, and opened on a local machine and then copied in full to the server, it does not appear to be an issue.

It has happened in multiple instances

What operating system are they running?
What do you mean by office? Is this a LAN environment with a shared mapped drive?
If so, can they see the mapped drive when they browse to the file from the login screen?
Are they navigating to the GLGLOB.xxx file and seeing it there to select? Or are they just using a remembered path to log in?

Sounds like the extracted zip is not writing all the files to the network drive. Or perhaps, the AV is quarantining some of the files?

This should be an easy problem to identify, since Ledger is just complaining that there is no GL data in the Folder it is being asked to open. GL data files begin GL* and should be viewable with Windows Explorer. It expects to find a basic set of files (the company profile and chart of accounts for example) when it opens.

Log in as the Server Admin.

First, check the properties on the Ledger shortcut to verify the Folder it is opening. The Folder name will follow the /d: parameter. Make sure that the extension is correct (after the /e: parameter).

Use Windows Explorer to open the Folder. Use Notepad to create a file "TEST.SAM" and save it (you'll need to change the file type to "All files", otherwise Notepad will save the file as "TEST.SAM.TXT".) Delete the file.

This should all work without error.

Now log is as the regular user on the workstation. Repeat the process above. It should also complete without error.

Report back your findings. I expect the User login to fail at some point in the process.

If you feel that the user has been set up identically, then delete the User profile from the server and set it up again. Repeat the above test.

Moe/Aurea:

It would be very helpful to have more details on the environment as Dan requested. One other question: Is both the Adagio programs and data on the same mapped drive?

When you open the restored database: are you browsing for the GLGLOB file?

I don't think it's the AV quarantining files as I would think that you would get a different error message.

If not a permissions issue then a hardware failure. Somehow the users rights or access to the map drive/shared folder are being interrupted. When you have this problem, using the same workstation open Windows Explorer and see if the drive letter for your Adagio data has a red X on it. Can you add/modify/delete a text file in the data folder?

We are running a combination of Windows 7 and Windows 10, our Server Environment is Windows Server 2012.
The issue is on a mapped drive within that office's LAN.
Adagio is being run locally(I believe, my experience with Adagio itself is limited and I was not present for the setup), not on the same drive as the files.

I can't speak to how users are navigating to files and am waiting on more information from the effected office.

I can rule out connectivity issues as many of the programs we use daily require access to the same share the Adagio files are located on. Our Adagio information is kept along with other data that is created, modified and deleted on a daily basis by users. Just to make sure, I also tested creating/modifying/deleting a file within an Adagio folder with no issues.

I also was not present when Adagio was installed, (they are not actually my client but are a PSR) but I believe they are running Adagio on the local workstation machines, only the data is stored on the server/shared drives

They are browsing to find the GLGLOB.XXX file, which is visible when they are browsing to it, but even though they can see it and choose it, it still says that there is no Adagio data created

They can also see the GLGLOB file if browsing through explorer to the folder the data was extracted to,

Moe/Aurea:

In my mind, this is clearly an environment issue otherwise others would be claiming the same problem.

So lets get back to basics: If it was working before and suddenly stopped working; what changed?

As Adagio gets more and more sophisticated, maybe it's looking for something that it's not finding. Like some file that is on the local machine, where Adagio is installed, but Adagio is looking for that file on the server, where the data is stored. Where do your ADSPROF.XXX (database file, XXX is the extension, edit with a text editor) point to?

Beyond that, this is a difficult problem to solve on the forum. We would be happy to offer our services to connect online and try to troubleshoot this problem.

Aurea:

Are you saying that the problem only occurs after data is restored?


I have seen cases where restored files are read-only, though I'm not certain if that would result in this error message.

BTW: From the limited descriptions available, it sounds like Adagio may have been installed incorrectly.

Yes, exactly Bruce, it appears that when it is extracted to a shared/server location it is extracting as read only

I think that is the issue, as when extracted on a local machine and then copied onto the shared location, the same issue (as far as I know) is not present