Cardiac catheterization lab softwares · ICAR family

GE Healthcare Mac-Lab: troubleshooting and error codes

The ServiceForge knowledge base holds 44 documented symptoms for the GE Healthcare Mac-Lab, with 88 ranked causes, 89 diagnostic checks with test points and expected values, and 0 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI

Symptoms

Domain security policy not confirmed on Acquisition systems

Administrator group members (INW\Domain Admins, INW\[withheld], INW\[withheld]) missing from Administrators group on Acquisition system

Ranked causes

1. Acquisition system not in correct domain or domain policy not applied (common)
2. Domain group policy not updated on Acquisition system (common)
3. TCP/IP properties misconfigured on server or Acquisition system (occasional)
4. INW server and Acquisition system cannot communicate (occasional)
5. DNS setup incorrect on Acquisition system (occasional)
6. Time on server and Acquisition system do not match (occasional)
7. Domain membership corrupted on Acquisition system (rare)

First check

Verify Acquisition system is in correct domain

Test point: Computer Name tab in System Properties
Expected: INW Domain is present

10 more checks with pass and fail actions, 8 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Supplies and list items from CVIS not appearing on Mac-Lab

Items added to CVIS system do not display on Mac-Lab interface

Ranked causes

1. INW service not configured or started (common)
2. CVIS List Sharing Delta export not configured for location (common)
3. Corrupt XML export from CVIS system (occasional)
4. CVIS List Sharing services not started (common)
5. Replication errors or issues with INW Server and Mac-Labs (occasional)
6. Network connection between CVIS and INW server lost (occasional)

6 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

System not ready for operation high voltage

IEB, computer, monitors, or connected equipment not powered on or properly connected; cables frayed, exposed, bent, or damaged

Ranked causes

1. IEB not plugged in or power unavailable at wall outlet (common)
2. IEB power switches off (common)
3. HP computer power switch off (common)
4. Monitors not turned on or improperly adjusted (common)
5. Loose or damaged cable connections (occasional)

First check

Verify wall outlet power available

Test point: wall outlet
Expected: AC power present
Tools: multimeter

4 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Cases performed on Mac-Lab not appearing in CVIS system

Completed procedures and case data from Mac-Lab do not sync to CVIS

Ranked causes

1. Interfaces on CVIS server not running or configured improperly (common)
2. Data Export Utility on Mac-Lab not configured correctly (common)
3. Data Export not enabled in System Admin File Path setup (common)
4. Network connection between Mac-Lab and CVIS Server down (occasional)

4 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Patient search not working with known admitted patients

Patient search returns no results even though patient is known to be admitted in HIS

Ranked causes

1. DICOM settings on Mac-Lab not configured correctly (common)
2. Network connection lost between Mac-Lab and CVIS (occasional)
3. Patient Interface service not running (common)
4. HIS feed to ADT Interface is down on CVIS (occasional)

4 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Unable to capture image

Image grabber window is blank or displays error (no video found).

Ranked causes

1. Loose or incorrectly connected cables (common)
2. Odyssey firmware version incorrect (occasional)
3. Odyssey driver not installed or updated (occasional)
4. Video source not connected or IntelliCam not configured (occasional)

First check

Verify all cables and connectors are tight

Test point: Red cable (input 1), blue cable (input 2), left DVI port (channels 1-2), right DVI port (channels 3-4)
Expected: Cables connected to correct inputs and ports

3 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Barcode scanner does not work or system locks after first scan

Barcode scanner malfunction or system hangs following initial scan operation

Ranked causes

1. Barcode scanner connected to mouse input instead of keyboard input (common)
2. Barcode scanner cable connected to PS/2 keyboard connector while power on (common)
3. Incorrect barcode scanner cable type (occasional)

3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Group Policy not applying correctly to local computer

Custom shell not displayed; domain user lacks admin rights; SQL replication failures; auto OS login fails

Ranked causes

