TAM in test environment 2

Andrew Carrick · November 17, 2011, 06:06:52 AM

Alice posted about this back in July but this is a slighlty different problem I think. We're getting error "failed to read licence info" when trying to open the test TAM. Anybody know how to overcome this? All files are a straight copy of live ones.

Jeff Zylstra · November 17, 2011, 09:55:18 AM

Have you the checked path and file and folder security and attributes to make sure that windows actually could "see" the file? It is possible that these things can get scrambled during the copy process, but still look normal when you check them in Windows. I've had to change and then change back security to "refresh" it before, which has worked for me. Just a thought.

Andrew Carrick · November 17, 2011, 09:56:48 AM

Thanks for the tip, any suggestions as to specific files and folders in particular?

Jeff Zylstra · November 17, 2011, 10:02:53 AM

Quote from: Andrew Carrick on November 17, 2011, 09:56:48 AM
Thanks for the tip, any suggestions as to specific files and folders in particular?

I would start with the Wintam folder, and then also check the Tam.Com file. I believe that there's also another file on the license disk, but I'm not sure about that. The problems that I've had have usually been with "inherited" rights on files and folders. It only takes one of two files that don't properly inherit rights to totally screw up a system.

Andrew Carrick · November 17, 2011, 10:05:49 AM

Thanks, have some Karma, more may follow.

Jeff Zylstra · November 17, 2011, 10:31:26 AM

Thanks. I need all the help I can get! Real or imagined!

Alice Mooney · November 17, 2011, 10:47:13 AM

Andrew - try going throught the license install process. Maybe it's not being recognized by the initial.tbl (think that's the one) or the tamglob.ini. I forget which one it looks at.
Run asupdate again after that.

Andrew Carrick · November 17, 2011, 10:49:48 AM

Thanks Alice we have checked those but good to post as others might need to know.

All hail the Jeff!

Andrew Carrick · November 18, 2011, 08:56:43 AM

We found this to be a combination of windows file permissions (granted full access to all files/users) and file paths, and making sure drive mapping was correct (i.e. file paths).

Jeff Zylstra · November 18, 2011, 10:10:20 AM

Glad you figured it out. You've earned yourself a beer. You have my permission to go to the pub right now and take care of that!

Andrew Carrick · November 18, 2011, 10:20:34 AM

Thank you, I'll send this to our MD and tell him where I am if he wants me....

Andrew Carrick · November 22, 2011, 09:04:45 AM

In this test environment, when we try a User Defined Report (Cash receipts) we get error message "POL_IDX not found", but the Cash receipts report runs OK.

I tried Reports Reindex, but get error 1705 which suggests a user is in reports, although none are. Any suggestions welcome!

Jeff Zylstra · November 22, 2011, 11:26:28 AM

Maybe run a reports unlock and a reports reindex?

Andrew Carrick · November 22, 2011, 11:27:59 AM

Yeah will probably give it a go tonight when all users are off. Cheers.

Jeff Zylstra · November 22, 2011, 11:32:08 AM

Quote from: Andrew Carrick on November 22, 2011, 11:27:59 AM
Yeah will probably give it a go tonight when all users are off. Cheers.

No need to if you don't want to, unless you have users actively running reports while you're reindexing. You should be able to run it with users in the system, and I think ours takes about 1 minute to run.