Good day gentlemen,

I have been forced to grow a new terminal server and have everything pretty much done.

We have about 3 users setup and things are all going well apart from the fact that some of the profiles cannot print anything from Ledger.

Is says it is doing stuff but nothing happens..

Any ideas anyone?

Thank you and,

Cheers, JK

John:
Did you log into the Terminal Server as each user and run the Adagio Workstation installation for each? That process installs some Crystal Reports support files for each user. Are they able to print from other modules?

Hi Bruce,

Thank you for your reply.

Yes, I did exactly that.

I have now uninstalled the application using the control panel using the administrator account and have re-installed it.

I then raised the user's account to admin level and ran WKSetup for Ledger.

Same problem.

Any ideas on where to look are appreciated...

As always, thank you!

Solved - posted for others.

There is something with the Adagio installer which somehow creates this weirdness when running the workstation setup on a terminal server.

Our env:

1- organizational unit for terminal server users,
2- no admin privilge assigned.

Fix:

1- remove the problematic profile from the terminal server,
2- remove the user from the TS OU putting them back into the main OU,
3- add the admin right,
4- run WKSETUP on all modules,
5- restore right and OU...

Cheers, JK

Well good day to you all!

I have just added another user and low and behold even the process noted above does not allow the user to print.

What is going on with this software?

Too hard to tell from out here. Sounds like you have a rights issue.

No way, I have the user set up as domain admin in the main organizational unit.

By way of this email, Doug (Dickie) could you please give me a call - perhaps a session with you is in order at this time.

When I can't print from a Terminal Server session, I confirm that the Crystal folder is present at UserProfileName\Windows\Crystal. It should have the same content as \Windows\Crystal. I believe this is already considered with an Adagio install.

Thank you Bruce - this is the kind of information that really helps but unfortunately in my case it did not.

I wiped out the profile on the terminal server and then with the user as a domain adminstrator went through the WKSETUPs.

Adagio Ledger report printing: Unable to preview/print Batch listing, Trial Balance, Detail Listing (G/L listing) from Reports menu. When trying to preview/print, it shows “Initializing printer”, then “Printing Reports”, but no report displayed or printed.

I am able to preview/print Reports> General report > Chart of Accounts, Account Group, Company profiles etc...

How is that for weird?

John:
It appears to me that the ones not printing have in common that they first create temporary tables and then run Crystal against those temporary tables. The ones that work are simpler ones that work directly with the existing tables. Doug could give you a definitive answer when you speak with him. And, to give credit where credit is due, it was Bob who was responsible for the previous post!

Bruce - thank you for the correction and Bob, please accept my apologies along with my thanks.

Bruce - what you say makes good sense - any idea where these files are crearted?

The user's Windows temp directory.

Thank you sir Bates!

I have ensured r/w access to %TMP% & %TEMP% (both pointing to same place) .... and everything is as it should be.

I even added everyone as RW.. so, there is something else...

Anyone - are there registry keys that are created by WKSETUP that I could try deleting - ie" kill profile, clean reg keys and start over?

It's worth confirming the r/w access from a user's perspective. Log into as the user, jump to that location with %TEMP% as a run command, create a folder and a file within that folder. Then delete the file and the folder. All reports are copied to the temp folder and manipulated. Not just those creating work files. Bruce originally asked you if other Adagio apps are printing properly. If they are, then we can say it's a Ledger issue.

Hi Bob,

Thank you for your input.

I have verified all of the above and was able to create a folder in the %TMP% directory, create a file in it, add to the file, close the flle, open the file and verify the contents were saved, jumped up one notch to the newly created test folder and then deleted the folder.

No problems!

So, I went to another database that has more data and watched what happens in the temp folder.

Files are created and are added to and then, they were deleted and the preview never displays.

Sounds like a LoadLibrary() when going to Crystal problem to me...

Is there a log file somewhere that might tell us more?

Again, thank you!!!

Reviewing the results from \SOFTRAK\SYSTEM\chksys.exe will confirm your setup.

Again, have you tried a report from AR or AP?

Hi Bob,

AP - Print open payables which also uses a temp file previews no problem.
AR - checked all reports - they all print..

