Hi @AkshayKaru  Contact SAS Tech Support - They are better equipped to help with your issue   Hope this helps, Ahmed   ... View more

And you should press for the upgrade to 9.4 ASAP. Many issues you report to SAS TS will get you a "upgrade first", because 9.2 is down to limited support, and lots of problems have been fixed in the meantime in subsequent releases. Not even mentioning all the advances in usability and functionality. ... View more

A long shot is to verify the data is actually an XLS file. I have seen a fair amount of code where people save files in different formats with the XLS or XLSX so the spreadsheet program will open them by default. See if you can open the file in a plain text editor such as Notepad and actually read results as text. If you see lots of commas  the file may be CSV, if you see HTML tags then it may actually be HTML.   ... View more

Looks like your content server is down / has crashed. Submit the problem to SAS technical support. ... View more

If the tables are hard coded in program then you need to use @andreas_lds suggestion. If they were dropped in the project flow then you can go to Tools>Project Maintenance (might be helpful). But I'm not sure if that option is available in EG 4.3. ... View more

Your best bet is opening a track with SAS technical support ASAP, but they will most probably advise you to upgrade. 4.3 is simply out of any current support. ... View more

Have a look at the SAS System Requirements doc for your operating system and SAS version e.g. System Requirements for SAS® 9.4 Foundation for Linux for x64 - inside those PDFs you will find a section for SAS/ACCESS Interface to DB2 (assuming that is what you are using to access DB2 from SAS).     ... View more

We'd likely suggest exactly what you've mentioned @Kurt_Bremser. It's got a very well understood amount of time you need to invest to resolve the problem. Finding what broke this system could be a significantly bigger time investment. ... View more

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 ... View more

You have a SAS metadata environment? You might look into metadata-bound libraries, which allow you to restrict who can see the tables and disallows any access attempts that try to circumvent the metadata-provided access.  See this blog post for details. ... View more