Question about Cosmi Print Perfect Platinum

1 Answer

Error reading event file - Cosmi Print Perfect Platinum

Posted by on

1 Answer

  • Level 1:

    An expert who has achieved level 1.

    Hot-Shot:

    An expert who has answered 20 questions.

    Corporal:

    An expert that hasĀ over 10 points.

    Mayor:

    An expert whose answer gotĀ voted for 2 times.

  • Contributor
  • 34 Answers

The EVT files include the event log messages as they are stored by the system. Each message is composed of an ID (that is, the message itself) and a number of insertion strings. The IDs are translated into strings through the use of messages DLLs.

All the application event logs messages DLLs are defined under the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\ Application

All the system event logs messages DLLs are defined under the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\ System

For example, the TCP/IP service's message DLL is defined under the following registry entry:
Key = HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\ System\TcpIp Value = EventMessageFile REG_EXPAND_SZ %SystemRoot%\System32\ netevent.d

Therefore, all the TCP/IP event log messages are defined in the DLL netevent.dll.

When the user double-clicks an event for which the message DLL is not defined in the registry, the message string cannot be displayed and the following message is displayed: The description for Event ID (51) in Source (aservice) could not be found. It contains the following insertion string(s): ... Below is a description of a way to read the system event logs of a computer with WINS on a computer without WINS. This sample can be adapted for any application or system component.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

The following operations are required:

  1. On the computer with WINS, run REGEDIT and select the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\ System\Wi
  2. On the Registry menu, click Export Registry File and select a file name (for example, Winsreg.reg).
  3. On the computer without WINS (for example, the one used to read the system event logs of the computer with WINS), run REGEDIT. On the Registry menu, click Import Registry File and select the file Winsreg.reg previously saved on the other computer.
  4. You should now have the following registry entry on the target computer (that is, the one without WINS):
    Key = HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ EventLog\System\Wins Value = EventMessageFile REG_EXPAND_SZ %SystemRoot%\System32\ winsevnt.d

    You now need to copy the file defined in the EventMessageFile registry value in your System32 directory. If X: is mapped to \\wins_server\admins$, you can run the following command: copy x:\System32\winsevnt.dll %SystemRoot%\System32\winsevnt.dll
    Of course, the file may be copied somewhere else, but in this case you need to edit the EventMessageFile registry value manually so that it points to the directory with the DLL.
  5. Close all the instances of the Event Viewer and rerun the Event Viewer. You should now be able to dump all the WINS events.

Posted on Nov 15, 2009

1 Suggested Answer

6ya6ya
  • 2 Answers

SOURCE: I have freestanding Series 8 dishwasher. Lately during the filling cycle water hammer is occurring. How can this be resolved

Hi,
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need.
goodluck!

Posted on Jan 02, 2017

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

1 Answer

Error code 1309


Click start control panel administrative tools computer management then select event viewer this may vary depending on what operating system you have
extend the events there you will see errors in red you will no what exactly what the error was and at what time it occured
Right click on the error message select properties you will see all details about the error
or click start type in event viewer press ENTER
this should give you some sort of understanding of the error and
you might be able work your way through the problem

In a perfect world, a computer would run smoothly without any glitch or error.
Of course it isn't a perfect world, though, and PCs do come under the occasional error.
One of those, Error 1309, occurs when you install either Microsoft Office 2003 or Microsoft Office Project 2003.
It is due to an ordering issue in the program's installation.
There is no perfect order because many computers handle the software differently, but there is a fix for the error if it should ever come up.

Open "Notepad."
Click "Format." Make sure "Word Wrap" is not selected or enabled.

Click "Open" and then navigate to the folder "C:\ProgramFiles\MicrosoftOffice2003\Files\Setup." Scroll through the list of files and select "PROJPRO.XML."
Search the file for the section "OCLNCORE.OPC_1033."
Once found, there will be a "CATCHLEVEL=1" written next to it.
Change the 1 to 3 so it reads "CATCHLEVEL=3

Save the file. Make sure it is saved over the original file.
This will override the error message 1309 and keep it from appearing.
http://support.microsoft.com/kb/830422
More information on error 1309

