Notes 8.5
1. Problem:
HTTP task does not load either automatically (due to being
listed in the Server tasks line) or manually with a "load HTTP "
command at the server console.
Symptom:
You will see one of the following error messages at the server
console as HTTP starts to load:
HTTP Server: Using Internet Site Configuration View
JVM: The Java Virtual Machine creation returned an invalid JVM
machine pointer.
JVM: Java Virtual Machine failed to start
HTTP Server: Error Loading Java Virtual Machine
HTTP Server: JVM: Missing entrypoint in JVM runtime library.
HTTP Server: Shutdown
or
HTTP Server: Using Internet Site Configuration View
JVMJ9VM015W Initialization error for library j9gc24(2): Failed to
instantiate heap; 256M requested
JVM: The Java Virtual Machine creation returned an invalid JVM
machine pointer.
JVM: Java Virtual Machine failed to start
HTTP Server: Error Loading Java Virtual Machine
HTTP Server: JVM: Missing entrypoint in JVM runtime library.
HTTP Server: Shutdown
Cause:
The JVM folders in the Domino program directory are not correct.
2. Problem:
You are upgrading the Domino Server from a version prior to
Domino 8.5, and your groups lose access
Symptom:
After the upgrade, your people lose access to applications that
they could previously use. The users are not listed in the ACLs
individually, but are group members.
Cause:
Check the group document properties in the Address Book and
determine if it has a "ShortName" field. If it has a "ShortName"
field, remove that field and save and close the Address book.
This field interferes with the users access in the $ServerAccess
field of the Address Book.
Recommendation:
Upgrade existing databases as necessary via 'compact -c '.
Doing so will allow Domino to take advantage of various
features associated with the latest ODS version.
Related Settings:
CREATE_R85_DATABASES, CREATE_R8_DATABASES
4. Problem:
When you save script library in the new eclipse editor "with
errors", then switch back to earlier version or non-eclipse
editor, you may end up seeing different code in different
environments. Or getting notification that a particular
subroutine already exists even if you see just one instance of
it.
Resolving the Problem:
Copying all script library text in eclipse editor, saving as lss file
and importing it in earlier version allows to synch back both
environments.
5. Problem:
This is an already existing issue in Lotus notes 8.5. The fix has
been proposed in Lotus Notes further releases.
LotusScript Agent stopped working after server upgrade from
7.0.3 to 8.5 (via 8.0)
Error reported: Object variable not set
Script was re-saved with 8.0.1 Designer to include some
additional prints to locate the offensive code. Change Notes
View Navigator from GetNextDocument to GetNext
' Set ssasnve2 = ssasnvn.GetNextDocument(ssasnve1) ' was
working in 7.0.x
Set ssasnve2 = ssasnvn.GetNext(ssasnve1) ' works in 8.5
Set ssasdoc = ssasnve2.Document
where ssasnve1 is a category, and ssasnve2 is a document