IBM AD04BML Installation Guide - Page 103

Troubleshooting Document Manager Server Configuration Problems

Get IBM AD04BML - Lotus Domino Document Manager PDF manuals and user guides View all IBM AD04BML manuals
Add to My Manuals
Save this manual to your list of manuals

Page 103 highlights

Chapter 9 Troubleshooting Document Manager Server Configuration Problems If a Lotus Domino Document Manager server is not configured correctly, users may run into errors when they try to perform various tasks. For example, when creating a document via the browser client, the user may see a message such as "Form Processed" or "Agent Done." Alternatively, the Document Manager log file (domdoc.log, located in Document Manager directory) may report an error condition such as "The Domino.Doc Configuration database could not be opened." Such problems can occur if the Document Manager server cannot identify itself on the network. In some cases, this may be the result of a subtle server misconfiguration. This chapter provides suggestions for locating and correcting the source of the problem. • Checking server configuration • Checking server information in profile documents • Checking template signatures Checking server configuration To check that the Document Manager server name and other related settings are correctly specified, follow these steps: 1. Log on to the Document Manager server using an administrator ID (a Notes ID that is a Domino administrator). 2. Open the server's Address Book or Domino Directory (names.nsf). 3. Open the server's Server document. 4. On the Basics tab, check the server address specified in the "Fully qualified Internet host name" field. From an operating system shell on the server, perform a "ping " to make sure that the server address is consistent with your network topology. 99

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
Chapter 9
Troubleshooting Document Manager Server
Configuration Problems
If a Lotus Domino Document Manager server is not configured correctly,
users may run into errors when they try to perform various tasks.
For example, when creating a document via the browser client, the user may
see a message such as “Form Processed” or “Agent Done.” Alternatively, the
Document Manager log file (domdoc.log, located in Document Manager
directory) may report an error condition such as “The Domino.Doc
Configuration database could not be opened.”
Such problems can occur if the Document Manager server cannot identify
itself on the network. In some cases, this may be the result of a subtle server
misconfiguration.
This chapter provides suggestions for locating and correcting the source of
the problem.
•
Checking server configuration
•
Checking server information in profile documents
•
Checking template signatures
Checking server configuration
To check that the Document Manager server name and other related settings
are correctly specified, follow these steps:
1.
Log on to the Document Manager server using an administrator ID (a
Notes ID that is a Domino administrator).
2.
Open the server’s Address Book or Domino Directory (names.nsf).
3.
Open the server’s Server document.
4.
On the Basics tab, check the server address specified in the “Fully
qualified Internet host name” field. From an operating system shell on
the server, perform a “ping <servername>” to make sure that the server
address is consistent with your network topology.
99