CDMS ISSUES AND TROUBLESHOOTING

Common Issues & Fixes

1. Internet Explorer (IE Mode) Error

CDMS not opening or showing compatibility error.

  1. Verify Edge settings are configured for IE Mode.
  2. Re-check installation steps.
  3. Open idg-cdms.lenovo.com.
  4. Reload in Internet Explorer Mode → Allow second option first, then first option.
  5. Restart browser and try again.

2. Local DB Issue / Object Reference Not Set to an Instance of an Object / Value cannot be null

  1. Open File Explorer → Documents.
  2. Enable Hidden Items.
  3. Locate or create folder CDMS DB.
  4. Ensure Local DB file (LocalDB_1.0.10.cdms or similar) is present.
    • If missing → Copy from backup or request IT/Admin.
  5. Close CDMS and Edge → Paste file into CDMS DB folder.
  6. If issue persists, temporarily disable antivirus from Windows Security → Virus & Threat Protection.
  7. Restart CDMS and re-test.

3. CDMS Installation on Desktop Directly Opens Login Page (No Registration Option)

When attempting to install CDMS on a Desktop system, the portal sometimes skips the registration page and directly opens the login page. This occurs because the Desktop does not have a valid Serial Number or Baseboard ID, which CDMS requires as a unique identifier.

Possible Reasons:

  1. Manufacturer Did Not Set Serial Number – Some OEMs ship systems without BIOS/Baseboard serial information, showing values like “To be filled by O.E.M” or blank.
  2. Motherboard Replacement – If the motherboard was replaced (often in local service centers), the serial number may not be updated in BIOS.
  3. CDMS Compatibility Limitation – CDMS does not support Desktop systems, only laptops running Windows 10 or 11 with valid BIOS details.

Resolution / Solution Steps:

  1. Inform the partner that CDMS requires a valid serial number or baseboard ID for registration.
  2. Verify system serial number using CMD/PowerShell commands or the CDMS Utility Tool.
  3. If the result is blank or “To be filled by O.E.M”:
  4. Explain that registration is not possible without a valid serial number.
  5. Advise the partner to arrange a laptop system instead of a desktop.
  6. Document the issue in ticketing system under “Installation Issue – Serial Number Missing”.

Note

  1. Always confirm with the partner whether they are using a Laptop or Desktop before starting installation.
  2. Clearly communicate that CDMS is only supported on Laptops with Windows 10/11.

CDMS - Partner User ID Recovery

Method 1: Using CDMS Utility Tool

  1. Connect with the partner.
  2. Open CDMS link in Microsoft Edge: https://idg-cdms.lenovo.com.
  3. Click the three dots (⋯) → Default Browser → Click Add.
  4. Paste and run the CDMS Utility Link: ➝ https://idg-cdms.lenovo.com/CDMS_UTILLITY/CDMS_UTILITY.xbap
  5. Click Get System Info.
  6. If Baseboard Serial Number is displayed: o Copy the serial number. o Login to CDMS portal from employee system. o Paste the serial number in Search Bar. o If valid, User ID details will appear.
  7. Copy the User ID and enter it in Utility Link → Forgot Password section.
  8. Re-enter the User ID for verification and proceed with password reset.

Method 2: Using BIOS/PowerShell Commands

  1. Connect with partner.
  2. Open Command Prompt (CMD) and run:
  3. WMIC BIOS GET SERIALNUMBER
  4. (Ensure correct spacing to avoid errors.)
  5. Copy the displayed serial number.
  6. Login to CDMS portal from employee system.
  7. Paste the serial number in Search Bar to retrieve User ID.
  8. If using Windows 10/11 (WMIC deprecated), use PowerShell command instead:
  9. Get-WmiObject -Class Win32_BIOS | Select-Object SerialNumber or Get-CimInstance -ClassName Win32_BIOS | Select-Object SerialNumber

Note

  • If serial number is not found, possible reasons include:
    1. Unsupported Device – CDMS only works on Windows 10/11 laptops (not desktops).
    2. Manufacturer Limitation – Some manufacturers do not set BIOS/Baseboard serial number (system shows “To be filled by O.E.M” or blank).
    3. Motherboard Replacement – If replaced at service centers, BIOS serial may not be updated.
  • Action in such cases:
    1. Show the evidence (blank/OEM serial) to the partner.
    2. Explain that without a valid serial number, CDMS cannot be installed.
    3. Request the partner to arrange another supported laptop system.

CDMS User Management Issues

Updating Partner Email ID

  1. Login to CDMS Portal.
  2. Navigate to:
    • Administration → Access Control → Access Control T2 Partner.
  3. In the search field, enter the User ID or Store Name and search.
  4. From the results, click Edit.
  5. In the details tab, locate the Email ID field.
  6. Update the email ID with the new partner-provided email.
  7. Click Save and Approve the changes.

Updating Partner City

  1. Request the partner to provide the CDMS User ID that requires city update.
  2. Raise a request with the CDMS IT Support Team to change the city for that User ID.
  3. Confirm with the partner once the update is successfully completed.

User / Partner Deactivation

Deactivation is required when a partner no longer uses a CDMS account, relocates to a new location, or needs to reinstall CDMS on a different system.

Step 1 – Collect Information

  • Obtain the User ID from the partner.
  • If the User ID is not available, retrieve the System Information from the T2 portal.

Step 2 – Raise Deactivation Request

  • Send a formal mail to IT Support requesting deactivation.
  • Include the following details in the mail:
    • Partner/Store Name
    • User ID (or System Info if User ID not available)
    • Reason for deactivation

