EventID.Net Comments Queue
Comments for event ID 50
currently in the processing queue.
Please note that we have not reviewed this information yet so it was
unfiltered, exactly how it is submitted by our contributors.
| Event ID: 50 Event Source: prolsam Event Type: Error Event Description: Error page buffer locked. Comment: PROIV application hang and need to restart service5.5 (PROIV service). |
| Send comments |
| Event ID: 50 Event Source: CPQTeamMP Event Type: Warning Event Description: Event Type: Warning Event Source: CPQTeamMP Event Category: None Event ID: 50 Date: 29-07-2008 Time: 12:18:51 User: N/A Computer: GUD1T409 Description: TeamMember ID: 1 PROBLEM: This Teaming Protocol-Edge Configuration Parameters section of the Registry is either missing the LcdToeEnabled Parameter or the Parameter is unreadable. Setting value to 0. ACTION: No action is required if the Default behavior is acceptable. Otherwise reconfigure the LcdToeEnabled value. Data: 0000: 00 00 00 00 04 00 58 00 ......X. 0008: 00 00 00 00 32 00 04 80 ....2..€ 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ Comment: The registry key path you specified does NOT exist! Perhaps this is the problem with your driver it is attempting to use the wrong key Check it out with development! I used regedt32 to "Find" the presence of "{4D36E972-E325-11CE-BFC1-08002BE10318}" elsewhere in the registry. I located the following key. To this key I added VlanID and VlanDefaultID REG_DWORD 0x0 values. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0008 I then restarted the server and dissolved and re-created the team. This has solved the problems of the erroneous error messages concerning a corrupt XML file. Let me know when you have re-created this problem in your laboratory environment and then have certified an updated teaming driver fix. We kindly suggest you to follow the steps given below: 1. Please note down the TCP/IP settings of the Team adapter. 2. Launch the HP Network Configuration Utility (NCU) Click on Dissolve Click OK. To apply changes click Yes. After all configuration changes are successful click on OK. 3. Try to team the NIC reconfigure the TCP/IP settings and check for the status of the issue. 4. Also check if the values for VlanID and VlanDefaultID are set. You can add values to both under HKLM\SYSTEM\CurrentControlSet\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0008 as a REG_DWORD value with data value 0. |
| Send comments |
| Event ID: 50 Event Source: TermDD Event Type: - Event Description: - Comment: For us overwriting a few files with SP3 original solved the issue: copy c:\windows\ServicePackFiles\i386\lhmstsc.chm c:\windows\Help\mstsc.chm copy c:\windows\ServicePackFiles\i386\lhmstsc.exe c:\windows\system32\mstsc.exe copy c:\windows\ServicePackFiles\i386\lhmstsc.exe c:\windows\system32\dllcache\mstsc.exe copy c:\windows\ServicePackFiles\i386\lhmstsc.mui c:\windows\system32\en-US\mstsc.exe.mui copy c:\windows\ServicePackFiles\i386\lhmstscx.dll c:\windows\system32\mstscax.dll copy c:\windows\ServicePackFiles\i386\lhmstscx.dll c:\windows\system32\dllcache\mstscax.dll copy c:\windows\ServicePackFiles\i386\lhmstscx.mui c:\windows\system32\en-US\mstscax.dll.mui Index: 606 |
| Send comments |
| Event ID: 50 Event Source: TermDD Event Type: Error Event Description: Description: The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client. Comment: |
| Send comments |
| Event ID: 50 Event Source: Ftdisk Event Type: - Event Description: - Comment: I had the same problem with a Proliant DL360 connected to a MSA50, Run the tool dmdiag.exe in fact had problems with one of the partitions on the disk 2: This problem was due to one of the Array Controller being recognized by the system, as detected by the tool ACU HP, In the disk management console I appeared red one volume, Restart the computer and the system recognized the Array Controller again. Index: 945 |
| Send comments |
| Event ID: 50 Event Source: TermDD Event Type: - Event Description: - Comment: Im my case the problem was too much TCP conections and retries generated by Netware client installed in the server Index: 606 |
| Send comments |
| Event ID: 50 Event Source: TermDD Event Type: - Event Description: - Comment: In my case a corrupt virus scanner (Avira) caused the issue on a XP Machine. Deinstallation, reboot and reinstallation worked for me. Index: 606 |
| Send comments |
| Event ID: 50 Event Source: W32Time Event Type: - Event Description: - Comment: I fixed this on a SBS 2008 by doing the following: Open cmd and type: w32tm /config /syncfromflags:domhier /reliable:no /update press enter after that type: net stop w32time and press enter. After that type: net start w32time and press enter. Done Index: 3163 |
| Send comments |
| Event ID: 50 Event Source: Mup Event Type: Warning Event Description: {Delayed Write Failed} Windows was unable to save all the data for the file \\servername\drive\folder\ .. F49F04}_51.fh_imgRecord0. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Comment: This warning was logged when rebooting a server remotely. GoToMyPC was being used to log in remotely to a client PC which was logged into the server in question remotely using MSTSC and rebooted the server this way. This was the first time that the warning has been displayed. There were backup jobs running on the server in question but all were failing for multiple reasons: media was bad several local Backup Exec services failed a remote agent was hung. These all happened at the same time. Local BE services were able to be restarted but the remote agent service wouldn''''t shut down despite using multiple methods (e.g. SysInternals'''' pskill command). A reboot of that server was required. Immediately after this entry was logged it was followed up by an error using event ID 7034 with the source Service Control Manager Eventlog Provider then followed by a warning using event ID 50 with the source of mrxsmb. |
| Send comments |
| Event ID: 50 Event Source: TermDD Event Type: - Event Description: - Comment: This error can be caused by having hamachi installed and enabled. Hamachi canibalises pretty much the whole networking stack for its own selfish purposes. Try exiting hamachi. Index: 606 |
| Send comments |
| Submit a new event for research. |