HVS32 does not start on Windows 10: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
Ddang (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „de:HVS32_startet_nicht_unter_Windows_10 Sollte unter einem Windows 10 Client beim Starten der HVS32.exe ein Betriebssystem-Fehler erscheinen, könnte es a…“) |
Ddang (Diskussion | Beiträge) |
||
| (Eine dazwischenliegende Version desselben Benutzers wird nicht angezeigt) | |||
| Zeile 1: | Zeile 1: | ||
[[de:HVS32_startet_nicht_unter_Windows_10]] | [[de:HVS32_startet_nicht_unter_Windows_10]] | ||
| − | + | If an OS error appears on a Windows 10 client while starting the HVS32, the problem might be related to the sharing of the HVS32 directory.[[File:0xc0000142.jpg|thumb|Error message]][[File:Error 0xc0000142 Event.JPG|thumb|Event Logs]] | |
= Diagnose = | = Diagnose = | ||
| − | + | This problem was reconstructable with the following constellation: | |
| − | * | + | *The client computer on which the HVS32 is supposed to be executed, runs with a Windows 10 OS |
| − | * | + | *The server on which the HVS32 is installed, runs with a Windows 2008 R2 OS |
| − | * | + | *The HVS32.exe does not start, but cancels with the following error message: "The application was unable to start correctly (0xc0000142)" |
| − | * | + | *It does not matter if the HVS32.exe is called via UNC path or mapped network drive (see also [[HVS32_crash_under_Windows_10|HVS32 crash under Windows 10]]) |
| | ||
| − | = | + | = Error cause = |
| − | + | The problem is that the sharing on the HVS32 directory under Windows 2008 R2 is executed with the sharing assistent, but not with a so-called "extended sharing". Under Windows 10, problems could arise due to the access on the sharing or rather loading of recources (DLLs) from this directory. | |
| | ||
| − | = | + | = Solution = |
| − | + | To safely configurate the sharing of the HVS32 directory under Windows 2008 R2 server for Windows 10 clients, do the following: | |
| − | # | + | #Login to the Windows 2008 R2 Server as administrator, on which the HVS32 is installed. |
| − | # | + | #Navigate to the installation directory of the HVS32 in the Windows explorer |
| − | # | + | #Right click the HVS32 installation directory and select "Properties" (Abb. 1 -> Tag 1) |
| − | # | + | #Select the menu point "Sharing" (Abb. 2 -> Tag 2) and click on "Advanced Sharing" (Abb. 2 -> Tag 3) |
| − | # | + | #Click on "Add" (Abb. 3 -> Markierung 4)<br/> '''Note:''' If this function is not active, you need to follow these steps: |
| − | ## | + | ##Activate the checkbox "Share this folder" (Abb. 3a -> Tag 5) |
| − | ## | + | ##Set an unique share name under "share name" |
| − | ## | + | ##Continue with step 7 |
| − | # | + | #Set a '''new''' unique share name in the window "New Share" under "Share name" (Abb. 4 -> Tag 6) (e.g. HVS32_WIN10) and confirm the dialog with "OK" |
| − | # | + | #Click on "Permissions" (Abb. 5 -> Tag 7) and enter all groups/users into the dialog (Abb. 6 -> Tag 8) who should receive access to the HVS32. Here you need read and write permission, because the VS32 has to create files as well. |
| − | # | + | #Confirm all dialogues with "OK" |
| − | # | + | #Navigate on the Windows 10 client via Windows explorer to the '''new''' HVS32 sharing and start the HVS32.exe |
| − | # | + | #Adjust the HVS32 links on the Windows 10 clients to the new sharing via UNC path (see also [[HVS32_crash_under_Windows_10|HVS32 crash under Windows 10]]) |
| − | #(Optional) | + | #(Optional) Adjust the network drive connections of the remaining clients to the '''new''' sharing |
| | ||
Aktuelle Version vom 15. Juli 2024, 12:19 Uhr
If an OS error appears on a Windows 10 client while starting the HVS32, the problem might be related to the sharing of the HVS32 directory.
Diagnose
This problem was reconstructable with the following constellation:
- The client computer on which the HVS32 is supposed to be executed, runs with a Windows 10 OS
- The server on which the HVS32 is installed, runs with a Windows 2008 R2 OS
- The HVS32.exe does not start, but cancels with the following error message: "The application was unable to start correctly (0xc0000142)"
- It does not matter if the HVS32.exe is called via UNC path or mapped network drive (see also HVS32 crash under Windows 10)
Error cause
The problem is that the sharing on the HVS32 directory under Windows 2008 R2 is executed with the sharing assistent, but not with a so-called "extended sharing". Under Windows 10, problems could arise due to the access on the sharing or rather loading of recources (DLLs) from this directory.
Solution
To safely configurate the sharing of the HVS32 directory under Windows 2008 R2 server for Windows 10 clients, do the following:
- Login to the Windows 2008 R2 Server as administrator, on which the HVS32 is installed.
- Navigate to the installation directory of the HVS32 in the Windows explorer
- Right click the HVS32 installation directory and select "Properties" (Abb. 1 -> Tag 1)
- Select the menu point "Sharing" (Abb. 2 -> Tag 2) and click on "Advanced Sharing" (Abb. 2 -> Tag 3)
- Click on "Add" (Abb. 3 -> Markierung 4)
Note: If this function is not active, you need to follow these steps:- Activate the checkbox "Share this folder" (Abb. 3a -> Tag 5)
- Set an unique share name under "share name"
- Continue with step 7
- Set a new unique share name in the window "New Share" under "Share name" (Abb. 4 -> Tag 6) (e.g. HVS32_WIN10) and confirm the dialog with "OK"
- Click on "Permissions" (Abb. 5 -> Tag 7) and enter all groups/users into the dialog (Abb. 6 -> Tag 8) who should receive access to the HVS32. Here you need read and write permission, because the VS32 has to create files as well.
- Confirm all dialogues with "OK"
- Navigate on the Windows 10 client via Windows explorer to the new HVS32 sharing and start the HVS32.exe
- Adjust the HVS32 links on the Windows 10 clients to the new sharing via UNC path (see also HVS32 crash under Windows 10)
- (Optional) Adjust the network drive connections of the remaining clients to the new sharing
 Abb. 1 |
 Abb. 2 |
 Abb. 3 |
 Abb. 3a |
 Abb. 4 |
 Abb. 5 |
 Abb. 6 |