SAS has stopped working. SAS can not start on window 10

[dear_fisher]

Product:            Base SAS / SAS Foundation

Release:            SAS 9.4 TS1 M4

Operating System: Window 10 X64

Problem:   After Windows was updated on Wednesday 10-4-2017,  SAS System (9.4TS1M4) fails to start on the Windows 10 X64 OS. I have tried the possible solutions below.

http://support.sas.com/kb/43/603.html  (can not apply SAS hot fix and also try environmental

parameter)

http://support.sas.com/kb/54/246.html  (I do not have  Xerox Phaser printer driver )

In addition, I downloaded the latest installment media (still M4) from www.sasdownload.dk and reinstalled the SAS. But the problem still can not be fixed.

 

Just now I checked EG. EG can be used to implement DATA step but not for PROC STEP. The same problem happened when I run PROC.

I guess the problem is due to the update of Window 10 because I can use SAS in September. 

__________________-

updated: added 10-18-2017

1. The problem should be not related to window 10 update

2. uninstall window 10 can not fix the problem

3. reinstalling sas 9.4 can not fix either.

4. This is the first case SAS TS received. TS has provided quite a lot potential solutions but none of them is working.

[Kurt_Bremser]

Revert to the standard Windows method of problem solving:

- reinstall the system from scratch

- reinstall SAS on the "green field" Windows

before doing that, consider

- restoring the system backup from before the update (when updating the system on a SAS server/machine, a system backup is always mandatory).

- removing all SAS software with Control Panel, and removing all SAS trees from the system (in "Program Files", "Program Files (x86)" and in %appdata%); also scan for SAS-related entries in the registry.

[dear_fisher]

Thank you. KurtBremser. I have removed all SAS/related entries before reinstalling SAS. At the moment, it is impossible for me to reinstall window 10 because this is not a private laptop and I am not at home country 😞

[JuanS_OCS]

Hello @dear_fisher,

I completely align with the comments by Kurt. If it is a company's laptop, perhaps you can ask your IT to force to rollback the latest update and block their installation, temporary, at least.

In the meanwhile, I would open a track with SAS Technical Support. Either if the solution must come from Microsoft or SAS, at least you will be able to manage the situation with your company and do all you can.

Sorry not to give you a technical solution, in this case it seems more about communication and manage expectations.

Kind regards,

Juan

[JuanS_OCS]

Hello @dear_fisher,

I completely align with the comments by Kurt. If it is a company's laptop, perhaps you can ask your IT to force to rollback the latest update and block their installation, temporary, at least.

In the meanwhile, I would open a track with SAS Technical Support. Either if the solution must come from Microsoft or SAS, at least you will be able to manage the situation with your company and do all you can.

Sorry not to give you a technical solution, in this case it seems more about communication and manage expectations.

Kind regards,

Juan

[nhvdwalt]

Does the Windows Event Viewer report anything ?

[Damo]

Hi @dear_fisher

You're between good hands with @Kurt_Bremser & @JuanS_OCS, for such issue if you can't rollback (would be the best option, especially as you know it was working before) you may want to be in touch with your local SAS Technical Support.

In the meantime, you may want to install all available hot fixes, who knows...

To assist you, the SAS Hot Fix Analysis, Download and Deployment Tool is the way to go.

Do you check your Event Viewer too?

Good luck.

Cheers,

Damo

[dear_fisher]

@Damo@nhvdwalt@JuanS_OCS@Kurt_Bremser Thanks for your all help. The event logs do not report any SAS-related information. I am communicating with SAS TS. You know, I am in another country and communication becomes difficult because of 9 hours time difference. ... I am also contacting our department IT and see how to roll back the window 10 updates. 

I have tried the possible hotfix and the problem is still occurring. It seems I am the first one to report the problem. 

[Damo]

Hi @dear_fisher

Regarding the Event Viewer, I would focus on the Application and System logs.

Try to reproduce the issue and refresh them (sort the display by the Date and Time column).

Obviously it does not look like a SAS issue as it was working fine prior to the update and it reminds me of the issue introduced by Windows Creator Update as per Problem Note 60323 (Windows 10 Creators Update might cause errors when you invoke SAS® applications or run SAS® programs).

If you are able to roll back that Microsoft update, you should be back on your feet.