I ran chksys and everything is A-ok!

Cheers, JK

//-------------------------------------------------------------
Here are the results from chksys:
//-------------------------------------------------------------

======= Checking Special System Configurations ======

========== Checking 32-bit System Status ==========
--- OK ---

======= Checking Report Tables Configuration =======
*** NOTE: Report Tables drive is: [M:];
Override status for user [Charlie.Costello] is [N].

=============== Checking Products ==============
Adagio Invoices Status:
M:\qrasp\QRTQIW80.qrw
Date: [03/09/2009] OK.
M:\qrasp\QRTQIZ81.qrw
Date: [11/20/2008] OK.
M:\qrasp\QRTQIB81.qrw
Date: [03/10/2009] OK.
M:\qrasp\QRTSMW90.qrw
Date: [11/05/2008] OK.
M:\qrasp\QRTSMZ90.qrw
Date: [10/24/2008] OK.

Adagio Invoices Status:
M:\qrasp\QRTQIW90.qrw
Date: [08/25/2011] OK.
M:\qrasp\QRTQIZ90.qrw
Date: [01/13/2011] OK.
M:\qrasp\QRTQIB90.qrw
Date: [06/22/2011] OK.
M:\qrasp\QRTSMW90.qrw
Date: [11/05/2008] OK.
M:\qrasp\QRTSMZ90.qrw
Date: [10/24/2008] OK.

Adagio Ledger Status:
M:\qrasp\QRTALW90.qrw
Date: [05/31/2011] OK.
M:\qrasp\QRTALZ90.qrw
Date: [05/31/2011] OK.
M:\qrasp\QRTMCW80.qrw
Date: [08/12/2003] OK.
M:\qrasp\QRTSMZ90.qrw
Date: [10/24/2008] OK.

Adagio Payables Status:
M:\qrasp\QRTAPW68.qrw
Date: [08/01/2012] OK.
M:\qrasp\QRTAPZ80.qrw
Date: [03/28/2007] OK.
M:\qrasp\QRTAPB68.qrw
Date: [10/20/2009] OK.
M:\qrasp\QRTAPT68.qrw
Date: [12/27/2002] OK.
M:\qrasp\QRTAPJ68.qrw
Date: [09/13/2004] OK.

Adagio Receivables Status:
M:\qrasp\QRTARW90.qrw
Date: [06/09/2011] OK.
M:\qrasp\QRTARB90.qrw
Date: [12/16/2008] OK.
M:\qrasp\QRTARZ90.qrw
Date: [08/23/2010] OK.
M:\qrasp\QRTSMW90.qrw
Date: [11/05/2008] OK.
M:\qrasp\QRTSMZ90.qrw
Date: [10/24/2008] OK.


. . . . 0 Error(s) and 0 Warning(s) Reported.
================== Finished ===================


//-------------------------------------------------------------
Here is the lanpak status:
//-------------------------------------------------------------


== VERSION == TOTAL
Version 9.0E 10
Version 9.0D 0
Version 9.0C 0
Version 9.0B 0
Version 9.0A 0
Version 8.1 0
Version 6.8 0

==== List of actual Lanpak Versions: ====
Serial #: 1211114556: ** Unknown version **; Lanpaks: 10


//-------------------------------------------------------------
Here is R/W for standard Adagio folders:
//-------------------------------------------------------------

=== STATUS OF COMMON ADAGIO FOLDERS ===
C:\WINDOWS\system32 --- Read/Write Status is OK for this folder.
C:\WINDOWS\CRYSTAL --- Read/Write Status is OK for this folder.
M:\qrasp --- Read/Write Status is OK for this folder.
M:\SOFTRAK\system --- Read/Write Status is OK for this folder.
M:\SOFTRAK\dict --- Read/Write Status is OK for this folder.
C:\SOFTRAK\SYSTEM --- Read/Write Status is OK for this folder.

