Add.JobSet():LDAP write error

[Sam2009]

Hi guys need help in this please.

We are having Omnivista 4760 installed in our site
suddenly, All Shoulder Jobs had deleted
I try to recreate jobs like Complete Synch. I get this error:
" Add.JobSet():LDAP write error: Operations error To solve the problem you must set the value of attribute 'nextid' to greater than biggest jobsetid value and restart the scheduler service'

could any one explain what happened?
and where could I modify this parameter ' nextid'

thanks

[E32]

Is this a really old setup where you might have overrun the maximum number of job ids in the database?

[alex]

The only way to re-create deleted Daily and Weekly Jobs (which MUST be present in a scheduler for 4760 to function properly) is to import them from dailyjob.ldif and weekly.ldif files \4760\data\scheduler folder.

[Sam2009]

ok
but how can I change the value of attribute 'nextid' and where???

[Zero]

Hi Sam2009,

From your initial inquiry, on "nextid" as described on the error notification, you may refer to: Directory-->System tab-->nmc-->[server name]-->Servers-->[server name]-->Scheduler-->Specific tab-->nextid parameter. As stated on your logs, you must set the value of "nextid" greater than the biggest jobset (JS) value. Then, restart the NMS Scheduler service. Or, I suggest reboot the OV4760 PC Server.

By the way, refer to the lists of JS and under each JS to locate the biggest JS number. After, add one (1) then set it as the value for the "nextid."



Thanks and regards,
Zero

[Sam2009]

thanks Zero
I modify this parameter and restart the Server.

but i get same error msg.

what is the problem???

[Zero]

Hi Sam2009,

I tried replicating your case but I only got the error notification of:

Add.JobSet(): LDAP write error: Already exists
To solve the problem you must set the value of attribute ‘nextid’ to greater than biggest jobsetid value and restart the scheduler service(Ex: set ‘nextid’ as atleast 301 if biggest jobsetname is JS300)

Based on my testing, the following JS were present under Directory-->System tab-->nmc-->[server name]-->Servers-->[server name]-->Scheduler:
JS0
JS12
JS14
JS16
JS21
JS7

Then, 'nextid' parameter was set to 26. I purposely changed the 'nextid' to 14 to create conflict with the existing JS14 and my stated above notification occured after I scheduled a report definition. Same message was experienced with the same setting of 'nextid' after I manually performed a Complete Synchronization.

With this, I suggest to delete all items under Directory-->System tab-->nmc-->[server name]-->Servers-->[server name]-->Scheduler. Then, perform a Server PC reboot and validate if the problem still persists. Meanwhile, for the Daily and Weekly Jobs, kindly refer to the directory mentioned by alex when recreating/importing the jobs. As additional note, removing the items under Directory-->System tab-->nmc-->[server name]-->Servers-->[server name]-->Scheduler will delete the items on the Scheduler module.

Nonetheless, I observed based on the behavior of OmniVista 4760, particularly on this testing that despite the initial error notification I mentioned, closing the error message and clicking the OK button again to proceed the scheduled report or the complete synchronization, the 'nextid' value will automatically be incremented and the job will be created. Thus, the system adjusts regardless of its limitation.



Thanks and regards,
Zero