Domino Configuration Tuner problem

HCL Domino Domino Forum
1

Hi,

We’re trying to use the DCT tool to check our servers which are release 8.5 and 7.0.2FP2 on linux 2.6.16-0.12-bigsmp

This has been tried on different workstations running Windows XP, several times during the day.

Have tried different Lotus Domino servers

The report always fails with the rule

ServerInfo

Retrieve prerequisite server information

Is there something we’re missing?

Thanks

Ian

The detail being

The Domino Configuration Tuner experienced an internal error while evaluating this rule.

It is possible that some of the server data that is retrieved in order to evaluate this rule could not be parsed. Sometimes these errors are transient. An attempt to scan the server again may result in successful evaluation of this rule.

; Line#: 33; Column#: 71

net.sf.saxon.trans.XPathException: XQuery static error in #…ultnotesini, “PartitionNumber”#:

Variable $resultnotesini has not been declared
2

Subject: checking with the development team on this problem

3

Subject: Any progress from the Development Team

Hi Brian,

Any news from the Development Team?

Thanks

Ian

4

Subject: Re-created… similar setup

I have just tried DCT across our 7.0.2fp2 infrastructure from an 8.5 client and hit upon exactly the same error… any news from development ? thanks

5

Subject: Still a problem with DCT & $resultnotesini not declared

Hi,

We’ve just tried running the DCT tool against a Lotus Domino server version 8.5 running on a Windows 2003 server and getting the same response.

Can anyone indicate what the problem may be,a nd how this can be addressed?

Details are

An exception occurred while running rule: ‘ServerInfo’

; Line#: 33; Column#: 71

net.sf.saxon.trans.XPathException: XQuery static error in #…ultnotesini, “PartitionNumber”#:

Variable $resultnotesini has not been declared

Many Thanks

Ian

6

Subject: Thanks Brian

Hi Brian,

Thanks for the update. Let me know if there is anything else you need.

Ian

7

Subject: Is there any fix

I’m having the same issue on an xp box going to 2 2003 servers one 8 one 8.5