=== STATUS OF ADAGIO RECENTLY USED DATA FOLDERS ===
AP: k:\juker --- Read/Write Status is OK for this folder.
AP: k:\record --- Read/Write Status is OK for this folder.
AP: k:\sfi --- Read/Write Status is OK for this folder.
AP: k:\threec --- Read/Write Status is OK for this folder.
AP: k:\snl --- Read/Write Status is OK for this folder.
AP: k:\j & s --- Read/Write Status is OK for this folder.
AP: k:\false creek --- Read/Write Status is OK for this folder.
AP: k:\alltech --- Read/Write Status is OK for this folder.
AP: k:\0875521_bc_ltd --- Read/Write Status is OK for this folder.
AP: k:\cil --- Read/Write Status is OK for this folder.
AP: k:\itb_marine_projects --- Read/Write Status is OK for this folder.
AP: k:\canpac --- Read/Write Status is OK for this folder.
AP: k:\mss --- Read/Write Status is OK for this folder.
AP: k:\kemah --- Read/Write Status is OK for this folder.
AP: k:\gatleedm --- Read/Write Status is OK for this folder.
AP: c:\accpac_data\alltech --- ** Folder doesn't exist.
Ledger: k:\jade\jade08 --- Read/Write Status is OK for this folder.
Ledger: k:\record\record10 --- Read/Write Status is OK for this folder.
Ledger: k:\snl\itb07 --- Read/Write Status is OK for this folder.
Ledger: k:\sfi\sfi june 10 --- Read/Write Status is OK for this folder.
Ledger: k:\snl\itb09 --- Read/Write Status is OK for this folder.
Ledger: k:\snl\itb08 --- Read/Write Status is OK for this folder.
Ledger: k:\sfi\sfi june 09 --- Read/Write Status is OK for this folder.
Ledger: k:\false creek\fcbp10 --- Read/Write Status is OK for this folder.
Ledger: k:\snl\itb06 --- Read/Write Status is OK for this folder.
Ledger: k:\juker\juker 2009 --- Read/Write Status is OK for this folder.
Ledger: k:\snl\pay test 2010 - delete 2010.08.01 --- Read/Write Status is OK for this folder.
Ledger: k:\snl\pay test 2010 - delete 2010.06.01 --- ** Folder doesn't exist.
Ledger: k:\threec\threec10 --- Read/Write Status is OK for this folder.
Ledger: k:\record\record11 --- ** Folder doesn't exist.
Ledger: k:\snl\itb10 --- Read/Write Status is OK for this folder.
Ledger: k:\0875521_bc_ltd\samson 2011 --- Read/Write Status is OK for this folder.
Ledger: k:\cil\mes --- Read/Write Status is OK for this folder.
Ledger: k:\cil\mes\mes 2011 --- Read/Write Status is OK for this folder.
Ledger: k:\kemah\kemah11 --- Read/Write Status is OK for this folder.
Ledger: k:\cil\mes\mes 2011 new --- ** Folder doesn't exist.
Ledger: k:\cil\mes\mes 2010 --- Read/Write Status is OK for this folder.
Ledger: k:\cil\cil 2011 --- Read/Write Status is OK for this folder.
Ledger: k:\cil\cil 2010 --- Read/Write Status is OK for this folder.
Ledger: m:\softrak\ledger\samdata --- Read/Write Status is OK for this folder.
Ledger: k:\alltech\alltec11 --- Read/Write Status is OK for this folder.
Ledger: k:\alltech\alltec09 --- Read/Write Status is OK for this folder.
Ledger: k:\alltech\alltec10 --- Read/Write Status is OK for this folder.
Ledger: k:\snl\itb11 --- Read/Write Status is OK for this folder.
Ledger: k:\sfi\sfi dec 11 --- Read/Write Status is OK for this folder.
Ledger: k:\sfi\sfi june 08 --- Read/Write Status is OK for this folder.
Ledger: k:\snl\itb 12 b4 fa --- Read/Write Status is OK for this folder.
Ledger: k:\snl\itb 12 before fa reevaluation --- ** Folder doesn't exist.
Ledger: k:\canpac\canpac 2011 --- Read/Write Status is OK for this folder.
Ledger: k:\_canpac --- ** Folder doesn't exist.
Ledger: k:\itb_marine_projects\itb mp 2011 --- Read/Write Status is OK for this folder.
Ledger: k:\cil\cil-2009 --- Read/Write Status is OK for this folder.
Ledger: k:\snl\itb04 --- Read/Write Status is OK for this folder.
Ledger: k:\sfi\sfi june 11 --- Read/Write Status is OK for this folder.
Ledger: k:\cil\test --- Read/Write Status is OK for this folder.
Ledger: k:\record\record07 --- Read/Write Status is OK for this folder.
Ledger: k:\threec\threec11 march11 --- Read/Write Status is OK for this folder.
Ledger: k:\juker\juker 2011 --- Read/Write Status is OK for this folder.
Ledger: k:\rls --- Read/Write Status is OK for this folder.
Ledger: k:\fourc --- Read/Write Status is OK for this folder.
Ledger: k:\record\record06 --- Read/Write Status is OK for this folder.
Ledger: k:\record\record09 --- Read/Write Status is OK for this folder.
Ledger: k:\record\record08 --- Read/Write Status is OK for this folder.
Ledger: k:\record\record11 (june 11) --- Read/Write Status is OK for this folder.
Receivables: k:\junk --- ** Folder doesn't exist.

