Requirement and relevance | How to obtain |
---|---|
Problem description Info used for analysis | End-user or Technical Support provided. |
Requirement and relevance | How to obtain |
---|---|
How many servers? Info used for analysis | End-user provided |
How many children (child servers) | N.A. |
Is LDAP being used? | N.A. |
Requirement | How to obtain |
---|---|
LSP version | N.A. |
Database version | For example, Microsoft SQL 2005, Microsoft SQL 2008 R2 or other. |
SharePoint version | Include service pack or patch levels. |
Requirement | How to obtain |
---|---|
SP/LSP logs | SP/LSP logs are in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS Refer to How to enable debug logging for Print Release for more information on how enable debug mode. |
Lexmark TPA (Transport Protocol Adapter) log | Navigate to C:\Program Files (x86)\Lexmark Solutions\LOGS or for 32‑bit systems C:\Program Files\Lexmark Solutions\LOGS |
DEBUG level logging can be configured within the TransportProtocolAdapter_log4net.config file |
|
Internet Information Service (IIS) logs that may be useful | Navigate to both C:\inetpub\logs and C:\Windows\System32\LogFiles\HTTPERR |
If the issue is specific to just one or two MFPs or SFPs, where all others in the fleet are fine | Capture a Menu Settings from the specific printer(s) Capture /se logs via EWS > embedded solution logs (Must be captured right away after the error and with debugging enabled) |