Upgrade From Notes 8.51FP2 to 8.5.2: Now Notes Starts But Displays "Error in Provisioning Operation"

HCL Domino Domino Forum
1

Hi …

I upgraded from Notes (all clients) 8.5.1FP2 to 8.5.2. Whenever I now start Notes, I get this message:

An internal error occurred during: “Provisioning Operation” - java.lang.StringIndexOutOfBoundsException

A look at one of the logs shows this:

<extendedDataElements name="CommonBaseEventLogRecord:level" type="noValue">

	<children name="CommonBaseEventLogRecord:name" type="string"> 

		<values>SEVERE</values>

	</children>

</extendedDataElements>

<extendedDataElements name="CommonBaseEventLogRecord:Exception" type="string">

	<values>java.lang.StringIndexOutOfBoundsException

at java.lang.String.substring(Unknown Source)

at com.ibm.rcp.provisioning.internal.requirements.Provisioning.parseRequestsFromString(Unknown Source)

at com.ibm.rcp.provisioning.internal.requirements.Provisioning.processDeferredActions(Unknown Source)

at com.ibm.rcp.provisioning.internal.impl.ProvisioningServiceImpl$1.run(Unknown Source)

at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)

</extendedDataElements>

<sourceComponentId component="Expeditor 6.2" componentIdType="ProductName" instanceId="1283368821388" location="mfeinman" locationType="Hostname" subComponent="org.eclipse.core.jobs" threadId="1" componentType="http://www.w3.org/2001/XMLSchema-instance"/>

<situation categoryName="ReportSituation">

	<situationType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>

</situation>

<extendedDataElements name="CommonBaseEventLogRecord:level" type="noValue">

	<children name="CommonBaseEventLogRecord:name" type="string"> 

		<values>SEVERE</values>

	</children>

</extendedDataElements>

<extendedDataElements name="CommonBaseEventLogRecord:Exception" type="string">

	<values>java.lang.NullPointerException

at com.ibm.rcp.provisioning.internal.impl.ProvisioningServiceImpl.processDeferredActions(Unknown Source)

at com.ibm.rcp.provisioning.ui.internal.ProvisioningStartup.earlyStartup(Unknown Source)

at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(Unknown Source)

at org.eclipse.ui.internal.EarlyStartupRunnable.run(Unknown Source)

at org.eclipse.core.runtime.SafeRunner.run(Unknown Source)

at org.eclipse.ui.internal.Workbench$54.run(Unknown Source)

at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)

</extendedDataElements>

<sourceComponentId component="Expeditor 6.2" componentIdType="ProductName" instanceId="1283368821388" location="mfeinman" locationType="Hostname" subComponent="org.eclipse.ui.workbench" threadId="2" componentType="http://www.w3.org/2001/XMLSchema-instance"/>

<situation categoryName="ReportSituation">

	<situationType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>

</situation>

<extendedDataElements name="CommonBaseEventLogRecord:level" type="noValue">

	<children name="CommonBaseEventLogRecord:name" type="string"> 

		<values>SEVERE</values>

	</children>

</extendedDataElements>

<sourceComponentId component="Expeditor 6.2" componentIdType="ProductName" instanceId="1283368821388" location="mfeinman" locationType="Hostname" subComponent="org.eclipse.ui" threadId="2" componentType="http://www.w3.org/2001/XMLSchema-instance"/>

<situation categoryName="ReportSituation">

	<situationType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>

</situation>

<extendedDataElements name="CommonBaseEventLogRecord:level" type="noValue">

	<children name="CommonBaseEventLogRecord:name" type="string"> 

		<values>SEVERE</values>

	</children>

</extendedDataElements>

<extendedDataElements name="CommonBaseEventLogRecord:Exception" type="string">

	<values>java.lang.NullPointerException

at com.ibm.rcp.provisioning.internal.impl.ProvisioningServiceImpl.processDeferredActions(Unknown Source)

at com.ibm.rcp.provisioning.ui.internal.ProvisioningStartup.earlyStartup(Unknown Source)

at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(Unknown Source)

at org.eclipse.ui.internal.EarlyStartupRunnable.run(Unknown Source)

at org.eclipse.core.runtime.SafeRunner.run(Unknown Source)

at org.eclipse.ui.internal.Workbench$54.run(Unknown Source)

at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)

</extendedDataElements>

<sourceComponentId component="Expeditor 6.2" componentIdType="ProductName" instanceId="1283368821388" location="mfeinman" locationType="Hostname" subComponent="com.ibm.rcp.provisioning.ui" threadId="2" componentType="http://www.w3.org/2001/XMLSchema-instance"/>

<situation categoryName="ReportSituation">

	<situationType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ReportSituation" reasoningScope="INTERNAL" reportCategory="LOG"/>

</situation>

Anyone see this before? If so, what did you do to get rid of the issue?

–Mark

2

Subject: Same Here

I have the same problem, but I upgraded from Lotus Notes 8.5.1FP3.

Also my system is Windows 7 x64.

This only seems to happen with upgrades. Another person in our department did a clean install and he does not get the error, and he has the same software and hardware.

We would like to find a fix for this though, because uninstalling every-ones Notes so that we can install the new version does not seem like a fun upgrade path.

3

Subject: upgrade from 8.5.1 fp4 to 8.5.2

I fixed the problem deleting com.ibm.rcp.provisioning.prefs which is in the folder workspace.metadata.plugins\org.eclipse.core.runtime.settings

4

Subject: Solution: Remove The Workspace Directory

After reading some unrelated entries whose solution was to remove the Workspace directory, I tried that for my issue and that seemed to resolve the problem. It did, however, delete my installed widgets and Domino Designer working sets & the databases listed within them, but I was due to clean that all up anyway.

5

Subject: That fixed it for me too.

It fixed it for me too, but it was kind of lame to have to blow my Workspace folder away.