Aug 27, 2013 | Lenovo Computers & Internet

Tip

How to display Errors found and Repairs made by CHKDSK


<b> <p>How to display Errors found and Repairs made by the CHKDSK Command<br /></b> The Chkdsk command is used to verify the integrity of a file system and is capable of correcting discrepancies in system data files. This command has been with us since DOS days and has been modified by Microsoft as required to meet the requirements of new operating and file systems as they evolved. <br /> If you execute the Chkdsk command from a command prompt without using the F (fix) switch, Chkdsk runs in the read-only mode. As Chkdsk runs its tests on the drive, it displays the results of these tests on the monitor screen and the test results remain there for you to read until you close the CMD box.<br /> However there are several drawbacks to running Chkdsk in the read-only mode, especially on an active NTFS volume (usually C:) <br /> 1. Chkdsk cannot make any corrections to the drive while in the read-only mode.<br /> 2. If Chkdsk encounters more than minor errors, it will not complete all of its tests.<br /> 3. If you are running Chkdsk in the read-only mode on the active partition, Chkdsk frequently reports disk corruption and other file system errors which do not exist. This happens when the system modifies the disk during the Chkdsk testing sequence.<br /> Considering the above, there is little to be gained by running Chkdsk in the read-only mode.<br /> You need to run Chkdsk/F at the command prompt to test the drive and to correct any errors found.. As soon as you make this entry the system responds with:<br /> "The type of file system is NTFS. Cannot lock current drive."<br /> "Chkdsk cannot run because the volume is in use by another process. Would you like this volume to be checked the next time the system restarts? (Y/N)."<br /> After you key in "Y" (followed by enter) and re-boot, the operating system starts to load and you are advised that a disk check has been scheduled and unless you cancel it, Chkdsk/F will start to run in a few seconds. (Actually the file being executed at this time is Autochk.exe). Chkdsk will run through its phases but it only displays the test results on the monitor screen for about 2 seconds before the screen clears and the operating system continues to load!<br /> If problems were found wiith the file system, you will not have time to read any messages regarding what they were or what actions were taken. If corrupted files and/or orphaned files/directories were detected you would most probably like to know about it and other problems found by Chkdsk. So how do you display the errors found and actions taken?<br /> The answer is that since running Chkdsk/F is a system event, the information is recorded in the System Event Log under application events. To read the log, Click on Start, Control Panel, Administrative Tools, Event Viewer and Application. Look for "Winlogon" in the Source column and double click on it. An Event Properties dialog box will open and display the log for you to read..<br /> Yavacotech.<br />

on Dec 09, 2010 | Computers & Internet

Tip

How to display Errors found and Repairs made CHKDSK


How to display Errors found and Repairs made by the CHKDSK Command
The Chkdsk command is used to verify the integrity of a file system and is capable of correcting discrepancies in system data files. This command has been with us since DOS days and has been modified by Microsoft as required to meet the requirements of new operating and file systems as they evolved.
If you execute the Chkdsk command from a command prompt without using the F (fix) switch, Chkdsk runs in the read-only mode. As Chkdsk runs its tests on the drive, it displays the results of these tests on the monitor screen and the test results remain there for you to read until you close the CMD box.
However there are several drawbacks to running Chkdsk in the read-only mode, especially on an active NTFS volume (usually C:)
1. Chkdsk cannot make any corrections to the drive while in the read-only mode.
2. If Chkdsk encounters more than minor errors, it will not complete all of its tests.
3. If you are running Chkdsk in the read-only mode on the active partition, Chkdsk frequently reports disk corruption and other file system errors which do not exist. This happens when the system modifies the disk during the Chkdsk testing sequence.
Considering the above, there is little to be gained by running Chkdsk in the read-only mode.
You need to run Chkdsk/F at the command prompt to test the drive and to correct any errors found.. As soon as you make this entry the system responds with:
"The type of file system is NTFS. Cannot lock current drive."
"Chkdsk cannot run because the volume is in use by another process. Would you like this volume to be checked the next time the system restarts? (Y/N)."
After you key in "Y" (followed by enter) and re-boot, the operating system starts to load and you are advised that a disk check has been scheduled and unless you cancel it, Chkdsk/F will start to run in a few seconds. (Actually the file being executed at this time is Autochk.exe). Chkdsk will run through its phases but it only displays the test results on the monitor screen for about 2 seconds before the screen clears and the operating system continues to load!
If problems were found wiith the file system, you will not have time to read any messages regarding what they were or what actions were taken. If corrupted files and/or orphaned files/directories were detected you would most probably like to know about it and other problems found by Chkdsk. So how do you display the errors found and actions taken?
The answer is that since running Chkdsk/F is a system event, the information is recorded in the System Event Log under application events. To read the log, Click on Start, Control Panel, Administrative Tools, Event Viewer and Application. Look for "Winlogon" in the Source column and double click on it. An Event Properties dialog box will open and display the log for you to read..
Yavacotech.