=== STATUS OF ADAGIO "EZTASKS" FOLDERS ===
m:\asp --- Read/Write Status is OK for this folder.

=== STATUS OF ADAGIO "CURRENCY" FOLDERS ===
m:\asp --- Read/Write Status is OK for this folder.

Thanks. That's all I can suggest. This information will be of use to Softrak. I think you need an experienced Adagio Consultant on site. Server setups are not my thing.

Hi John,

In the release notes and ReadMe help files for the Oct 17, 2011 service pack of Adagio Ledger 9.0D, this text is included in the Fixes section:

Ledger 9.0D was updated from version 7 to version 8.5 of the Crystal Reports print engine. When installing Adagio for use with Remote Desktop Services (Terminal Services in Windows Server 2008 and previous versions) this necessitated manually copying the crystal folder from the main windows folder to the windows under each user. For example, on Server 2003 you had to copy the crystal folder from C:\windows\ to C:\Documents and Settings\username\windows. This is no longer required. The install and workstation installs will do the copy. The Ledger program will also do the copy if possible, which will avoid the need to do a workstation install in some cases.

If you are not running this service pack but instead the original release of Adagio Ledger 9.0D from June 29, 2011, then try downloading and installing the service pack, log into the terminal server as the user(s), and re-run the workstation setup for the user(s). For each user in question, ensure that they can 'see' a \windows\crystal directory that is not empty. Perhaps compare the file contents to your own - it should not be that much different, if at all.

If this doesn't fix the problem, then you may have to resort to manually copying the C:\windows\crystal directory for each user that has a problem. Depending on your terminal services setup, the destination may be %PROFILEPATH%\windows\crystal, %HOMEBASE%\windows\crystal, or %USERPROFILE%\windows\crystal.

This problem has never affected either AR or AP, but it did affect BankRec.
--
Also to briefly explain reports that require temp files. For reports such as the GL detail listing or the AR Aged trial balance, the temporary file(s) are initially created in the data directory - this occurs while the 'creating work file' progress bar on the report goes from 0% to 100%. When the progress bar completes, the work file(s) get copied to the user's temp directory within a specific unique folder, depending on the report. EG, for the GL Detail listing, the folder name is GLLS#### where #### is some generated task number such as 0003, and the work file names are GLTRNTMI.dat and GLTRNTMR.dat.

Thank you for the information.

I noticed that after deleting the profile and running WKSETUP for the modules and logged in with administrstor rights the %ProfilePath%\windows\crystal folder was not created.

I tried running the report and it failed.
I copied the folder in and the report failed again.

What I have not tried is to copy the folder if not present before the failure occurs.

I will post back in a few minutes.

Again, thank you!!!!

No luck - that was my last guess.

How do we get this solved?

Do I call in our reseller Doug Dickie?

Thanks again for all your help!

I just created a new user with domain admin rights, copied the Windows\crystal folder in and voila - everything works...

Since I need to retain the user name I need to follow this up some more.

Are there any registry keys written by WKSETUP that I should delete from the terminal server that would belong to just the affected user...

