Anonymous_User Absent Member.
Absent Member.
266 views

Generic file driver startup error

I deployed the Generic File Driver to test it out based on
recommendations from quite a few people. I deployed the driver based on
the instructions. This is a brand-new, fully patched eDir/IDM 4.0.2
installation on a new server.

When I try to start the driver I get the following message:
Message: <description>java.lang.IllegalArgumentException: No enum
constant
info.vancauwenberge.filedriver.shim.FileDriverPublicationShim.GenerateCommnd.modify</description>
<exception class-name="java.lang.IllegalArgumentException">
<message>No enum constant
info.vancauwenberge.filedriver.shim.FileDriverPublicationShim.GenerateCommnd.modify</message>
<stack-trace>java.lang.IllegalArgumentException: No enum constant
info.vancauwenberge.filedriver.shim.FileDriverPublicationShim.GenerateCommnd.modify
at java.lang.Enum.valueOf(Unknown Source)
at
info.vancauwenberge.filedriver.shim.FileDriverPublicationShim$GenerateCommnd.valueOf(FileDriverPublicationShim.java:1)
at
info.vancauwenberge.filedriver.shim.FileDriverPublicationShim.init(FileDriverPublicationShim.java:478)
at com.novell.nds.dirxml.engine.Publisher.run(Publisher.java:497)
at java.lang.Thread.run(Unknown Source)

If I change the "Generated command" Publisher parameter to Add or
Dynamic then the GenerateCommnd.modify changes to GenerateCommnd.add or
GenerateCommnd.dynamic appropriately but the rest of the error is the same.
I even deployed a whole new driver leaving it 100% default and I get the
same error.
Any thoughts on what's happening here?
Labels (1)
0 Likes
15 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Generic file driver startup error

Which version of this shim are you using exactly? It's a great tool, and
the last one I used was 0.6, but I was using XML input files so perhaps
choosing that made me not need the values you are needing. My
currently-running driver config does not have those options defined as far
as I can tell, but again if the options do not apply to my XML input
method that may be normal.


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Knowledge Partner
Knowledge Partner

Re: Generic file driver startup error

On 5/14/2014 6:12 AM, ab wrote:
> Which version of this shim are you using exactly? It's a great tool, and
> the last one I used was 0.6, but I was using XML input files so perhaps
> choosing that made me not need the values you are needing. My
> currently-running driver config does not have those options defined as far
> as I can tell, but again if the options do not apply to my XML input
> method that may be normal.


I used 0.0.6 as well, but on CSV's Pub channel only.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Generic file driver startup error

On 5/14/2014 8:11 AM, Geoffrey Carman wrote:
> On 5/14/2014 6:12 AM, ab wrote:
>> Which version of this shim are you using exactly? It's a great tool, and
>> the last one I used was 0.6, but I was using XML input files so perhaps
>> choosing that made me not need the values you are needing. My
>> currently-running driver config does not have those options defined as
>> far
>> as I can tell, but again if the options do not apply to my XML input
>> method that may be normal.

>
> I used 0.0.6 as well, but on CSV's Pub channel only.
>
>

That's me - CSVs on Pub channel only. I just can't even get the driver
to start even with all defaults.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Generic file driver startup error

Phil Cook wrote:

>
> That's me - CSVs on Pub channel only. I just can't even get the driver to start even with all defaults.


Have you tried editing the driver XML

1. Get Driver Properties
2. Click Driver Configuration, then Driver Parameters
3. Click Edit XML

Locate:

<definition display-name="Generated command:" name="pub_command" type="enum">
<description>What command should be generated on the publisher channel? 'add','modify' or dynamically determined by the driver.
In Dynamic mode, the driver will first generate a query based on association. If One instance is returned, it will generate a modify, otherwise it will generate an add. This gives in certain scenarios more freedom to use the filter merge authority setting.
Note: modify events will generate a query-back when a merge is needed. This can have serious performance consequences! For this reason, using 'modify' is not advised.</description>
<enum-choice display-name="Add (default)">add</enum-choice>
<enum-choice display-name="Modify">modify</enum-choice>
<enum-choice display-name="Dynamic">dynamic</enum-choice>
<value>add</value>
</definition>

Change to:

<definition display-name="Generated command:" name="pub_command" type="enum">
<description>What command should be generated on the publisher channel? 'add','modify' or dynamically determined by the driver.
In Dynamic mode, the driver will first generate a query based on association. If One instance is returned, it will generate a modify, otherwise it will generate an add. This gives in certain scenarios more freedom to use the filter merge authority setting.
Note: modify events will generate a query-back when a merge is needed. This can have serious performance consequences! For this reason, using 'modify' is not advised.</description>
<enum-choice display-name="Add (default)">ADD</enum-choice>
<enum-choice display-name="Modify">MODIFY</enum-choice>
<enum-choice display-name="Dynamic">DYNAMIC</enum-choice>
<value>ADD</value>
</definition>

