Got a warning message:
...when opening up Sas Studio. I do not pay for it (it has been free to use, have been using it for half a year at least) Not sure what should I do, because I would like to keep using it and I would like to keep all my documents. Is the SAS Studio just a trial version? What do I need to do? Can I not use it after April 4? or should I just ignore it?
Ignore it. Just logged in to SAS On Demand and saw the same message. SAS will update the license and the message will go away.
https://communities.sas.com/t5/SAS-Software-for-Learning/Please-ignore-expiration-warning-for-SAS-OnDemand-for-Academics/m-p/858792
Related
I have recently installed Visual Studio 15.3.1 Community Edition (although I suspect this affects all editions). When doing actions such as
closing SQL .sql file tabs
copying or renaming files
other actions which I can't pinpoint
Visual Studio will freeze or hang for a few seconds or permanantly. It sometimes displays "(Not Responding)" in the title bar, but not always. This is getting really frustrating.
It seems like the Visual Studio feedback system is at fault. Turning it off solved my problem.
Open Visual Studio
Navigate to Help > Privacy > Privacy Settings
Select the "No, I would not like to participate" radio button and click OK
Hopefully whatever bug is causing this issue will be fixed soon and I'll happily participate in the feedback program again!
See this issue posted a lot on the MS forums.
I struggled with it for a while. When editing XAML files, it would always freeze and hang.
Tried many solutions that didn't fixed it. Then, I found the solution that did fix it for me.
I made two changes at the same time, so I can't say for sure which one solved it, but I can guess.
First change, which probably isn't the fix, is that I added the registry keys from this page. They were missing on my system. Page has a lot of detail, but having those keys set properly can't hurt. I noticed in Process Monitor that it was missing on the following regkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\Setup\CachePath
Second change I made, the one I'm guessing solved the issue, was deleting the 17k+ ".TRN" files inside the following directory:
%LocalAppData%\Microsoft\VSApplicationInsights\
On my computer they were in something like the following:
C:\Users\Michael\AppData\Local\Microsoft\VSApplicationInsights\vstelXXX_SOMEGUID
Going back to check now, and after three-or-so hours of work there's another 475 files in that folder. It's producing about four or five .TRN files a minute, all with encrypted data inside. Not going to speculate as to the purpose of it, but I doubt it's anything good or useful. Deleted all those, and the XAML editor in VS now works fine, or at least as well as it ever did. No more 30+ second hangs on a modern twentysome core workstation.
In the recent update of VS 2022, the program suddenly starts freezing (randomly) and the fix for me was to turn off inline hints (the thing that pops up when you double click Ctrl key).
I'm using VS for C++ so I turned it off for C++ specifically
Go to the Tools menu tab -> Options
I know this question was asked few times before but there is still no answer. Is there a way to make c++ editor behave like c# one so that it commits intellisense selection when I press spacebar? I've set member list to be aggressive and it works for all characters in "{}.,:;+-*/%&|^!=<>?##\ " except for space. I can commit with spacebar if I press ctrl+spacebar before but I want it to be more automatic, like in c#. I'm using VS2017 but in 2015 it's the same story.
Refer to your description, I tested it in my VS 2017 and got the same result as yours, I have reported it to the VS Product Team, please check this: VS 2017 > C++ > Intellisense: Committed by press the space bar not works even if set “Disable Aggressive Member List” to “True” and you can vote it or add your comments, then we need to wait for the response from the VS Product Team, thank you for your understanding.
z/OS 1.11, MXG 32.10, SAS 9.3, Batch
I'm working on upgrading MXG to 32.10 with SAS 9.3. While running a CICS report today, I received the message that MXG was taking 20x to 30x CPU processing to decompress messages because the decompression exit was not enabled. To do so, I have to set the macro variable &SMFEXIT to CICS in each run, as follows (I had already assembled and linked the exit and had it available in STEPLIB):
%LET SMFEXIT=CICS
Other options are available but they are more complex and still need set every time I want to access the CICS data. I used it in my program and it worked fine and ran much, much faster.
I figured I'd put this into AUTOEXEC. It didn't work there. AUTOEXEC seemed to process normally with no errors, meaning there was no output at all... It may have had a warning, but that wouldn't show. Only errors display from AUTOEXEC.
I found that I could specify global option ECHOAUTO, along with SOURCE, to display AUTOEXEC processing. That has to be done either in CONFIG or as an invocation parameter. I tried both options and neither worked. I purposefully misspelled it in CONFIG and that threw an error, so I know it was being found. SAS lists the invocation parameters in SASLOG, so ECHOAUTO and SOURCE were both listed there. I received no indication that those options were working and AUTOEXEC processing just didn't go to SASLOG.
I ran PROC OPTIONS RESTRICT and nothing was restricted.
All the messages kept telling me to talk to the System Administrator. I found nothing that told me who that was, what they were supposed to do or how to find out... I sit by our System Administrator and he was no help with this because I'm the one that knows SAS. Or, I thought I did...
So, how do I set &SMFEXIT to CICS globally? Bonus for information as to why ECHOAUTO totally ignored me and information about the System Administrator. Also, where can I find information about the limitations of AUTOEXEC as in what can or cannot be there. Better yet, tell me in what guide I can find this information myself. I searched for a long time and couldn't find any of that. SAS documents are many. SAS information about these questions is either scarce or just impossible to find.
Thanks...
UPDATE: I am considering setting up my MXG proc so that it has a concatenation that throws in this control card ahead of the MXG/SAS programs. Seems like an awful hack... Still would like other options and answers to the ancillary issues IAAP. Thanks again.
Ah yes, the head slap... Every issue above is easily explained by the fact that AUTOEXEC is not being called! Variables aren't set. Logic isn't added to the SASLOG.
We use Windows SAS, too. We use AUTOEXEC.SAS to extensively initialize that environment. On the other hand, on z/OS, we use JCL and parameters to initialize SAS without using AUTOEXEC, so it has never been implemented.
On z/OS, the AUTOEXEC global option defaults to the SASEXEC ddname. I added the appropriate JCL to my MXG PROC to point to my AUTOEXEC member. Voila. My variable is set. The logic is available in SASLOG. Everything appears to be working, all with one simple root cause.
Thanks...
I am using SQL Server Compact Edition.
One of the column size of my table is more than 500.
When I am Selecting from this table I am getting this error in visual studio:
multiple steps oledb operation generated
How can I avoid this error?
This may happen when you pass an unexpected value in one of your DB operation (say you pass NULL to a non-NULL field for example).
I would expect the error message to be longer and more informative (did you truncate it ?). In the current situation, that's pretty much all we can say about it.
A quick google search gave me that link which may help.
I'm trying to debug a curious problem where by one coldfusion 8 instance is giving me an error (numeric or value error: character to number conversion error ORA-06512: at line 1) but with exactly the same code another coldfusion 8 instance isn't throwing the same error.
They are both on 8,0,1,195765 Enterprise, both running on Windows 2003.
I can't imagine why they might be using different drivers unfortunately I can't (without a huge faf) have them point to the same database.
I can (and have) modified the code so the error is no longer occurring, but I'm now trying to figure out what was going on.
So how do I find out what oracle jdbc driver ColdFusion is using, I found this blog post:
http://rahulnarula.blogspot.co.uk/2009/04/getting-oracle-jdbc-driver-version-info.html
But that's only returning me no driver found.
If it helps both databases are using oracle 10g and both databases appear to be set up the same way (though I haven't ruled out that there maybe something there)
You could try looking inside macromedia_drivers.jar for this file:
\macromedia\jdbc\oracle\oracle.properties
It looks like it contains the build ID for the Oracle driver.
Another approach would just be to diff macromedia-drivers.jar using beyond-compare or similar. It may not tell you what version the drivers are, but it will tell you whether they are the same.
Also, does the short, initial code block in the linked article not work? That ought to return something for the Macromedia drivers.
Barny