Scheduling a SAS programme using SAS Guide 4.3

[AkshayKaru]

Dear Sir/Madame,

Please note that we are having a problem scheduling a job using SAS GUIDE 4.3.

Note:

User 1 can connect to machine 1 and can schedule the job without any error.

User 2 can connect to machine 1 but cannot schedule the job.

User 2 is getting a windows command line screen with the following error message:

log4net:ERROR XmlHierarchyConfigurator: Could not create Appender [EventLogAppender] of type [log4net.Appender.EventLogAppender]. Reported error follows.

System.Security.SecurityException: La source est introuvable mais certains ou l'ensemble des journaux des événements n'ont pas pu faire l'objet d'une recherche.

Journaux inaccessibles: Security

a System.Diagnostics.EventLog.FindSourceRegistration(String source, string machineName, Boolean readonly)

Can you please advise on the issue hat User 2 is having and how we can solve it.

Thanking you in advance

Best Regards,

Karunesh

[Kurt_Bremser]

Schedule the job on the server.

Export all code to a .sas file and run that in batch. Server-side scheduling of SAS batch jobs is much easier and more reliable than the kludge with scheduling projects on the Windows desktop. (Everything you do on a Windows desktop is a kludge by nature)

Note that 4.3 is ancient right now, and might not (reliably) work with a current Windows version. Update to 7.1 ASAP.

[AkshayKaru]

Thanks a lot Kurt for your reply.

Is there any workaround so that we can make the Windows scheduling work in Guide 4.3 as it works for User 1?

Best Regards,

Karunesh

[Kurt_Bremser]

You've said it all in your post. The keyword is "workaround". You're only stumbling from fix to fix. (typical for Windows)

Do something that makes sense and switch to server-side scheduling three days before yesterday. Once you've climbed the initial part of the learning curve, life (as long as it concerns scheduling) will be a breeze.

[SASKiwi]

You can do server-based scheduling in SAS Management Console via a point-and-click interface. It is no more difficult to set up than using EG. The only downside is having to export your code from the EG projects first.

[TomKari]

First, please note that I generally agree with the other posters that scheduling important production work through the Enterprise Guide scheduling system isn't a practice that I would recommend, as there are too many moving parts that are subject to failure.

However, if you want to continue on this, from the diagnostics that you have posted I think you would be best contacting SAS Technical Support. It looks like either something is incorrect in your EG installation, or that User 2's installation on the machine of interest is incorrect. Tech Support would be best placed to help with this.

Tom

[CaseySmith]

From that error, it looks like User 2 may have EG logging turned on and that it is interfering with scheduling since they do not have permission to create a Windows Event Log appender (perhaps they don't have permission to write to the Windows Event log?).

I recommend having User 2 turn off EG logging if not already.  For example, open EG, go to Tools->Options->Application Logging, and uncheck "Enable logging" if checked.  If that does not resolve, try renaming the logging.config file in User 2's %appdata%\SAS\EnterpriseGuide\7.1 location (ex. to logging.configBAK).  Then have User 2 try to schedule again and see if it resolves.

Casey