My company has recently installed Centreware Web 6.5 and wants to use the Configuration Sets and Policies to manage our printer fleet. I've set them both up but when I go to run the policy I get a short loading icon and then nothing happens. When I go to the results tab it shows that nothing has ran but on our print server i'm showing an error from the xerox scheduler. Has anyone else had issues with running configuration policies?
Here is the error: Exception caught
Class Name = Xerox.CWW.CWWLib.SchedConfigSet
Error = System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Security.SecurityException: The source was not found, but some or all event logs could not be searched. Inaccessible logs: State.
at System.Diagnostics.EventLog.FindSourceRegistration(String source, String machineName, Boolean readOnly, Boolean wantToCreate)
at System.Diagnostics.EventLog.SourceExists(String source, String machineName, Boolean wantToCreate)
at System.Diagnostics.EventLog.SourceExists(String source)
at DBVersionDetect.EventLogManager.WriteLog(String pSource, String pMessage, Nullable`1 pEventID, Nullable`1 pType, Nullable`1 pVerbosity) in c:\XGS-SDI\XOS\Device Management\Version\XDMCWW\6.5\Common\CWWLib\Mainline\Source\EventLogManager.cs:line 22
at DBVersionDetect.EventLogManager.WriteLogInfo(String pMessage, String pSource, Int32 pEventID, Verbosity pVerbosity) in c:\XGS-SDI\XOS\Device Management\Version\XDMCWW\6.5\Common\CWWLib\Mainline\Source\EventLogManager.cs:line 77
at Xerox.CWW.CWWLib.SchedConfigSet.ConfigSet_WakeUpEvent(String strParam, Int32& devicesAttempted, Int32& devicesAnswered, Boolean& success) in c:\XGS-SDI\XOS\Device Management\Version\XDMCWW\6.5\Common\CWWLib\Mainline\Source\SchedConfigSet.cs:line 256
at Xerox.CWW.CWWLib.SchedulerEvent.wakeUp(String strParam, String eventName) in c:\XGS-SDI\XOS\Device Management\Version\XDMCWW\6.5\Common\CWWLib\Mainline\Source\SchedulerEvent.cs:line 507
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object parameters, Object arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
at Xerox.Scheduler.ThreadPool.RunEventInProc(ScheduledEvent workItem, AutoResetEvent workerTermEvent)
Thanks in advance
Solved! Go to Solution.
I see no one has responded to this post yet. So, at this point I would recommend contacting your local Xerox Support Department to speak with a Product Specialist for more assistance. Please call 1-800-821-2797.
We have been in the process of getting this utility to work with our fleet of Xerox devices as well. We found this same exact roadblock when trying to apply some configuration policies/run configuration audits in the CWW web interface. Here is what I found that at least stopped this particular error.
I'm not a programmer at heart but know enough to probably be dangerous -- so I have to read exception error message stack traces like these a few times to know exactly what it's trying to tell me. Here, it's a security issue. After googling the "The source was not found...Inaccessible logs..." line, I discovered that the program was trying to write something to the Windows event log but didn't have permissions to do so. That requires a Windows registry modification (please ensure you have a backup of it before poking around).
For this particular instance on the CWW server, launch regedit as an admin, navigate to HKLM\System\CurrentControlSet\Services\EventLog. In the tree, expand the EventLog key. Right click the State subkey and click Permissions. In the Permissions for State box, click Advanced toward the bottom. Change the owner to yourself, and then add the "NETWORK SERVICE" account with full control to that key. Restart the IIS services on that machine, then try to run the configuration policy again. It should at least run without throwing the exception you and I were getting. Hope this helps!
I wish I could give you a thousand Kudos! It's been such a headache getting this program up and running. But your resolution was 100% correct. I can't thank you enough!