Kyle_R:
There have been a few reports of a "TabBanner" error when trying to load Attachments on Service Desk Manager 12.7, after applying Cumulative Patch 2 RO68594.
.
.
.
"AHD04622:Undefined arguments Style supplied to PDM_MACRO TABBANNER."
Hello Everyone,
Root cause has been identified, and the good news is - you don't have to use the above workaround!
The root cause was not following the Post Installation Steps exactly.
This is the section which tripped up several sites:
------------------------------------------------------------------------
Patch RO68585 POST INSTALLATION STEPS
======================== IMPORTANT NOTE: ===============
Steps 1 through 5 are required steps. You need follow them to complete the installation.
.
.
.
d. Update the usp_pdmMacro and usp_pdmMacroParam tables by running
the following commands on the command prompt:
pdm_load -i -f data_USRD_2601_INSERT.dat
pdm_load -u -f data_USRD_2601_UPDATE.dat
------------------------------------------------------------------------
If the "-u" (update) is replaced by a "-i" (insert only), then the table is not updated as this row already exists. An error is thrown, but it is possible to miss this and continue on.
The end result is no working Attachments tab.
I can understand how this happened. My guess is that the user was going down a long list of data loads at the command line, using "up arrow" to replace the file name, and missed the variable change. It probably doesn't help that the patch notes are not lined up in this section, which may have made that easier to spot.
Take Away Tip
Use "Copy and Paste" when following Post Installation Steps.
Don't type them out or use "up arrow" if in doubt.
It's a good idea to make up your own "run sheet" in a plain text file, and adjust any changes to the commands that need to be issued, such as putting in your own server names.
If you script it in a batch file, perhaps with a "pause" command at key places, there is less chance in having a difference between the UAT/test environment and the production run.
Anyway, I'm pleased that there is not a problem with the deliverables in this area, and I still hope that this thread may help someone!
Note that the workaround is still valid if you did encounter this issue. *
Thanks, Kyle_R.
* EDIT: But following the above command also works and is recommended instead of the first workaround.
Also, for clarity, there is no problem with the ascii.dat deliverable.