SAS EG debugger doesn't work

[mlm155]

I am trying to use the debugger with a data step (trying p301d01 and p301103). Debugger always gives an error "Unknown error occurred during command submission"

I successfully used the debugger earlier. Tried restarting SAS but no result.

Any suggestion will be appreciated.

Thanks

[KaueMAlmeida]

I can't imagine some error during debugging process.

At Enterprise Guide you must press the F5 key at your keyboard. It will open the Data Step Debugger. After this, you should see something like the picture below.

The Enterprise Guide compiles your code in real time, during the execution process. The debugger runs your code at the same time that reads your tables and their data.

You also can write some conditionals (e.g. if/else) statements to interact with your data using the _N_ and the _ERROR_  for checking something at the code, for example.

Anyway, could you post a picture from the error?

[Kevin_Leonte]

I'm having the same exact issue with the same exact program (p301d01) used in the Advanced Programming e-course. 

The program runs fine without the debugger, but as soon as you run the debugger on either of the 2 datasteps in that program you get the error "Unknown error occurred during command submission" and the only option is to click the close button which closes the debugger.  

[SASKiwi]

This is really only a problem SAS Tech Support can investigate. What version of EG are you using?

[Kevin_Leonte]

@SASKiwi .  Thanks for the feedback.  It's not that big of an issue for me to really go down the SAS tech support road. I've been a SAS programmer for 25+ years and I've lived without a debugger for those many years... I just wanted to reply and point out that this is happening to more than one user.  😁

BTW, I'm using EG version 7.15 (7.100.5.5850) (64-bit).

Happy New Year!

Kevin

[SASKiwi]

@Kevin_Leonte - Likewise. I never use it either but I'm keen to see bugs fixed. Happy New Year to you too!

[Panagiotis · Accepted solution]

It could be a global option you have set in Enterprise Guide. Execute this procedure:

proc options option=source;
run;

Then look at the log. If the log says: NOSOURCE Does not write program source statements to the SAS log, then that is the issue. When this option is turned on it causes the error with the debugger.

It could because of the SOURCE|NOSOURCE option: https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/lesysoptsref/n0gnz7tqcszvbpn1umls21zdkw62....

You can fix it by changing the option back to SOURCE:

options source;

Once you do that confirm you have changed it using the OPTIONS procedure above. Then try to use the debugger again.

Let me know if that works.

- Peter

[Kevin_Leonte]

@Panagiotis 

Yes, that was it!  

In the SAS course the first program which sets up the course data, issues an options nosource command at the top of the program.  I just added the options source command to the end of the first program (which is renamed to autoexec so it prompts to run every time the project is opened) and then the debugger worked.

Thanks and Happy New Year!

Kevin

[Panagiotis]

Glad that worked!

You are correct that the setup program changes that option and causes that error. That has been fixed in the setup program. Thank you for letting us know!

Happy new year to you as well!

- Peter

[mlm155]

Thanks for your response.

I just tried to do this -- somehow my whole project was giving errors so downloaded everything again and when I tried the debugger worked without me having  to try anything else.

Thanks & Happy new year to everyone!

[Panagiotis]

Glad to hear it worked! We went ahead and updated the program and fixed it this morning and pushed the changes. So when you redownloaded everything you received the updated program with the fix. Glad it works for you!

- Peter