Good luck,

Damo

[dear_fisher]

@Damo Thanks. JAVA problem happened to me before after window updates. I fixed it throught installing M4. 

 TS suggests to change to the statement from clicking to SAS 9.4 (English) icon- choose Properties to  

"C:\Program Files\SASHome\SASFoundation\9.4\sas.exe" -CONFIG "C:\Program Files\SASHome\SASFoundation\9.4\nls\en\SASV9.CFG" -sasuser work

 I added "-sasuser work". but it is not working. 

Below please find the information from application. Many thanks.

Log Name: Application
Source: Windows Error Reporting
Date: 10/12/2017 11:22:05 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: D26299.uni.au.dk
Description:
Fault bucket 120846310390, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: sas.exe
P2: 9404.0.22563.55383
P3: 5823d872
P4: StackHash_0278
P5: 10.0.15063.447
P6: a329d3a8
P7: c0000374
P8: PCH_6C_FROM_ntdll+0x00000000000A5EF4
P9:
P10:

Attached files:
\\?\C:\Users\au491605\AppData\Local\Temp\WER51C7.tmp.WERDataCollectionStatus.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER659A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6637.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_sas.exe_c41b5e449879d665eb4cbe0312871e44fedc385_ab4f543b_09729dd0

Analysis symbol:
Rechecking for solution: 0
Report Id: 5e407f4c-0822-404c-b52e-8f4134ac9291
Report Status: 268435456
Hashed bucket: f0919e0bcf991c4bb4f86d4adb13752d
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-10-12T18:22:05.663407800Z" />
<EventRecordID>603059</EventRecordID>
<Channel>Application</Channel>
<Computer>D26299.uni.au.dk</Computer>
<Security />
</System>
<EventData>
<Data>120846310390</Data>
<Data>4</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>sas.exe</Data>
<Data>9404.0.22563.55383</Data>
<Data>5823d872</Data>
<Data>StackHash_0278</Data>
<Data>10.0.15063.447</Data>
<Data>a329d3a8</Data>
<Data>c0000374</Data>
<Data>PCH_6C_FROM_ntdll+0x00000000000A5EF4</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
\\?\C:\Users\au491605\AppData\Local\Temp\WER51C7.tmp.WERDataCollectionStatus.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER659A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6637.tmp.txt</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_sas.exe_c41b5e449879d665eb4cbe0312871e44fedc385_ab4f543b_09729dd0</Data>
<Data>
</Data>
<Data>0</Data>
<Data>5e407f4c-0822-404c-b52e-8f4134ac9291</Data>
<Data>268435456</Data>
<Data>f0919e0bcf991c4bb4f86d4adb13752d</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 10/12/2017 11:21:40 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: D26299.uni.au.dk
Description:
Faulting application name: sas.exe, version: 9404.0.22563.55383, time stamp: 0x5823d872
Faulting module name: ntdll.dll, version: 10.0.15063.447, time stamp: 0xa329d3a8
Exception code: 0xc0000374
Fault offset: 0x00000000000f775f
Faulting process id: 0x3608
Faulting application start time: 0x01d34386f1f0996e
Faulting application path: C:\Program Files\SASHome\SASFoundation\9.4\sas.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 5e407f4c-0822-404c-b52e-8f4134ac9291
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-10-12T18:21:40.902796700Z" />
<EventRecordID>603058</EventRecordID>
<Channel>Application</Channel>
<Computer>D26299.uni.au.dk</Computer>
<Security />
</System>
<EventData>
<Data>sas.exe</Data>
<Data>9404.0.22563.55383</Data>
<Data>5823d872</Data>
<Data>ntdll.dll</Data>
<Data>10.0.15063.447</Data>
<Data>a329d3a8</Data>
<Data>c0000374</Data>
<Data>00000000000f775f</Data>
<Data>3608</Data>
<Data>01d34386f1f0996e</Data>
<Data>C:\Program Files\SASHome\SASFoundation\9.4\sas.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>5e407f4c-0822-404c-b52e-8f4134ac9291</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

[Damo]

Hi @dear_fisher

For such issue, your SAS TS will be better suited than us.

Please let us know the outcome.

Cheers,
Damo

[dear_fisher]

Dear @Damo Thank you.

Best, Y