1. Computer not in correct Organizational Unit (OU) (common)
2. Network settings incorrect (DNS, IP, Subnet, Gateway) (common)
3. Local machine time not synchronized with Domain Controller (occasional)

First check

Verify computer OU assignment

Test point: Active Directory computer object
Expected: Computer in correct organizational unit for policy scope

2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Image buttons grayed out

Live and Freeze buttons on Image window toolbar are grayed out and unavailable.

Ranked causes

1. CardioImage or Image capture option not enabled (common)
2. Odyssey board firmware outdated or driver not installed (occasional)
3. IntelliCam cannot detect Odyssey 0 device (occasional)

First check

Verify software options and monitor configuration

Test point: Software options, Image window location
Expected: CardioImage enabled, Image capture enabled, window on third monitor

2 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Patient not found in Schedule search after CVIS scheduling

Scheduled patient from CVIS system does not appear when searching Mac-Lab schedule

Ranked causes

1. DICOM settings not configured correctly on Mac-Lab (common)
2. DICOM services not running on CVIS Server (common)
3. Network connection lost between Mac-Lab and CVIS (occasional)

3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Test DICOM connectivity with X-ray system

Diagnostic procedure to verify DICOM configuration and connectivity between Mac-Lab and X-ray system

Ranked causes

1. MWL MPPS Service not running on Mac-Lab after configuration changes (common)
2. X-ray system not configured to use Mac-Lab as MWL/MPPS destination (common)
3. Networking problem between Mac-Lab and X-ray system (occasional)

First check

Test network connectivity via PING

Test point: Command prompt
Expected: PING successful response from X-ray system hostname or IP address

3 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Cannot obtain proper policies on acquisition or review system

Policies not applied to acquisition or review workstation systems

Ranked causes

1. DNS not pointing to correct INW server (common)
2. INW server unreachable (occasional)

First check

Verify DNS configuration

Test point: DNS settings on workstation
Expected: DNS entry directed to INW server IP

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

CryoCath to other ablation device switching procedure

Transition from CryoCath to RF ablation device or vice versa; cable and driver switchover sequence

Ranked causes

1. Incorrect switchover sequence may cause communication loss or driver failure (occasional)
2. Incorrect switchover sequence when switching to CryoCath may cause communication loss (occasional)

First check

Verify current ablation device and cable configuration

Test point: Ablation setup screen and physical cable at catheter connector
Expected: Software driver and physical cable match; either CryoCath or RF device installed

2 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

DNS resolution by name fails

System cannot ping remote device by name; resolves by IP address only

Ranked causes

1. DNS client-side cache out of date (common)
2. DNS server-side configuration error (occasional)

First check

Ping device by IP address

Test point: Remote Device IP
Expected: replies received

1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Image distorted or partially cut off

Able to capture images using provided DCF files but image is distorted, cropped, vertically elongated, or horizontally elongated.

Ranked causes

1. Incorrect pixel clock setting (common)
2. Incorrect video timing settings (horizontal/vertical positioning) (common)

First check

Test all provided DCF files to identify best image

Test point: IntelliCam Digitizer menu
Expected: Identify DCF file with best image quality

2 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

No login through custom shell

User unable to authenticate through the custom shell interface on Windows XP/2003 system

Ranked causes

1. Auto-logon sequence interfering with login (common)
2. Incorrect group policies applied to system (occasional)

First check

Verify user can reach Windows logon dialog

Test point: Start Menu
Expected: Shift+logoff shows standard Windows logon dialog

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

No video display on review stations with 18 inch LCD monitor

Monitor connected to review station displays no video output

Ranked causes

1. Video cable disconnected, damaged, or incorrect type (common)
2. Monitor or video card defective (occasional)

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Replication errors in Mac-Lab system

Database replication between clab database and clients fails; synchronization incomplete

Ranked causes

1. Replication tool cannot connect to clab database on acquisition system (common)
2. SQLServerAgent service logon credentials incorrect or missing (common)

First check

Verify replication tool connectivity to clab database