on Dec 09, 2010 | Computers & Internet

1 Answer

I cannot drop files from my laptop to my lacie n2870. What is the problem?


Click start control panel administrative tools computer management then select event viewer this may vary depending on what operating system you have extend the events there you will see errors in red you will no what exactly what the error was and at what time it occured Right click on the error message select properties you will see all details about the error or click start type in event viewer press ENTER you might be able work your way through the problem

Jan 13, 2013 | LaCie Hard Disk 500GB with Hi-Speed USB2.0...

Tip

How to Fix Blue Screen Errors (BSOD)


<p>Blue screen errors, or blue screen of death (BSOD) errors, are the most severe errors Windows can encounter. Since Windows can not recover from this kernel level error, a blue screen is displayed with the error details. The error details contain a STOP error code, which indicates the type of error.<br /> <p>There are a lot of possible causes for blue screen errors, but most of them relate to the computer hardware. The cause of a BSOD error can be a temperature problem, a timing error, a resource conflict, hardware failure, a corrupt registry, a virus or simply a device incompatibility or driver error.<br /> <p><b>How to analyze blue screen errors</b><br /> <p>The first thing to do to analyze a blue screen error is to check the meaning of the STOP error code. You need to stop Windows from rebooting when a STOP error is encountered. Once the blue screen of death is shown, you can check the meaning of the STOP error code. Together with the filename of the driver or module, this will give an indication of the error cause.<br /> <p>Another option to analyze the cause of the blue screen error is to look at the Windows system event log or to debug the memory dump (minidump) that Windows created when the error occurred. The event log can be viewed using the event viewer. Right-click Computer in the Start menu, and then select Manage. In the Computer Management window select Event Viewer. The information in the event log can be of great help to isolate the cause of the blue screen error.<br /> <p>Reading the minidump requires a bit more technical knowledge, but Microsoft has tools to read the minidump.<br /> <p><b>The most common cause of blue screen errors</b><br /> <p>In reality, the most common cause of blue screen errors is a device driver problem. Outdated, incorrect or corrupt drivers can cause the system to encounter a STOP error, resulting in the BSOD.<br /> <p>So the easiest way to try and fix a blue screen error is to reinstall and update your system's device drivers. This will ensure that all driver bugs are fixed and that all hardware has the correct driver.<br /> <p>If you know which device caused the error, you can update or reinstall that driver first. The file name in the blue screen of death can help identify the driver. Look for a file with the .SYS extension and search for that file name.<br /> <p>If you do not have the drivers for all devices, or are not comfortable updating your PC's drivers manually, you can use a driver update tool to find, download and update all device drivers for you. Such tools will accurately identify your computer hardware, including any device causing an error, and automatically install the latest drivers for it.<br /> <p>In most cases updating or reinstalling drivers will solve your blue screen errors.<br /> <p><b>Other causes of blue screen errors</b><br /> <p>However, if updating device drivers does not fix the blue screen error, there are a number of additional things to try:<br /> <p>Load the default BIOS values - resource conflicts and timing issues can be caused by incorrect BIOS settings.<br /> <p>Update the BIOS - especially after adding new hardware or installing a Windows service pack this can help fix issues.<br /> <p>Update Windows - missing updates, including service packs can be a source of stop errors.<br /> <p>Check your system - run a virus scan and spyware scan after updating your definition files.<br /> <p>Driver rollback - if you have recently updated a driver, you can use the driver rollback to revert back to the previous driver version.<br />

