About CaseySmith

CaseySmith · ‎06-15-2017

I suggest starting with the Bitbucket documentation. For example, here is how you would clone a repository to your local machine: https://confluence.atlassian.com/get-started-with-bitbucket/clone-a-repository-861178563.html After making changes to your .sas files in the locally cloned repository using EG, here is how you could commit the changes and push them back to Bitbucket: https://confluence.atlassian.com/get-started-with-bitbucket/push-code-to-bitbucket-861185309.html Or you could commit the changes directly from within EG (as documented in the paper you referenced), then push using Git command-line (as demonstrated in previous link), or using a Git GUI, such as Git Extensions, SourceTree, etc. Again, working with cloud-based Git repositories (such as Bitbucket, Github, etc.) in EG is almost identical to any other remote Git repository. You clone it to the client, work out of your locally cloned repository, commit changes to your locally cloned repository, then push the commits back to your remote origin repository (Bitbucket in this case). Casey

CaseySmith · ‎06-15-2017

Hi @sasprofile, You work with a Bit Bucket (or Github, etc) project the same as you do any other remote Git repository. You will need to clone the repository to your local machine (using external tool), work on (edit, submit, etc) the .sas files out of your locally cloned repository using EG, commit changes to your .sas files in your local repository from within EG (or external tool), then push the commits back to your remote repository when ready to "share with the world" (colleagues). Casey

CaseySmith · ‎06-14-2017

Thanks for your answers. Those versions are compatible, so it should be able to work. And if you can use the same Enterprise version of SAS Studio from the same machine, but you don't see the Task Type filter, that confirms EG is not detecting the Enterprise SAS Studio instance for some reason. At this point, I too suggest contacting Tech Support. As Sam noted, EG retrieves the URL for the Enterprise Edition of SAS Studio from metadata, which is normally in this location in SAS Management Console: Plug-ins tab->Application Management folder->Configuration Manager->SAS Application Infrastructure->SAS Studio Mid-Tier 3.5 You could check to make sure that is defined and the URL is set properly (points to the correct Enterprise Edition of SAS Studio), or Tech Support could help you with this. Tech Support may also request an EG log to help debug. They should be able to assist.

CaseySmith · ‎06-13-2017

Hi @PaalNavestad, A few questions... 1) What exact version of EG (listed in Help->About) do you have? 2) What exact version of Enterprise Edition of SAS Studio do you have? 3) Just to confirm (since it sounds like what you were saying), you are able to use your Enterprise Edition of SAS Studio just fine from a browser on the same client machine as EG? 4) When you click Tasks (menu)->Browse... in EG, do you see a Type filter with Built-in and SAS Studio checkboxes (as in screenshot below)? Casey

CaseySmith · ‎06-13-2017

I tried unsuccessfully to reproduce the issue you described using EG 7.11 HF5. (The issue I was thinking of was different.) Installing the latest 7.11 hot fix (U23005) or upgrading to latest version (currently 7.13 HF5) might resolve your issue.

CaseySmith · ‎06-12-2017

What is the exact version of EG (in Help->About dialog) you are using? This looks like an issue that was introduced briefly and fixed in a subsequent update.

CaseySmith · ‎06-08-2017

Disregard my response below, that was before seeing the full callstack you just posted. From the callstack you just sent, I see the error is occurring when attempting to make a connection to your local SAS server. The first thing I'd do is try to run SAS (Display Manager) directly from the Windows start menu (or C:\Program Files\SASHome\SASFoundation\9.4\sas.exe). If SAS comes up fine in that case (and able to submit something simple, ex. "%put hello;"), then I suggest trying to re-register SAS with this command: C:\Program Files\SASHome\SASFoundation\9.4\sas.exe -regserver If still no luck, you can use ITConfig2.exe discussed below to test Local connection (change to SAS Workspace Server and select COM as the Connection Protocol, then press Test button). That looks like a failure trying to connect to a SAS metadata server. Check your active profile (in EG's Tools->Connections) to make sure your active profile is configured and set as expected. If you are intending for EG to connect to your local SAS, make sure "<do not use a profile>" is selected. If you are intending for EG to connect to a SAS metadata server (usually remote), use the SAS Integration Technologies Configuration Wizard (ex. C:\Program Files\SASHome\x86\Integration Technologies\ITConfig2.exe) to test a connection to the SAS server (ex. Test SAS Servers->Enter a SAS server definition manually->select SAS Metadata Server->specify appropriate machine name, port, and credentials->Press Test button). Casey

CaseySmith · ‎06-07-2017

Disregard. The issue I was thinking of was with the value EG was setting to SYSLAST when you explicitly link a data set to a program in a process flow. (EG sets the SYSLAST macro to the linked data set in this case.) I second posting your log. What is the exact version of EG (listed in EG's Help->About dialog) you are using? I seem to recall this being a bug at one point that was fixed. Casey

CaseySmith · ‎06-06-2017

This issue has been reported at least once before. However, since we were unable to reproduce internally, we were unable to debug. Note: The EG data grid control was replaced in later versions, so there is a decent chance that the latest version (EG 7.13) will not exhibit this problem. Casey

CaseySmith · ‎05-25-2017

Thanks @Quentin! That was the missing clue. I am now able to reproduce (which greatly increases our ability to debug and potentially fix the issue). I will enter it into our tracking system. Casey

CaseySmith · ‎05-25-2017

Yeah, the appSettings stub wasn't included in the EG 5.1 SEGuide.exe.config file, but the option does work in 5.1. You should be able to copy the appSettings example above and paste it immediately above the </configuration> line in the SEGuide.exe.config file.

CaseySmith · ‎05-24-2017

I believe this undocumented config file option will accomplish what you desire... If you open the SEGuide.exe.config file in the EG installation directory (ex. C:\Program Files\SASHome\SASEnterpriseGuide\7.1), you'll see a commented-out "appSettings" element. Remove the comment region demarcators ("") from around the appSettings element and specifiy the key "FormatValuesAsNeeded" with the value "false". It should look like this: <appSettings> <add key="FormatValuesAsNeeded" value="false" /> </appSettings> Now, after you save the SEGuide.exe.config file and restart EG, that config file option will instruct EG to read the formatted values directly from the server rather than formatting the raw values just-in-time (as a performance enhancement for wide data). Casey

CaseySmith · ‎05-24-2017

Thanks @Quentin. I made sure my options matched exactly, but I still can't reproduce. One of our developers (who supports the editor) is also attempting to reproduce and looking into.

CaseySmith · ‎05-24-2017

Hi @BonnaryW, Yes, there is a SAS Deployment Wizard (SDW) "noreboot" option. SDW options can be passed through the standalone installer by including them after "--" on the command-line. For example: SASAddInForMicrosoftOffice71_x86_x64.exe -- -noreboot Casey

CaseySmith · ‎05-24-2017

Hi Quentin, I'm not able to reproduce in EG 7.13 HF5 using your steps. Have you changed other Autocomplete options other than "Autocomplete on: Third character" (in Program->Editor Options...->Autocomplete tab)? What specific version of EG 7.13 are you using (version in Help->About box)? Casey

Online Status	Offline
Date Last Visited	2 weeks ago