Reporter 10 Can’t display new log when them can’t Unzip some RAW log file

I need a solution

Hi guy 

Sorry for post Reporter Discussion in Proxy I can’t found Reporter discussion forum 

In this case Reporter 10 Can’t display or query new log when them can’t unzip some RAW log file at first. 

How  can I config Reporter 10 to ignore or skip some interrupt RAW log file automatically ? 

Workaround:  we must to delete or move this interrupt file out of process RAW log folder manually.

BR

PK

0

Related:

  • No Related Posts

Looking for the reason CICS TS OpenBeta V5.4 region will not start up?

Getting the following messages trying to start CICS TS V5.4 Beta region for the first time:

08.01.46 STC05651 +DFHAP1203I TCICSA2 Language Environment is being initialized.
08.01.50 STC05651 +EQA9986E – Error in CEEEV006 loading OSI
08.01.50 STC05651 +DFHSR0601 TCICSA2 Program interrupt occurred with system task III in control
08.01.50 STC05651 +DFHME0116 TCICSA2 142
142 (Module:DFHMEME) CICS symptom string for message DFHSR0601 is
142 PIDS/5655BTA00 LVLS/710 MS/DFHSR0601 RIDS/DFHSRP PTFS/BETA9

Related:

Event ID 5004 — Network Adapter Interrupt Failure

Event ID 5004 — Network Adapter Interrupt Failure

Updated: January 7, 2009

Applies To: Windows Server 2008 R2

Interrupt failures can occur when:

  • The interrupt is already in use by another device in the computer, resulting in a resource conflict
  • The network adapter failed and therefore cannot detect the interrupt

 

Event Details

Product: Windows Operating System
ID: 5004
Source: E100B
Version: 6.1
Symbolic Name: EVENT_NDIS_INTERRUPT_CONNECT
Message: %2 : Could not connect to the interrupt number supplied.

Resolve
Replace or reconfigure the network adapter

The computer has an older Industry Standard Architecture (ISA) bus-enabled network adapter. Replace the network adapter with a newer version that is not ISA bus-enabled.

After replacing the network adapter, use Device Manager to update the driver.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To use Device Manager to update the network adapter driver:

  1. Click Start, type devmgmt.msc in Start Search, and then press ENTER.
  2. Expand Network Adapters.
  3. Right-click the network adapter, and then click Update Driver Software.
  4. Follow the steps in the Update Driver wizard.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To use Device Manager to view the status of network adapters:

  1. Click Start, type devmgmt.msc in Start Search, and then press ENTER.
  2. Click Network adapters in the Device Manager tree, and then verify that the network adapter is present.
  3. Right-click the network adapter, and then click Properties.
  4. Device Status should indicate This device is working properly.

 

Related Management Information

Network Adapter Interrupt Failure

Networking

Related:

%2 : Could not connect to the interrupt number supplied.

Details
Product: Windows Operating System
Event ID: 5004
Source: ndis
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_NDIS_INTERRUPT_CONNECT
Message: %2 : Could not connect to the interrupt number supplied.
   
Explanation

The parameters given to the driver are incorrect.

   
User Action

Use the Device Manager to remove and then reinstall the driver. If you continue to see this error message, contact the person with administrative rights on the computer for assistance.

Related:

Cannot request exclusive semaphores at interrupt time.

Details
Product: Windows Operating System
Event ID: 104
Source: Kernel
Version: 5.0
Component: System Resources
Symbolic Name: ERROR_INVALID_AT_INTERRUPT_TIME
Message: Cannot request exclusive semaphores at interrupt time.
   
Explanation

Exclusive system semaphores are owned by a task. The system checks to make sure that only the owner modifies the semaphore. It is impossible to determine the requester at interrupt time, so exclusive semaphores might not be modified then.

   
User Action

End your requested operation, wait awhile, and retry. If you still get this message, contact the supplier of the running application.

Related:

A conflict has been detected between two drivers which claimed equivalent IRQs. Driver %2, with device , claimed an interrupt with Level in data address 0x28, vector in data address 0x2c and Affinity in data address 0x30.

Details
Product: Windows Operating System
Event ID: 24
Source: Various
Version: 5.0
Component: System Event Log
Message: A conflict has been detected between two drivers which claimed equivalent IRQs. Driver %2, with device , claimed an interrupt with Level in data address 0x28, vector in data address 0x2c and Affinity in data address 0x30.
   
Explanation

Two drivers are requesting exclusive use of the same interrupt (IRQ). The second driver cannot be loaded, and functionality dependent on this driver will not be available.

   
User Action

Change the IRQ value for the specified driver. Or, if you know which driver is competing with the specified driver for this IRQ, change the IRQ value for the competing driver. For information on how to change the IRQ value, see your hardware documentation.

Related: