Error 534

[Support Team]

There are many hits throughout this Message Board for "Error 534." This is a short and sweet synopsis of why one would see such an error:

- You're running the report from a workstation/client PC and not the server ~ Your workstations require a Mapped Network Drive to the server's RWD folder. Once this is mapped, Liberty's RWDBUtil.exe must be told about this. You will change your client's RWDBUtil.exe "Application Base Path" to X:\ instead of C:\RWD\, where X:\ = the mapped drive letter you chose. Please refer to our Network Guide (http://files.rswhost.com/docs/nwguide.pdf) for further instructions.

- You're running a report that has a bug in it ~ While Liberty is AMAZING and POWERFUL software, it's possible to come across bugs (or as we like to refer to them, "programming opportunities"). :) As of 3.5c, there are NO KNOWN ISSUES in regard to Error 534 and reports. Make sure you're running the latest version of Liberty on ALL OF YOUR COMPUTERS (yep, not just the one you work at or the manager's computer; all of them).

- The update failed to install ~ We have no known issues in this department, but based on how nice Windows is treating you today or if you have a "custom" MS SQL installation that hasn't been configured properly (or is experiencing issues), you could be showing that you're on the latest version, yet the update wasn't applied 100%. We'll do everything we can to help determine if the issue is being caused by us (in which case, we can fix it) or if it's due to an issue on your system (in which case, we'll TRY to fix it, but we can't make any guarantees NOR can we continue troubleshooting this issue once it's determined to be an issue on your computer).

keywords: can't run reports, error 534, cannot run reports, dll, printjob

[Selections]

That's great we know what the problem might be, but now we need a solution.

I will need to use the address label feature next month, and I'd prefer not to go back to the old version of the software. Frankly, it frustrates me considerably that something that worked fine in the previous version does not work in the new version.

[Support Team]

Selections:

This article is a Knowledge Base article. It outlines the myriad reasons why one would see a 534 error. If you're getting a 534 error, we'd need to know a few details, as outlined in this Knowledge Base article. Details such as:

- Does this happen on your server, workstation or both?
- Did it ever work before?
- If you run the report with Criteria filters set to ALL vs. specific filters, do you get the error?

Please provide us with the details that are surrounding your error (again, are you on the server or workstation, does it run if set to All, etc.?)

Keep us posted!

[Selections]

Dean,

Thank you for your reply. To answer your questions:

1. We are running L4C from a single workstation.
2. It worked with the previous version. Never with this version.
3. It does not work with any type of filtering.

Any suggestions are appreciated.

Selections:

This article is a Knowledge Base article. It outlines the myriad reasons why one would see a 534 error. If you're getting a 534 error, we'd need to know a few details, as outlined in this Knowledge Base article. Details such as:

- Does this happen on your server, workstation or both?
- Did it ever work before?
- If you run the report with Criteria filters set to ALL vs. specific filters, do you get the error?

Please provide us with the details that are surrounding your error (again, are you on the server or workstation, does it run if set to All, etc.?)

Keep us posted!

[Jason Zander]

Which report are you attempting to run. As of 3.5d, there 2 known reports that would give the 534 error. These were the mailing label reports (both Avery and 2-across) but only when attempting to filter by consignor/purchase/both accounts. This is now fixed as of 3.6a.

Please let us know which report it is, and all filters you are including as well as the Liberty version you are on if it is not the report mentioned above.