When applying a templete in SoftPro Select, an Apply Template Failed error appears showing a couple Infinite loop detected errors. This can be caused by quite literally just about anything. It is coming from either a formula or Iron Python rule attempting to access a part of the file that doesn’t quite exist yet.
An interesting error occurred with SoftPro Select last week while rendering a document. The error was Document error, an error occurred while processing the document: Removal of token ‘SoftPro.Documents.Markup.Tokenizer.CommandToken failed. (more…)
The other day a user needed to be given a permission in SpAdmin on a Classic 15 system. It didn’t go so well. The permission showed as being applied but the user was still unable to do the task. Print Checks was the permission needed rights granted.
This was a contract customer, someone who pays me just for being around, so a solution needed to be found sooner than later. A dive into the PermissionsByUser table in the SoftPro Database found the problem. The Allow flag was set to False on the UserID for Program zero. I’m guessing Program zero is ProForm, one is ProTrust, two and three exist, but I don’t know enough to hazard a guess at this point. (more…)
With some of the recent releases of ProForm Classic, the Word merge macro file spwinmrg.dot is removed along with other unnecessary files from the SoftPro Share. For the most part it’s a welcome change as there were many files in the shared folder that were unnecessary and confusing to technical staff.
A problem comes in when attempting to add macros to normal.dot because, the macro files is now installed under the Client executable folder in the Program Files tree. (more…)
During an installation of Softpro Classic SQL it is possible to run into a SQL database check error that won’t let you continue.The Error is Unable to establish a connection to the SQL Server
In Version 15 HF2 of SoftPro Classic, Pro1099 on some systems likes to start up needing local machine Administrator access. Not all machines, but some of them. I have clients who for good reasons don’t want users to have Administrator access. That usually happens as more hands touch more desktops.
A client recently upgrading from Standard 12.2 to Classic 15 HF3 had some single sided transfers that needed cleaned up in ProTrust. They were in pretty good shape with 110 of them in a 10 year database. As they were cleaning up the error message Unable to match the selected transactions. Ledger locking failed started appearing.
