topic Re: red X in error tab in SAS Programming

red X in error tab

Ronein — Mon, 20 Oct 2025 09:58:51 GMT

Hello

I am running a sas program and get 0 errors and 0 warnings.

However, there is red X in program tab and also rex X in error tab

Re: red X in error tab

Kurt_Bremser — Mon, 20 Oct 2025 10:45:49 GMT

"The quoted string currently processed has become more than 262 characters long“

Fix that first (unbalanced quotes or similar)

Re: red X in error tab

Ronein — Mon, 20 Oct 2025 11:51:09 GMT

But how can I know where did it occur in the program??

Re: red X in error tab

Ronein — Mon, 20 Oct 2025 11:52:55 GMT

If Igo to log what word should I search there to find the data set where it's creation cause the problem?

Re: red X in error tab

PaigeMiller — Mon, 20 Oct 2025 12:14:34 GMT

Maxim 2

Re: red X in error tab

Quentin — Mon, 20 Oct 2025 13:32:11 GMT

To start with I would search for "ERROR".

The red X on the error tab is not a problem. It is always there, as a visual icon to indicate it is the error tab.

The red X on the program tab is a concern. It indicates (I believe) that an error was generated the last time code from the program was submitted. I agree, it's surprising to see a red X on the program tab while the error tab reports 0 errors.

I wonder if it's possible you have turned off log messages at some point (e.g. via PROC PRINTTO or similar)? Or if an error is being generated by EG pre-code or post-code which is not shown is the log? Those are just guesses as to possible causes. I don't know the actual condition that EG uses to flag the program tab with an X.

One thing you could try would be to run a step that does not generate errors, and confirm that the red X on the program tab goes away, then run your full program again, and see if it returns.

Re: red X in error tab

Kurt_Bremser — Mon, 20 Oct 2025 16:57:17 GMT

@Ronein wrote:
But how can I know where did it occur in the program??

Read the log from top down; there is also a text search function available, IIRC. But I STRONGLY recommend to clean up your code from the start, step by step. See Maxim 25.

Re: red X in error tab

Ksharp — Tue, 21 Oct 2025 01:48:05 GMT

For the issue mentioned by Kurt, you could try option:
option noquotelenmax;

But look from your screen shot, it more looks like a sas bug, I suggest you to contact with sas technical support.

Re: red X in error tab

Kurt_Bremser — Fri, 24 Oct 2025 17:45:58 GMT

And make sure that your code does nowhere contain the word ERROR (in capitals) and that there is nothing that writes this word to the log (e.g. a PUT statement where the data contains ERROR).

Re: red X in error tab

Tom — Fri, 24 Oct 2025 18:00:31 GMT

@Kurt_Bremser wrote:

And make sure that your code does nowhere contain the word ERROR (in capitals) and that there is nothing that writes this word to the log (e.g. a PUT statement where the data contains ERROR).

I certain hope that SAS/Studio is not so simple minded as to treat that as an indication of an error. And I have never seen it do that.

Re: red X in error tab

Kurt_Bremser — Fri, 24 Oct 2025 18:04:25 GMT

I think we're dealing with EG here, based on the screenshot. And I think I had something similar happen to me quite some time ago with EG.