We've been having a few problems with our system lately, so I had my MS partner come in to take a look.
The problems:
- A Transaction/AR oddity where a transaction had the wrong total (if you add up the items you get one number, RMS came up with a completely different number) and therefore AR was off.
- As part of a recent ILC standardization project, we had an unusual chain of events occur: first, somewhere along the line we ended up with two duplicate items with slightly different ILCs (for example: 1234XYZ and 1234XZ where 1234XYZ is the correct ILC). At some point, 1234XYZ was made inactive--I think that somebody didn't know we could merge duplicate items. During the ILC standardization, the active and incorrect ILC 1234XZ was changed to 1234XYZ. No 'ILCs must be unique' error--the duplicate ILCs were allowed (one active, one inactive). Subsequent WS250s apparently created multiples of this item at the store level. The HQ Item table shows two item IDs with the same ILC, one active and another inactive. The various Store Ops databases show varying numbers of Item IDs in their Item tables, several for each HQID, all with the same ILC.
So my partner takes a look, says "that's odd, let's see if MS can help" and submits a support request.
The formal MS reply? SBS 2003 Premium is not a supported server OS for RMS. Game over, thanks for playing.
I *know* that I have read here that several RMS resellers *actually recommend* SBS 2K3 Premium to their clients. Are you aware that if you ever need support from MS that you will need to upgrade to Windows Server 2003 standard?
Just FYI, Tom