Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Requisition synchronization is failing due to space in requisition name

Description

The following error is logged in web.log file after creating a new requisition and attempting to synchronize the requisition.

----Error---- [Requisition-Accessor-Thread] o.o.n.p.p.RequisitionFileUtils: Trying to create snapshot for file:/C:/Program%20Files/OpenNMS/etc/imports/pending/FileName.xml, but /C:/Program%20Files/OpenNMS/etc/imports/pending/FileName.xml does not exist.
----Error----
After running process mon I noticed the application performs a CreateFile operation for C:\Program Files\OpenNMS\etc\imports\FileName.xml and result in NAME NOT FOUND.

Manually copying from C:\Program Files\OpenNMS\etc\imports\pending\FileName.xml to C:\Program Files\OpenNMS\etc\imports\FileName.xml results in a successful synchronization in OpenNMS.

Running on Windows 2012 R2 64 Bit.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Alejandro Galue April 15, 2016 at 3:05 PM

Thanks to f068cdb5fb07488dd7f09d249fd4b95be4002e63 (on foundation-2016). The problem was a server side class responsible for managing the requisition changes through the ReST API. The new requisitions UI and provision.pl are working now as expected.

Seth Leger April 6, 2016 at 11:46 AM

This seems related to but not identical to https://opennms.atlassian.net/browse/NMS-8086#icft=NMS-8086.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created March 18, 2016 at 3:28 PM
Updated April 15, 2016 at 3:05 PM
Resolved April 15, 2016 at 3:05 PM

Flag notifications