07-13-2022
matthew-masters
Calcite | Level 5
Member since
07-13-2022
- 4 Posts
- 1 Likes Given
- 0 Solutions
- 0 Likes Received
-
Latest posts by matthew-masters
Subject Views Posted 1320 07-13-2022 12:15 PM 1322 07-13-2022 12:14 PM 1324 07-13-2022 12:12 PM 1358 07-13-2022 11:05 AM -
Activity Feed for matthew-masters
- Liked Re: SAS Studio Fails to Save Certain Scripts to Disk (Encoding?) for Reeza. 07-13-2022 02:37 PM
- Posted Re: SAS Studio Fails to Save Certain Scripts to Disk (Encoding?) on SAS Programming. 07-13-2022 12:15 PM
- Posted Re: SAS Studio Fails to Save Certain Scripts to Disk (Encoding?) on SAS Programming. 07-13-2022 12:14 PM
- Posted Re: SAS Studio Fails to Save Certain Scripts to Disk (Encoding?) on SAS Programming. 07-13-2022 12:12 PM
- Posted SAS Studio Fails to Save Certain Scripts to Disk (Encoding?) on SAS Programming. 07-13-2022 11:05 AM
-
Posts I Liked
Subject Likes Author Latest Post 1
07-13-2022
12:15 PM
It is a SAS Studio installation, but I think the issue may be a bit too vague to solve here-- I will reach out to support as you suggest. Thanks!
... View more
07-13-2022
12:14 PM
I think you're right-- I was hoping that there was a simple solution that I was missing, or that this was a common issue (albeit I didn't see any existing topics on this). I'll reach out to support directly, thanks!
... View more
07-13-2022
12:12 PM
Thanks for you reply. The SAS code is always edited in the SAS Studio environment, never in other editors. The only thing that comes from other document types is format or labeling data-- these codebooks were created decades ago and saved in these formats. It would be possible, but entirely too time-consuming, to type information from these codebooks out by hand into the SAS editor, but my guess is that copying and pasting the information is somehow corrupting or introducing an error that the SAS Server is unable to solve. I may follow others' suggestions and reach out to support directly. Thanks!
... View more
07-13-2022
11:05 AM
A few of my colleagues and I have run into issues saving scripts while using SAS Studio. When saving (and occasionally when running) certain scripts, one of three things happens: The script saves/runs successfully with no error messages An error message pops up, and the file is not saved or the code not run: "null" error prompt "Unknown submission error" error prompt The script appears to save properly, but the file is in fact only partially saved. When #3 above happens, it's easy to lose most of your script without knowing that there's an issue. This is obviously not good, and we end up spending more time backing up every file through some other method (like copying and pasting to Notepad) before attempting to save. We think we may have identified that the issue is related to text encoding, as certain formats or labels are created by copying and pasting text from other files like Excel, Word, or PDF documents. These errors do not occur with all scripts. Is this some sort of text encoding issue? It appears SAS Studio is using UTF-8, but saving the script through Notepad using UTF-8 encoding and the .sas extension does not fix the issue. Thanks, Matt
... View more