Smarter Business Software for Sabah SMEs

This usually happens for three reasons:

• Version mismatch: Your AutoCount Accounting and AutoCount Server versions don't match. Update AutoCount Server to the latest version.
• Server service stopped: Right-click the AutoCount Server icon in your system tray and click Start Service.
• Firewall blocking: Check that port 19500 is open in Windows Firewall and your antivirus.

Still stuck? Our Plan B & C clients get priority remote troubleshooting for this.

AutoCount relies on SQL Server running in the background. To restart it:

1. Press Windows key, type Services, and open it.
2. Find SQL Server (A2006) or your SQL instance name.
3. Right-click and select Start. Wait until the status shows "Running".

If it keeps stopping, check that the service is set to Automatic startup and that your PC has enough disk space. This is covered under all our support plans.

AutoCount v2.0 requires periodic online license validation. If your server has been offline for more than 7 days, the license enters a grace period.

To fix:

1. Connect the server PC to the internet.
2. Open AutoCount — it will auto-validate within minutes.
3. Go to Tools > Program Control > Module Setting to check remaining offline days.

For restored account books, offline validity is 10 days. Need help setting up offline redundancy? Ask us about Plan C.

This means your database has minor corruption but is still repairable. Here's the safe fix:

1. Open AutoCount Management Studio > Tools > SQL Query.
2. Run this query (replace yourDBname with your actual database name):
   ALTER DATABASE yourDBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE
3. Then run:
   DBCC CHECKDB ('yourDBname', REPAIR_REBUILD)
4. Repeat until you see 0 allocation errors, 0 consistency errors.
5. Finally run:
   ALTER DATABASE yourDBname SET MULTI_USER

Warning: Always backup first. Not confident with SQL? Our Plan B & C includes monthly health checks to catch this early.

POS sync issues are usually network or port-related. Try this checklist:

• Check Server Monitor: On the back-end PC, open POS Server Monitor (check system tray). Make sure the sync service is running. If stopped, highlight it and click Restart.
• Verify Sync Port: Open POS Server Monitor and confirm the sync profile is linked to the correct database. Wrong port = no sync.
• Network connection: Ensure the POS terminal and back-end PC are on the same network and can ping each other.

Sync still failing? We can remote in and diagnose under Plan B or C.

AutoCount needs specific ports open to communicate between workstations and the server:

• AutoCount Server Port: 19500 (default)
• SQL Server Port: 1433 (or dynamic port if configured)
• POS Sync Port: Check your POS Server Monitor settings

To allow in Windows Firewall:

1. Go to Windows Defender Firewall > Advanced Settings > Inbound Rules.
2. Add new rules for AutoCount Server.exe and SQL Server.
3. Allow both TCP and UDP for the ports above.

We configure this during onboarding for all Plan C clients.

Common E-Invoice issues in AutoCount:

• API not connected: Go to E-Invoice Settings and verify your LHDN API credentials are correct and not expired.
• Invalid buyer details: Make sure customer TIN and business registration numbers are valid in the customer master file.
• Item code missing: All items must have valid classification codes (e.g., MSIC, tax type) mapped before submission.
• Invoice amount mismatch: Round-off differences between AutoCount and MyInvois can cause rejection. Check your tax rounding settings.

We provide E-Invoice setup and troubleshooting as part of all support plans. For complex mapping, we offer project-based services.

If invoices fail to submit to MyInvois, check these in order:

1. Internet connection: The server PC must have stable internet to reach LHDN servers.
2. API status: Log in to the LHDN MyInvois portal directly to confirm your API key is active and not revoked.
3. Error log: In AutoCount E-Invoice module, check the Submission Log for specific rejection codes (e.g., TIN invalid, amount mismatch).
4. Consolidated invoices: Ensure all individual invoices in a consolidated batch are valid before grouping.
5. Self-billed invoices: Verify supplier TIN and SST registration numbers are correctly entered.

Still failing? Send us the error screenshot via WhatsApp — Plan A clients get text support, Plan B & C get remote hands-on fixes.

POS terminals need periodic license validation, especially after hardware changes or Windows updates:

1. On the POS terminal, go to POS Front End > Settings > License.
2. Click Validate License while connected to the internet.
3. If it says "License not found," check that the terminal is pointing to the correct POS Server PC and database.
4. For new terminals, ensure the license is registered under the correct Product ID tied to your main license.

Note: Additional POS users must tie to the same Product ID as the main license. Need more terminals? Contact us for license expansion.

Report issues are usually caused by printer drivers, Crystal Reports runtime, or report template corruption:

• Update printer driver: Download the latest driver from your printer manufacturer's website (HP, Epson, Canon).
• Reinstall Crystal Reports runtime: AutoCount uses Crystal Reports for printing. Reinstall the runtime from the AutoCount installer DVD or download from SAP.
• Check default printer: Make sure a physical printer (not PDF or XPS) is set as default in Windows.
• Report template: If only one report is broken, restore the default template from Tools > Design Report or re-import the .rpt file.
• Paper size: Confirm the report paper size (A4, A5, thermal roll) matches your printer settings.

For custom report design or thermal printer setup, we offer project-based services quoted separately.