Test point: Acquisition system, clab database port 1433
Expected: Connection successful; replication tool can query database

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

System cannot communicate on network

Equipment unable to reach other devices; ping to gateway or remote hosts fails

Ranked causes

1. IP addressing misconfigured (common)
2. Default Gateway not routing packets correctly (occasional)

First check

Ping loopback address

Test point: 127.0.0.1
Expected: replies received

3 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Unable to communicate with TRAM

System cannot connect to TRAM unit; network communication fails during operation

Ranked causes

1. System IP address in TRAM reserved range 192.168.0.xxx (common)
2. TRAMnet jumper cable disconnected or improperly seated (common)

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Unable to logon to Custom Shell with Hospital User

User cannot authenticate to Custom Shell using hospital account credentials

Ranked causes

1. Default_MLCL Computers_Policy missing proper trusted user group information (common)
2. Users group missing required MLCL groups for logon rights (common)

First check

Verify Default_MLCL Computers_Policy is listed

Test point: Group Policy Objects Applied list
Expected: Default_MLCL Computers_Policy present

2 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

3rd monitor in pan mode after resolution change

Display for 3rd monitor changed to pan mode showing only portion of desktop after display resolution changed to 1600X1200.

Ranked causes

1. Monitor does not natively support 1600X1200 resolution (occasional)

First check

Install ATI Control Panel utility

Test point: Setup.exe in ATI FireGL driver folder
Expected: ATI Control Panel installed and system restarted

2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Ablation device not receiving data

Ablation device driver does not receive data from cable or device; data transmission fails

Ranked causes

1. COM port communication error between device driver and hardware (common)

First check

Click ablation device driver in ablation setup screen to reset COM port

Test point: Ablation setup screen device driver button
Expected: COM port resets; device reconnects and begins receiving data

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Amplifier communication choppy signals in CardioLab

Signal acquisition from amplifier is degraded, intermittent, or contains noise artifacts

Ranked causes

1. PCI Comms board incorrect version number (occasional)

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Amplifier signals incomplete, intermittent, or noisy

Received signals from amplifier are incomplete, drop out intermittently, or contain noise

Ranked causes

1. Fiber optic cable contaminated with dust or debris (common)

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Archive utility user configuration required

GEMS Task Scheduler service must be configured with [withheld] account credentials and set to automatic startup

Ranked causes

1. GEMS Task Scheduler not configured with correct user account (common)

First check

Access GEMS Task Scheduler service properties

Test point: Services administrative tool
Expected: GEMS Task Scheduler service opens in properties dialog

2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Barcode scanner disconnected or not connected caution

Barcode scanner cable not connected or disconnected while system powered

Ranked causes

1. Barcode scanner cable disconnected while powered (occasional)

First check

Verify barcode scanner cable connected

Test point: barcode scanner connector
Expected: cable connected securely with power off

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Calibration: RF noise during ablation procedure caution

RF noise present during cardiac ablation procedure requires mitigation

Ranked causes

1. RF noise interference during ablation (occasional)

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Clients not in correct Active Directory Organization Unit or group policies not applied

Client systems missing group policy settings or not in correct organization unit; replication cannot proceed

Ranked causes

1. Client not joined to domain or organization unit misconfigured (occasional)

First check

Verify all clients are domain members and in correct Organization Unit before starting replication

Test point: Active Directory Users and Computers; each client system
Expected: All client systems show as domain-joined members in correct OU; group policies applied

1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Correct group policies not applied

System does not have Default_MLCL Computers_Policy listed in applied group policy objects

Ranked causes

1. System not properly entered into domain (common)

First check

View applied group policy settings

Test point: Help > Pick a Task > Use tools > Tools > Advanced System Information
Expected: View Group Policy settings applied displays in right window (up to 2 minutes)

1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Data import does not work on non-English systems

Patient demographics cannot be imported from CARTO XP systems on non-English CardioLab installations

Ranked causes

