Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

customlib file versions

Created: 11 Feb 2013 • Updated: 12 Feb 2013 | 2 comments
Lark's picture
This issue has been solved. See solution.

I've just noticed a small version difference between files in the \Symantec\Workflow\Shared\customlib folder on two ServiceDesk servers I am working with.

For example, Symantec.ServiceDesk.Cm.Core.dll is version 7.5.1317.1 on one server and 7.5.1361.1 on the other.  Many of the other similarly named files (Symantec.ServiceDesk....) have the same version differences.  They seem to be identical in size but have different dates.  The difference was noted when I moved a workflow package from one to another and was prompted to update one of the older files.

Both have 7.5.1 installed.

Is this normal?  If not how do I tell where the different versions came from?  I thought the two servers were in sync with versions and had the 7.5.1 CM patch.

Comments 2 CommentsJump to latest comment

gBBB's picture

Hi Lark,

Based on what you are seeing, I would guess that one server was originally installed with the ServiceDesk 7.5.0 installer (1317) and then patched with the 7.5.1 CM standalone patch, while the other server was originally installed with the 7.5.1 installer (1361). Is that correct?

This is simply the result of our build process. Every time we build ServiceDesk, all file versions get updated to the new build number - regardless of if they were changed or not (hence why you see those two files have the same file size). Thus when we updated the ServiceDesk 7.5.1 installer to automatically include the updated CM project, all other files were rev'd as well (to 1361).

 

You don't need to worry about anything. The only changes made between 1317 and 1361 were the updates contained in the CM patch. That patch only contains the updated CM project, and won't update any other projects or files. If that patch has been applied to the 1317 server, it it completely up-to-date functionally (despite the version number mismatch on the other files).

For any outside readers of this thread, please reference http://www.symantec.com/business/support/index?page=content&id=HOWTO83330 for more information.

 

Did that answer your question Lark?

SOLUTION
Lark's picture

Yes I think you're correct.  Now I think about it the SD server with 1361 versions has probably been rebuilt with code from an SMP server with the latest SD7.5.1 installed.  The 1317 SD server is based on an upgrade using the KB you referenced.

I've been rebuilding the first SD server a few times (marvelling at how much better that installer is compared to v7.1) to compare default config with our PoC environment.  As we have quite a few cases open with Symantec at the moment I'm very sensitive to code variations that could influence these.

Great answer thanks!