Step 3 – Relocation Cases

  • If the partner has moved from one location to another:
    • Deactivate the previous location’s CDMS account first.
    • Obtain approval for the new location setup.
    • Proceed with fresh installation and registration at the new site.

CDMS Batch Upload Errors:

  • SQL Logic Error
    • Symptom: Error during Excel batch upload.
    • Resolution Step
      • Apply Filter (Ctrl+Shift+L) in Excel.
      • Validate columns:
        • Date format: yyyy/mm/dd (e.g., 2025/06/30).
        • GSTIN column: Enter value or NoGSTIN.
        • BP Category: Must be T3.
        • Barcode length: Exactly 20 characters (=LEN(cell)).
        • Remove unwanted rows/columns (Ctrl+Shift+Right Arrow → Delete).
      • Ensure no special characters (comma, apostrophe) in End Customer, City, Partner Name.
      • Use the official Batch Upload Template.
  • Input String Error
    • Causes:
      • Wrong date format.
      • Barcode length not equal to 20.
      • Extra/unwanted rows or columns.
    • Resolution:
      • Correct date to yyyy/mm/dd.
      • Validate barcode length (=LEN(cell)).
      • Delete empty/unwanted rows & columns.
  • Column Not Found (Column 9/11 Missing)
    • Cause: Extra unused rows and columns in file.
    • Fix: Delete unused rows (Ctrl+Shift+Down Arrow → Ctrl+- (Delete)).
    • Ctrl + shift + Right
  • MTM Not Matched Issue
    • Symptom: MTM not recognized in upload.
    • Resolution Steps:
      • Check if MTM exists in MTM Master File.
      • If missing → Request responsible admin to update MTM Master File.
      • If Present → Refresh CDMS and retry upload.

Tagging Issues:

It is the process of resolving Tagging Issues in CDMS, such as incorrect entries in BP Category, BP Name, End Customer, or GSTIN values.

Step 1: Access DM Tool

  1. Open the DM (Data Mart) Tool at: ➝ https://cdms.lenovo.com/DCSDM
  2. Login with authorized credentials.

Step 2: Download Template

  1. Navigate to Data Table.
  2. Click Download Template.
  3. Save the template file locally.

Step 3: Correct the Data

  1. Open the downloaded template in Excel.
  2. Correct tagging errors such as:
    • Wrong BP Category.
    • Incorrect BP Name.
    • Incorrect End Customer values.
    • Invalid GSTIN values.
  3. Ensure all corrected data follows standard CDMS format.

Step 4: Upload Corrected File

  1. Save the corrected file in Excel format.
  2. Ensure file name follows standard naming convention, e.g.:
    • SO_T3_TAGGING_EXP(15).xls
  3. Upload the corrected file into the DM Tool.

Note

  • Ensure corrections are verified before uploading to avoid duplication.
  • Maintain a local copy of corrected files for audit purposes.
  • File naming convention should always include SO, T3, TAGGING, and version number for traceability.

Cross Sale Issue:

A. Identifying the Correct Beneficiary Partner

  1. Validate transactions using the Barcode (unique per product).
  2. Review the transaction history across Sell-In, Sell-Thru, and Sell-Out stages.
  3. Example scenario: cdms
    • Lenovo → Rashi (T1) → Sell-In on 18 June 2024.
    • Rashi → Return to Lenovo on 3 Dec 2024.
    • Lenovo → Redington (T1) → Sell-In on 28 Dec 2024.
    • Redington → Sterling (T2) → Sell-Thru on 29 Jan 2025.
    • Sterling → Evaluable (T3) → Sell-Out on 28 Feb 2025.
    • Evaluable returned product to Sterling (not recorded).
    • Sterling incorrectly made return to Redington on 29 Apr 2025.
    • Redington returned to Lenovo on 6 May 2025.
    • Lenovo → Rashi (T1) → Sell-In on 30 May 2025.
    • Rashi → Spark Tech (T2) → Sell-Thru on 31 May 2025.
    • Spark Tech → Hiyanshi Infotech (T3) → Sell-Out on 29 Jun 2025.
  4. Error Identified:
    • Sterling failed to record the return from Evaluable but still got credit.
    • Correct beneficiary should be Spark Tech, not Sterling.
  5. Resolution: Update CDMS to credit Spark Tech.

Handling Duplication Issues

  1. Duplication occurs when the same Barcode is used for multiple Sell-Out entries.
  2. Verify product details against CDMS reports.
  3. Inform the partner:
    • “Duplication has occurred because the same product was sold multiple times in reports using the same barcode.”
  4. Request partner to share full report/invoices for verification.

Note

  • Always validate using Barcode, as it is unique per product.
  • For faster checks in invoices with multiple barcodes, use MTM (Model Number) first, then drill down to barcodes.
  • Key fields for validation: Barcode, Sell-In, Sell-Thru, Sell-Out, Invoice Date, and Status.
  • Keep records of corrected cases for audit and compliance.

Inventory Issues:

Sold-Out Products Still in Inventory

  • Issue: Product marked as sold but still appears in inventory report.
  • Resolution:
    • Escalate the issue to Niyaj.
    • Request removal of incorrect barcodes from inventory.

Missing Purchase Serial Numbers

  • Issue: Certain purchase serial numbers are missing from CDMS inventory report.
  • Resolution:
    • Escalate the issue to Niyaj.
    • Request addition of the missing serial numbers to inventory records.

Uploading Stock into Inventory

  • Requirement: Partners must upload all current stock at once.
  • Process:
    1. Prepare an Excel file with a single column titled Barcode.
    2. Enter all stock barcodes into this column.
    3. Upload the file into the CDMS Inventory Module.