Hi All,

Our G/L has crashed 2 times in the last week, so we're thinking something with our setup is wrong.

An integrity check and rebuild is unable to solve the problems.

We think the latest crash was caused by someone going into a specific part of the GL while someone else was posting. The person who was posting received an error saying something to this effect.

Could it be file handles, multiuser issues or open files issues?

All of our users access Adagio on a central server.

I've ran the chksys utility and it comes up with 0 errors and 0 warnings. The R/W status is also OK on all Adagio directories.

We are using AL 8.1A.

Thanks!

Cam

Hi Cam,

Do you know the precise wording of the error? That would help narrow things down.

If one user was prevented from posting because another user was performing some other process, I would not expect the result to be a crash but rather a simple message, provided the network and workstations are set up correctly. What server version do you have and what are the Windows versions on the workstations?

File caching and oportunistic locking should be disabled on workstations. All users should use unique login IDs and run the same program files installed on the server.

Is the data integrity clean?

Why aren't you using Adagio Ledger V9.0B - you're on an upgrade plan for the module and the benefits are significant?

I'll wager a flakey network card is causing the problem.

Hi All,

I don't know the exact wording of the message - but got a few more details from the lady it happened to. She was posting a larger batch, so left her desk. When she returned a message was there that said the posting was not complete because someone else had done something in the GL.

There are actually only 4 people who use the GL. 3 of them use XP, and one just upgraded to Windows 7. I think i need to explain better about how we run Adagio. The Adagio programs are actually installed on a server (what we call the Citrix server), and everyone uses Citrix to remote into the server, where they run the Adagio modules. None of the Adagio modules reside on local machines - they are only installed in one place, the Citrix server.

Since the chksys came up clean and the R/W status was clean, does this not mean that file caching and opportunistic locking are disabled?

This server is running Microsoft Windows Server 2003, Standard Edition, Service Pack 2.

Also, how could it be a flakey network card if all the data and processing reside on the same server, and not on workstations?

Thanks!

We're not using 9.0B yet because it doesn't work with F9 financial reporter. As soon as I get my act together and find some time, I need to develop all of our statments with the Ledger financial reporter, and then upgrade.

OK. Don't forget to use the File | Import from ExcelDirect option in the financial reporter to speed the move from F9. It will load your Excel spreadsheet directly into the Financial Reporter, preserving all the formatting. You can probably easily convert the formulas to be compatible with those used in the financial reporter.

I'd have lost the bet on the network card given your hardware configuration.

Are you sure that the netowrk locking is correctly set up? Are your users seeing locking collisions if you try a specific one?

Can you convince people to write down the exact wording of messages and what they were doing so that we can provide better help? Our favourite tool is SnagIt to easily capture screenshots when things go wrong.

Is anyone working in Accpac Plus alongside Adagio?

Thanks for the help Andrew - how do I test the network locking and how do I try a specific collision?

Accpac Plus was never installed on the Citrix server, so it would now be impossible for someone to be using it alongside Adagio.

Thanks!

Try and edit the same account at the same time on different workstations. Correct set up of the locking will prevent that circumstance.

Hi Andrew,

We tried to both edit an account at the same time, and if one person is in the edit account, the other one could not get in.

We also tried to post, and while the posting was going on the other person tried to edit the account, and they were locked out as well.

It seems that just on a rare occasion someone manages to get into an area when it should be locked - does this make sense?

Maybe what we're lacking is a procedure saying that no one else can be in while certain other activities are going on?

Thanks for your help with this.

Cam

You'll be better off when you move to 9.0B.

In the interim, make sure people write down the exact error messages they get when the system appears to have crashed.