on Nov 29, 2010 | Computers & Internet

1 Answer

The Machine Reboots after displaying Blue Screen With Error Message


Windows is entirely in control of any blue screens; so the hardware spec is not relevant yet.
can you try reading your windows event log immediately after a crash? :::Start>all programs>administrative tools>event viewer

you are looking for an error mentioning a filename... C:\windows\~somepath~\Minidump.dmp
If you get yourself a copy of WinDB (here: http://msdn.microsoft.com/en-us/windows/hardware/gg463009)

You can then open WinDB and open/read that crash dump file (file open crash dump), and it will provide you with a filename of the driver that caused a problem (possibly even tell you what it was doing when it was called).. chances are it's one of the following causing the problem: Graphics Card drivers Storage controller drivers Motherboard drivers (Power Management related issue usually)
If you have the latest driver; then get the hardware checked out...

May 17, 2011 | Intel D865GBF Intel 865G Socket 478 ATX...

1 Answer

I get error rtl100.bpl what must i do


hi
i am techbuddies from fixya group i would like to try and solve your issue .
please try to follow these steps

You probably read web pages written in a language that displays Right To Left
(hence rtl100) There are several reasons why that file might corrupt, an
add-on of some kind being the main suspect. Go to start/run, and type:

iexplore -extoff

to see it that stops the error.
If not, try refreshing all system files with :

sfc /scannow

if is doesnot work then try this

Are any devices malfunctioning? Select Start, All Programs, Accessories,
System Tools, System Information. Open Components under System Summary
and click on Problem Devices. Is anything listed there?

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Does anything turn up in the Event Viewer Logs?

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.
if the same problem comes up please try to get in touch with me on my email or on fixya

thanks
techbuddies

Dec 30, 2009 | Dell Microsoft Windows XP Home Edition

1 Answer

Windows dvd maker


What OS are you using? Ultimate, Premium, Basic?
Windows DVD Maker has stopped working Issue : While trying to create DVD in Windows DVD Maker in Vista, or while creating a DVD from Windows Movie Maker, which uses Windows DVD Maker, the burn process stops with error message.

Error message : " Windows DVD Maker has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. "

Cause : Windows DVD maker stops working because of incompatibility with one or more codec files which are outdated or incompatible with the particular project or the DVD Maker software itself.


Resolution :

These Codec files should be located and renamed to resolve the issue.

1. Open Start menu and type Event Viewer in the Start menu search bar. Open Event Viewer from the menu.

2. In the Event Viewer window Click on Windows Logs in the left panel

3. Click on Application Logs under Windows Logs

4. Locate error messages listed in the Central panel of the Event Viewer window and double click the error to check if this is log is related to DVD Maker.

Sample Error Log :

Problem signature

Problem Event Name: APPCRASH
Application Name: DVDMaker.exe
Application Version: 6.0.6000.16386
Application Timestamp: 4549b5b0
Fault Module Name: nevideohd.ax
Fault Module Version: 4.6.15.0
Fault Module Timestamp: 459bb828
Exception Code: c0000005
Exception Offset: 00008b89
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1062


5. Locate Fault Module name, it should be a file with extension .ax.

6. Once the file name is identified, try to locate the file in C:/Windows/System32 folder. ( Please click on Show Contents if the files are not listed Automatically ).

7. If the files are not listed in System32 folder, search for the file, with search containing system files and folders.

8. Locate the file and rename it.

9. Check if the issue persists. If the issue persists and the error message again appears, locate the new .ax file that is causing the issue from the Event Viewer, error log.

These steps will resolve the issue instantly without a restart.


Sep 18, 2008 | Computers & Internet

Not finding what you are looking for?
Cosmi Print Perfect Platinum Logo

145 people viewed this question

Ask a Question

Usually answered in minutes!

Top Cosmi Computers & Internet Experts

Tony

Level 3 Expert

2600 Answers

raysaw

Level 2 Expert

231 Answers

Les Dickinson
Les Dickinson

Level 3 Expert

18391 Answers

Are you a Cosmi Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...