I looked and saw sme stuff in HKEY_LOCAL_USER... - should I kill the Softrak key? will killing the Softrak key for this user make a mess of the other users?

Recap: I delete the profile but that does not seem to yeild the same result as what I get when creating a new profile...

This is WAY beyond the scope of this forum.

Sorry.

Thank you sir Bates.

I will engage Doug Dickie at once.

Regards, JK

Gentlemen,

Upon review of this case I have elected to not seek an at cost solution for what I believe is a vendor related issue.

We will abandon the profile and create another moving the Exchange store and everything required to move forward in this way - a workaround indeed but the burn rate on this issue is unacceptable.

To everyone that pinged up - thank you.

If I stumble into the solution I will ping up.

Again, thank you and,

Cheers, JK

Hi John:
Judging from your postings, I think you’re a reasonable man but in this case I don’t think it’s fair to describe your situation as a “vendor related issue”. Naturally, as a dealer, my viewpoint will be different from yours. But there are so many different operating environments: Windows XP, Vista, 7, 8 and server environments (Windows, Linux even some Novell) plus Terminal Services, Citrix and so on. There are certainly many successful Adagio implementations on Terminal Services. However there are sometimes going to be issues where support from an external, experienced dealer like Doug is necessary (there's my bias as adealer showing up). I also support another well-known accounting product and can say that there are even more frequent “challenges” with the operating environment there.

Having said that, I’m happy that you have a new plan of action in which you have confidence. It would be valuable to hear the results at the end.

Hi Bruce,

Thank you for your candid reply.

I agree that we view issues from different lenses however our environment is mature and well known and was not problematic until CR8.5 was implemented in the Ledger software.

I believe it is those changes that have me burning the midnight oil and as such I move the onus of responsiblity to the vendor.

Being a programmer from way back (C5.01 days) I fully understand the complexities and nuances and understand and agree that there are going to be issues to be addressed.

However, the fact is that support beyond the limits of this forum are on a fee basis forces my decision to not persue further and to look for alternatives.

I have already invested a substantial effort and being informed that the meter will be running to continue in this discovery makes me uncomfortable.

The problem should be reviewed, solved and posted for all those concerned.

Just my 2c...

Again, thank you all for posting up and,

Cheers, JK

Sorry John. This won't happen for the reasons that Bruce noted. We can only fix what we can replicate, and you yourself have said that printing is working for two of your users and not a third. Some technical issues require the on site presence of an expert.

Your unwillingness to compensate a reseller for their experience and education, both formal and informal, does your employer no service. Even Tiger Woods employs a coach.

Andrew,

I will let your responce stand for all to view.

Again, thank you to everyone who posted up including you!

Cheers, JK

Hi,

For what it's worth, we now have the same situation for a new user being setup on Terminal Server 2008 R2, that the GL Trial Balance and GL transaction Details reports will not print. This is not an isolated situation.

And we're going through the various options on user rights setup. Administrator prints fine but this particular new user cannot print the selected noted reports.

Will advise on our solution when we get there.

Brian

Hi Brian,

Both of those reports generate a work file in the C:\Windows\temp Folder (check TEMP= path in environment). Of course, it sounds like a rights issue, since the Administrator can print fine.

Hi Brian,

Check my comments on the 1st page of this thread. It solved my problem.

Updates on our current testing:

The current user in question is using a dumb terminal to connect directly to their terminal server. With this connection he cannot print GL trial balances or GL transaction details reports. Logging in as the system administrator to terminal services, these reports in Adagio GL print fine.

The same user, if logging in to another PC workstation (not a dumb terminal), as his same user and same rights, connects to their terminal server with a desktop icon. We have discovered with this connection logged in as the same user ID as before, he can print GL trial balances or GL transaction details reports without issues.

Going back to the previous direct connection on the dumb terminal, the selected reports do not print.

It seems deeper than a rights issue.

To resolve the immediate printing issue, the user is now using a different workstation until we can resolve.

Brian

Hi Brian,

At the different workstations, go to the CMD prompt and type SET . Make a note of the location of the TEMP/TMP variable:



Make sure the user has full rights in the paths that are defined. Also, make sure that you have verified the Folders and Folder contents from Bob's post on the first page of this thread.