Microframe Corporation 3007 Series Guía de usuario descargar pdf (Pagina 107)

1-99

1 to 199

115: The MicroKernel cannot access the archival logging

dump file

The MicroKernel cannot access the archival logging dump file for

one of the following reasons:

 The filename indicated for dumping entries in an archival log is

not a valid filename. Be sure this filename does not contain a

volume specification. The dump file is created on the same

volume as the log file.

 The caller does not have access rights to the dump file.

 The MicroKernel cannot open the file because another user has

opened the file using an exclusive operating system lock.

116: The file is owned by another MicroKernel engine

acting as a Gateway

The MicroKernel cannot contact the engine running on the gateway

computer even though it can read the locator file. This might occur

the following reasons:

 The name of the gateway computer cannot be resolved. To solve

this problem, try one of the following:

 Ensure that the gateway computer is registered with your

name resolution service, such as DNS.

 If you are not using a name resolution service, you must

provide name resolution manually. Locate the file named

HOSTS on your current machine. Add a line in this file

associating the TCP/IP address of the gateway computer

with the network name of that computer. For example, if the

gateway computer is named “mycomp” and its IP address is

125.1.4.245, then you should add the following line to the

file:

125.1.4.245 mycomp

 When the two computers are separated by a router so they can

both see the server, but cannot see one another. Try the

following:

a. Use the Gateway Locator utility to identify the owner of the

gateway.

b. Use Pervasive System Analyser (PSA) to test the network

connection to that computer.

1 2 ... 102 103 104 105 106 107 108 109 110 111 112 ... 251 252

Sin comentarios

Microframe Corporation 3007 Series Guía de usuario Pagina 107