![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello All, I have MVBASE 1.3 patchset 09 running on Windows Server 2003... The workstation component regularly stops working, and requires restarting manually. Does anyone know if I can make anything of this message that appears in the Event Log when this happens: Category: Workstation Type: Warning User: N/A Event ID: 192 Description: The description for Event ID ( 192 ) in Source ( mvBASE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retreive this description; see Help and Support for details. The following information is part of the event: mvworksc.exe, 0085, CiThread.cpp, 267, 0, 00001244, c0000005, 7db8173 These type of events always appear in the Event Log when the Workstation service stops responding (all clients connected via telnet stop responding, but I can get in with mvTERM). Is there anything I can do with this data to figure out why this is happening? Thanks. Gabe |
#3
| |||
| |||
|
|
Hello All, I have MVBASE 1.3 patchset 09 running on Windows Server 2003... The workstation component regularly stops working, and requires restarting manually. Does anyone know if I can make anything of this message that appears in the Event Log when this happens: Category: Workstation Type: Warning User: N/A Event ID: 192 Description: The description for Event ID ( 192 ) in Source ( mvBASE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retreive this description; see Help and Support for details. The following information is part of the event: mvworksc.exe, 0085, CiThread.cpp, 267, 0, 00001244, c0000005, 7db8173 These type of events always appear in the Event Log when the Workstation service stops responding (all clients connected via telnet stop responding, but I can get in with mvTERM). Is there anything I can do with this data to figure out why this is happening? Thanks. Gabe |
#4
| |||
| |||
|
|
Hi Gabe, I am sure you know this but mvBASE 1.3.02 is not certified for Windows 2003 server only version 2 is! I'm aware of it. Unfortunately it's what I have to work with at the |
|
I would say if you are going to keep running on 1.3.02 just use the application not the service! I'm trying that (thanks guys). |
|
I think also there is a later version then patch set 9 ( 9.1 or 9a ) you could have a look at that!! I'll double-check this morning when I come into the office. |
#5
| |||
| |||
|
|
Hi Gabe, I am sure you know this but mvBASE 1.3.02 is not certified for Windows 2003 server only version 2 is! I would say if you are going to keep running on 1.3.02 just use the application not the service! I think also there is a later version then patch set 9 ( 9.1 or 9a ) you could have a look at that!! |
|
Craig gabegreen (AT) gmail (DOT) com> wrote in message news:1158692321.663893.135020 (AT) m73g2000cwd (DOT) googlegroups.com... Hello All, I have MVBASE 1.3 patchset 09 running on Windows Server 2003... The workstation component regularly stops working, and requires restarting manually. Does anyone know if I can make anything of this message that appears in the Event Log when this happens: Category: Workstation Type: Warning User: N/A Event ID: 192 Description: The description for Event ID ( 192 ) in Source ( mvBASE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retreive this description; see Help and Support for details. The following information is part of the event: mvworksc.exe, 0085, CiThread.cpp, 267, 0, 00001244, c0000005, 7db8173 These type of events always appear in the Event Log when the Workstation service stops responding (all clients connected via telnet stop responding, but I can get in with mvTERM). Is there anything I can do with this data to figure out why this is happening? Thanks. Gabe |
#6
| |||
| |||
|
|
Hi, This is from the properties dialog box of the executable file: File Version 1.0.0.1 MVSERVER.EXE build#: 0085 Comments: Patch Set 9 Release Product Version: 1.3.02 Modified Feb 28 2003 Same values for the workstation app, etc... Is this the latest set of patches? I believe so but want to be sure. I am now trying application mode. Just curious, why the suggestion to run in app mode? I have no preference, just wondering why it may make a difference. Thanks, Gabe Craig wrote: Hi Gabe, I am sure you know this but mvBASE 1.3.02 is not certified for Windows 2003 server only version 2 is! I would say if you are going to keep running on 1.3.02 just use the application not the service! I think also there is a later version then patch set 9 ( 9.1 or 9a ) you could have a look at that!! How do I determ Craig gabegreen (AT) gmail (DOT) com> wrote in message news:1158692321.663893.135020 (AT) m73g2000cwd (DOT) googlegroups.com... Hello All, I have MVBASE 1.3 patchset 09 running on Windows Server 2003... The workstation component regularly stops working, and requires restarting manually. Does anyone know if I can make anything of this message that appears in the Event Log when this happens: Category: Workstation Type: Warning User: N/A Event ID: 192 Description: The description for Event ID ( 192 ) in Source ( mvBASE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retreive this description; see Help and Support for details. The following information is part of the event: mvworksc.exe, 0085, CiThread.cpp, 267, 0, 00001244, c0000005, 7db8173 These type of events always appear in the Event Log when the Workstation service stops responding (all clients connected via telnet stop responding, but I can get in with mvTERM). Is there anything I can do with this data to figure out why this is happening? Thanks. Gabe |
#7
| |||
| |||
|
|
Hi Gabe, The latest patch is 9.1 on rainingdata web site. I think the reason for running as an app is down to the certification the app works but service is flaky I seem to remember reading a link about this or talking to rainingdata support can't quite remember! I run one of my mvBASE 1.3.02 systems on 2003 but only as app and have had no issues at all!!!! Craig gabegreen (AT) gmail (DOT) com> wrote in message news:1158875487.550805.165790 (AT) i3g2000cwc (DOT) googlegroups.com... Hi, This is from the properties dialog box of the executable file: File Version 1.0.0.1 MVSERVER.EXE build#: 0085 Comments: Patch Set 9 Release Product Version: 1.3.02 Modified Feb 28 2003 Same values for the workstation app, etc... Is this the latest set of patches? I believe so but want to be sure. I am now trying application mode. Just curious, why the suggestion to run in app mode? I have no preference, just wondering why it may make a difference. Thanks, Gabe Craig wrote: Hi Gabe, I am sure you know this but mvBASE 1.3.02 is not certified for Windows 2003 server only version 2 is! I would say if you are going to keep running on 1.3.02 just use the application not the service! I think also there is a later version then patch set 9 ( 9.1 or 9a ) you could have a look at that!! How do I determ Craig gabegreen (AT) gmail (DOT) com> wrote in message news:1158692321.663893.135020 (AT) m73g2000cwd (DOT) googlegroups.com... Hello All, I have MVBASE 1.3 patchset 09 running on Windows Server 2003... The workstation component regularly stops working, and requires restarting manually. Does anyone know if I can make anything of this message that appears in the Event Log when this happens: Category: Workstation Type: Warning User: N/A Event ID: 192 Description: The description for Event ID ( 192 ) in Source ( mvBASE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retreive this description; see Help and Support for details. The following information is part of the event: mvworksc.exe, 0085, CiThread.cpp, 267, 0, 00001244, c0000005, 7db8173 These type of events always appear in the Event Log when the Workstation service stops responding (all clients connected via telnet stop responding, but I can get in with mvTERM). Is there anything I can do with this data to figure out why this is happening? Thanks. Gabe |
![]() |
| Thread Tools | |
| Display Modes | |
| |