1. Non-English CardioLab system language incompatibility (common)

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Equipment housing damaged or overheating caution

Visible cracks in housing, signs of overheating, or other physical damage to equipment enclosure

Ranked causes

1. Equipment housing cracked or damaged (rare)

First check

Visually inspect housing for cracks and damage

Test point: equipment enclosure exterior
Expected: no visible cracks, overheating signs, or damage

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

InSite 2.0 service agent loses connection to network or enterprise server

Service agent loses connection to network or enterprise server

Ranked causes

1. Network or enterprise server down (occasional)

First check

Verify network or enterprise server is available

Test point: Network connectivity, enterprise server status
Expected: Network and enterprise server operational

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

InSite 2.0 service agents fail to start after system restart

Service agents attempt to start three times then shut down when system is restarted

Ranked causes

1. Agents require manual restart after system restart (common)

First check

Verify agents have shut down after three startup attempts following system restart

Test point: InSite 2.0 agent status
Expected: Agents have stopped after three connection attempts

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Option codes become corrupted

Option codes cannot be read or applied correctly; system may not recognize licensed features

Ranked causes

1. Corrupted option registry keys (rare)

4 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Replication setup required for Acquisition systems

Each Acquisition system must be added to replication on INW server via Service Console to enable data consolidation

Ranked causes

1. Acquisition systems not yet added to replication (common)

3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Scrambled video display after 6.0 software upgrade

Video output appears garbled or corrupted following system upgrade to version 6.0

Ranked causes

1. Incompatible refresh rate between video card and monitor (occasional)

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Serial number entered incorrectly

System does not recognize or accept serial number entry; options cannot be applied

Ranked causes

1. Incorrect serial number value provided (common)

First check

Open command prompt

Test point: Windows command line
Expected: Command prompt window opens

2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Slow network transfer and ping speeds

Network communication experiencing reduced performance; transfer rates below expected

Ranked causes

1. NIC not negotiating 100mb/s Full Duplex with switch (common)

First check

Verify NIC negotiation speed and duplex

Test point: Network Interface Card settings
Expected: 100mb/s Full Duplex

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

SQL database not running on clients or service fails to start

SQL Agent service does not run on client systems; service fails when manually started; databases are not replicated to clients

Ranked causes

1. SQL user password changed without replication update on all systems (common)

First check

Verify SQL user password change was followed by replication update on all systems

Test point: Acquisition system and all client systems SQL Server configuration
Expected: All systems running the same SQL user password; replication completed successfully

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

SQL Server registration required for replication

SQL Server must be registered in Enterprise Manager before Acquisition systems can be added to replication

Ranked causes

1. SQL Server not yet registered in Enterprise Manager (common)

First check

Access SQL Server Enterprise Manager

Test point: Server desktop
Expected: Enterprise Manager opens and shows SQL Server Group

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Test DICOM connectivity with CVIS

Diagnostic procedure to verify DICOM configuration and connectivity between Mac-Lab and CVIS

Ranked causes

1. DICOM configuration settings incorrect on Mac-Lab or CVIS (common)

First check

Perform patient search for common name

Test point: Study > Patient Search at Navigator
Expected: Enter Patient Last Name of Smith and press Start Search

4 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Unable to logon to Custom Shell with hospital user account

User cannot authenticate to the Custom Shell using hospital credentials

Ranked causes

1. Default_MLCL Computers_Policy missing proper trusted user group information (common)

First check

Verify Default_MLCL Computers_Policy is listed under Applied Group Policy Objects

Test point: Group Policy Management Console, Applied Group Policy Objects
Expected: Default_MLCL Computers_Policy listed

2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI

User does not have appropriate rights error

Error message displayed when logged in domain as [withheld]

Ranked causes

1. User not in correct organizational unit (OU) (common)

1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Community

0 fixes logged by technicians through their AI, with outcomes, for this model.

ServiceForge knowledge base record. Field-unverified unless technicians confirmed it. A teaching summary of the record, not a service manual. Export 2026-10-14.