Click Apply, deploy and restart.


--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Generic file driver startup error

On 5/14/2014 8:40 AM, Alex McHugh wrote:
> Phil Cook wrote:
>
>>
>> That's me - CSVs on Pub channel only. I just can't even get the driver to start even with all defaults.

>
> Have you tried editing the driver XML
>
> 1. Get Driver Properties
> 2. Click Driver Configuration, then Driver Parameters
> 3. Click Edit XML
>
> Locate:
>
> <definition display-name="Generated command:" name="pub_command" type="enum">
> <description>What command should be generated on the publisher channel? 'add','modify' or dynamically determined by the driver.
> In Dynamic mode, the driver will first generate a query based on association. If One instance is returned, it will generate a modify, otherwise it will generate an add. This gives in certain scenarios more freedom to use the filter merge authority setting.
> Note: modify events will generate a query-back when a merge is needed. This can have serious performance consequences! For this reason, using 'modify' is not advised.</description>
> <enum-choice display-name="Add (default)">add</enum-choice>
> <enum-choice display-name="Modify">modify</enum-choice>
> <enum-choice display-name="Dynamic">dynamic</enum-choice>
> <value>add</value>
> </definition>
>
> Change to:
>
> <definition display-name="Generated command:" name="pub_command" type="enum">
> <description>What command should be generated on the publisher channel? 'add','modify' or dynamically determined by the driver.
> In Dynamic mode, the driver will first generate a query based on association. If One instance is returned, it will generate a modify, otherwise it will generate an add. This gives in certain scenarios more freedom to use the filter merge authority setting.
> Note: modify events will generate a query-back when a merge is needed. This can have serious performance consequences! For this reason, using 'modify' is not advised.</description>
> <enum-choice display-name="Add (default)">ADD</enum-choice>
> <enum-choice display-name="Modify">MODIFY</enum-choice>
> <enum-choice display-name="Dynamic">DYNAMIC</enum-choice>
> <value>ADD</value>
> </definition>
>
> Click Apply, deploy and restart.
>
>

Thanks for the reply. Tried it, here's the result:
<description>Parameter tagName='pub_command',
displayName='Generated command:' has illegal value 'ADD'. Legal values
are [[string (data type)] and [value? (once or not at all)] and
not[null, '' (empty string)] and ['add' or 'dynamic' or
'modify']].</description>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Generic file driver startup error

Phil Cook wrote:

> Thanks for the reply. Tried it, here's the result:
> <description>Parameter tagName='pub_command', displayName='Generated command:' has illegal value 'ADD'. Legal values are [[string (data type)] and [value? (once or not at all)] and not[null, '' (empty string)] and ['add' or 'dynamic' or 'modify']].</description>



Where did that message come from? the Driver startup or is that from Designer somehow?

I only guessed that because when looking at the source, it looked like these constants were supposed to be all in uppercase.

Try posting a comment on the cool solutions entry - the developer seems to respond there.

https://www.netiq.com/communities/cool-solutions/wp-content/uploads/sites/2/2013/01/GenFileDriver_0_6.zip is the previous version (I believe)

--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Generic file driver startup error

On 5/14/2014 6:12 AM, ab wrote:
> Which version of this shim are you using exactly? It's a great tool, and
> the last one I used was 0.6, but I was using XML input files so perhaps
> choosing that made me not need the values you are needing. My
> currently-running driver config does not have those options defined as far
> as I can tell, but again if the options do not apply to my XML input
> method that may be normal.
>
>

