About dpage

dpage · ‎01-02-2017

If you don't have the credentials to pass to stop (as indicated in the note) you can use the kill argument instead - it's not the graceful shutdown you'd get, but it's better than terminating the process.

dpage · ‎01-02-2017

There would be two key logs, C:\program files\SASHome\InstallMisc\InstallLogs\IT_*.log (not the filelist one) and C:\Users\<userid>\AppData\Local\SAS\SASDeploymentWizard\SDW*.log

dpage · ‎12-15-2016

Check the logs for SASServer1 (what should be coming up on port 8080), Lev1/Web/Logs/SASServer1_1/*.log and Lev1/Web/WebAppServer/SASServer1_1/logs/server.log - you should either find errors, or a succesful start (but after the timeout expired)

dpage · ‎12-12-2016

Let's open a track with support and we can look into specific logs and issues.

dpage · ‎12-09-2016

The Mid-Tier server. However, if the only thing you created on the web server machine was a web server, it shouldn't be appearing in this list, I'd be worried some additional things were configured on the web server tier that you didn't intend.

dpage · ‎12-09-2016

Correct - https://support.sas.com/documentation/cdl/en/biig/69172/HTML/default/viewer.htm#n05002intelplatform00install.htm SAS(R) 9.4 Intelligence Platform: Installation and Configuration Guide says: "4.If your deployment plan separates SAS Web Server from SAS Web Application Server, install SAS Web Server first." (In the 'Install Order Rules for Multiple Machine Deployments' section of the 'Installing and Configuring your SAS Software' chapter ) similar story if you wanted to do Machine 1: Meta & Web Machine 2: Compute You'd make a plan with 3 machines Machine 1: Meta Machine 2: Compute Machine 3: Web Configure them in order, but when configuring machine '3' you would go back to machine 1, and configure it in a new configuration directory, (C:\sas\WebConfig separate from C:\sas\MetaConfig)

dpage · ‎12-07-2016

Can you change the permission back to allow the delete?

dpage · ‎12-07-2016

Did you reload apache after the change? If you visit http://dc5coj.ca:8088/rute directly, does the page display as expected? If not, the problem is on the web app server side, if it does, the error is on the web server side.

dpage · ‎12-06-2016

What product(s) are you attempting to install? If you just want the SAS Client software, you shouldn't see prompts for sastrust or sasadm - verify your selection of machine if you're using a plan file. If you're after a larger offering, you will find more details in SAS(R) 9.4 Intelligence Platform: Installation and Configuration Guide http://support.sas.com/documentation/cdl/en/biig/69172/HTML/default/n05020intelplatform00install.htm It gives some information about the prompts you're seeing, with links to more details about setting up users.

dpage · ‎11-23-2016

Hopefully someone else can provide the XML snippet, but in the meantime for the logger definitions http://support.sas.com/documentation/cdl/en/bisag/68240/HTML/default/viewer.htm#n0pitzrsxlrvyfn1o967czb2oww2.htm and for the usage of SASMC to change live logging levels http://support.sas.com/documentation/cdl/en/bisag/68240/HTML/default/viewer.htm#p0o497lmygjfrfn0z7t999n72tpg.htm The topics are covered in the SAS(R) 9.4 Intelligence Platform: System Administration Guide

dpage · ‎11-18-2016

It means you have pre-assigned libraries that the user validating connect server doesn't have credentials to connect to. http://support.sas.com/kb/59/292.html

dpage · ‎11-07-2016

I'm not aware of any such resource - If you can elaborate what you're trying to do maybe it can be done a different way?

dpage · ‎11-07-2016

When you order one of those products, the license you receive will include any needed dependencies it might have you don't have to assemble that information yourself.

dpage · ‎10-18-2016

You'd have to check your response files and confirm the correct hostnames were entered during the prompting phase. You can examine your response files and see if anything was incorrectly entered (or defaulted to the old hostname accidently somehow) At this point it's probably best to open a tech support track to track down what happened.

dpage · ‎10-18-2016

Is this hostname correct "esesslx0538.ss.sw.se" You'll get an unable to bind message if that reverse looks up to an IP not available on the machine as something that can be bound to.

Online Status	Offline
Date Last Visited	‎07-14-2021 02:23 PM

Re: External Account Password Change

Re: SAS WebApp | Horizontal Cluster -- 404 after start the second mid ...

Re: Cannot execute systemEvalutation application - invalid config-dir ...

Re: Deployment error on task 'Create token for staticcerts'

Re: SAS Support policies

Re: %FSLOGIN error

Re: %FSLOGIN error

Re: %FSLOGIN error

Re: Hostname Update Error

Re: Hostname Update Error

Re: Cannot execute systemEvalutation application - invalid config-dir ...

Re: Deployment error on task 'Create token for staticcerts'

Re: SAS Support policies

Re: %FSLOGIN error

Re: %FSLOGIN error

Re: How to stop SASserver5 in webserver

Re: SAS Deployment Wizard seems stuck during installation - Please hel...

Re: Problem was encountered while configuring SAS Web Application Serv...

Re: SAS Web Server configuration on 2 machines (SAS9.4M4)

Re: SAS Web Server configuration on 2 machines (SAS9.4M4)

Re: SAS Web Server configuration on 2 machines (SAS9.4M4)

Re: Deleting Stored Process With All Groups Write Permissions=Deny

Re: Web application using SAS

Re: Problem with installing SAS

Re: Enable Metadata server debugging using proc metadata or proc metao...

Re: SAS Connect Server Validation failed

Re: List of Products

Re: List of Products

Re: SAS webserver configuration failure: Http port 7980 does not exist

Re: SAS webserver configuration failure: Http port 7980 does not exist

SAS Global Forum 2019