Skip to main content

SAS Enterprise Guide has encountered a problem and needs to close. Sorry for the inconvenience

Issue:

I had some issues with SAS EG, Whenever I open up SAS EG, I got the issue that EG needs to be restarted or closed. I did try to reinstall it, but didn’t help. Every time I launch it showed only Exit SAS Enterprise Guide and Restart option with SAS Enterprise Guide has encountered a problem and needs to close. Sorry for the inconvenience error message. Issue screenshot below: 


Information in Show Details:

Thanks for the quick reply, detail is shown below

'.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.


-------------------------- Technical Information Follows --------------------------

Exception Details:
----------------------------------------
Exception type:  System.Xml.XmlException
Message:         '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
Source:          System.Xml
Target Site:     Throw

Stack Trace:
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
   at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos)
   at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)
   at System.Xml.Linq.XDocument.Load(String uri, LoadOptions options)
  at SAS.EG.Options.EGOptions.DeserializeOptions(String fileName)
   at SAS.EG.Options.EGOptions.Load()
   at SAS.EG.Options.EGOptions.get_Instance()
   at SAS.EG.ProjectElements.ProjectCollection.SetDataModelOptions()
   at SAS.EG.MainForm.LoadOptions()
   at SAS.EG.MainForm..ctor()
   at SAS.EG.App.Startup(String[] args)
   at SAS.EG.App.Main(String[] args)
   at SAS.EG.EntryPoint.Main(String[] args)

Solution:

This has been resolved doing following:

1. Uninstall all of the SAS programs from control panel.
2. Go to C:\Program Files\SASHOME and rename SASEnterpriseGuide folder to SASEnterpriseGuide_Old. 
3. Go to start then type %appdata% then rename SAS folder to SAS_old
4. Install Enterprise Guide.

Any time a user has issues similar to this you can try steps above.

Comments

Popular posts from this blog

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login   14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...

Insufficient authorization to access prgramname.lst

Issue: I had an issue with batch server. The code runs fine in SAS EG and SAS DI Studio but fails when I run with batchserver. Error seems to be ERROR: Insufficient authorization to access /opt/sasinside/Lev1/SASApp/Sas_Program.lst. NOTE: The SAS System stopped processing this step because of errors. Solution: When you execute on batch mode sas tries to save the output file (Sas_Program.lst) under /opt/sasinside/Lev1/SASApp where is no permission to write. We should add two system options to sasv9_usermods.cfg file to redirect this outputs to another directory. The options are following: -altprint <directory>  -print <directory> Where directory is a directory where you have access to write. You must provide this directory. The directory can be some shared location like: /share/sas/lst. If you decide to add this options these are the steps to follow: 1. Create or choose a driectory where your userid have write access. The userid is the ...