I'm using the latest available - v0.7, package version 0.6. I'm using
CSV files. I had high hopes for this driver but this sort of issue (the
driver won't even start) perhaps indicates it's not ready for
prime-time. My biggest concern is supportability if we move forward with
it - apparently not many people are using it and so there's limited
places to go for assistance. Bummer.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Generic file driver startup error

On 5/13/2014 5:30 PM, Phil Cook wrote:
> I deployed the Generic File Driver to test it out based on
> recommendations from quite a few people. I deployed the driver based on
> the instructions. This is a brand-new, fully patched eDir/IDM 4.0.2
> installation on a new server.
>
> When I try to start the driver I get the following message:
> Message: <description>java.lang.IllegalArgumentException: No enum
> constant
> info.vancauwenberge.filedriver.shim.FileDriverPublicationShim.GenerateCommnd.modify</description>
>
> <exception class-name="java.lang.IllegalArgumentException">
> <message>No enum constant
> info.vancauwenberge.filedriver.shim.FileDriverPublicationShim.GenerateCommnd.modify</message>
>
> <stack-trace>java.lang.IllegalArgumentException: No enum constant
> info.vancauwenberge.filedriver.shim.FileDriverPublicationShim.GenerateCommnd.modify
>
> at java.lang.Enum.valueOf(Unknown Source)
> at
> info.vancauwenberge.filedriver.shim.FileDriverPublicationShim$GenerateCommnd.valueOf(FileDriverPublicationShim.java:1)
>
> at
> info.vancauwenberge.filedriver.shim.FileDriverPublicationShim.init(FileDriverPublicationShim.java:478)
>
> at com.novell.nds.dirxml.engine.Publisher.run(Publisher.java:497)
> at java.lang.Thread.run(Unknown Source)
>
> If I change the "Generated command" Publisher parameter to Add or
> Dynamic then the GenerateCommnd.modify changes to GenerateCommnd.add or
> GenerateCommnd.dynamic appropriately but the rest of the error is the same.
> I even deployed a whole new driver leaving it 100% default and I get the
> same error.
> Any thoughts on what's happening here?


I just imported this driver, and cannot find these settings, Generated
command. I am using Package version 0.0.4. What are you using?

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Generic file driver startup error

Geoffrey Carman wrote:

>
>
> I just imported this driver, and cannot find these settings, Generated command. I am using Package version 0.0.4. What are you using?


he said he was using package version 0.0.6 (the latest)

--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Generic file driver startup error

On 5/14/2014 8:29 AM, Alex McHugh wrote:
> Geoffrey Carman wrote:
>
>>
>>
>> I just imported this driver, and cannot find these settings, Generated command. I am using Package version 0.0.4. What are you using?

>
> he said he was using package version 0.0.6 (the latest)
>

Anyone know where I can download previous versions to see if I can get
them to work? I'm needing the metadata feature so it looks like I need a
minimum of .5 (pkg .4).
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Generic file driver startup error

On 5/14/2014 8:40 AM, Phil Cook wrote:
> On 5/14/2014 8:29 AM, Alex McHugh wrote:
>> Geoffrey Carman wrote:
>>
>>>
>>>
>>> I just imported this driver, and cannot find these settings,
>>> Generated command. I am using Package version 0.0.4. What are you
>>> using?

>>
>> he said he was using package version 0.0.6 (the latest)
>>

> Anyone know where I can download previous versions to see if I can get
> them to work? I'm needing the metadata feature so it looks like I need a
> minimum of .5 (pkg .4).


I have your email, I can send you 0.0.4.


0 Likes
Knowledge Partner
Knowledge Partner

Re: Generic file driver startup error

Phil Cook wrote:

> Anyone know where I can download previous versions to see if I can get them
> to work? I'm needing the metadata feature so it looks like I need a minimum
> of .5 (pkg .4).


check your mail...
0 Likes
Knowledge Partner
Knowledge Partner

Re: Generic file driver startup error

On 5/14/2014 8:29 AM, Alex McHugh wrote:
> Geoffrey Carman wrote:
>
>>
>>
>> I just imported this driver, and cannot find these settings, Generated command. I am using Package version 0.0.4. What are you using?

>
> he said he was using package version 0.0.6 (the latest)


You act like I read the nonsense Phil spouts. 🙂 Thanks for noticing.



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Generic file driver startup error

On 5/13/2014 5:30 PM, Phil Cook wrote:
> I deployed the Generic File Driver to test it out based on
> recommendations from quite a few people. I deployed the driver based on
> the instructions. This is a brand-new, fully patched eDir/IDM 4.0.2
> installation on a new server.
>
> When I try to start the driver I get the following message:
> Message: <description>java.lang.IllegalArgumentException: No enum
> constant
> info.vancauwenberge.filedriver.shim.FileDriverPublicationShim.GenerateCommnd.modify</description>
>
> <exception class-name="java.lang.IllegalArgumentException">
> <message>No enum constant
> info.vancauwenberge.filedriver.shim.FileDriverPublicationShim.GenerateCommnd.modify</message>
>
> <stack-trace>java.lang.IllegalArgumentException: No enum constant
> info.vancauwenberge.filedriver.shim.FileDriverPublicationShim.GenerateCommnd.modify
>
> at java.lang.Enum.valueOf(Unknown Source)
> at
> info.vancauwenberge.filedriver.shim.FileDriverPublicationShim$GenerateCommnd.valueOf(FileDriverPublicationShim.java:1)
>
> at
> info.vancauwenberge.filedriver.shim.FileDriverPublicationShim.init(FileDriverPublicationShim.java:478)
>
> at com.novell.nds.dirxml.engine.Publisher.run(Publisher.java:497)
> at java.lang.Thread.run(Unknown Source)
>
> If I change the "Generated command" Publisher parameter to Add or
> Dynamic then the GenerateCommnd.modify changes to GenerateCommnd.add or
> GenerateCommnd.dynamic appropriately but the rest of the error is the same.
> I even deployed a whole new driver leaving it 100% default and I get the
> same error.
> Any thoughts on what's happening here?

To all: first of all, thank you all for jumping in so quickly to help.
The author of this driver sent me an updated jar file which fixed it.
He'll be updating the CoolSolutions site shortly.
Yeah community support!

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.