About mklybor

mklybor · ‎04-04-2014

yes I've done so, and supplied my transport logs. we'll see what turns up. thanks.

mklybor · ‎04-03-2014

I changed the internal connection info to match the external connection and still the same problem persists. I'm assuming that both the internal and the external connection should match what is specified in the mobile application's connection settings that identify my server. both internal and external settings are now the same as the connection setting on the mobile.

mklybor · ‎03-31-2014

thanks. I've reviewed numerous server logs looking for trouble and didn't see any. the date and time is easy to find because this is a controlled development environment with a small number of users and I can control access. Not sure which logs I should be looking at, there are so many.

mklybor · ‎03-31-2014

I'm having a similar (I think!) problem. I can access my library, browse the list of reports and subscribe to them. However I get a "download failed" msg on the tablet when I try to access the report contents. I am using android mobile V6.3. and VA V6.2 hotfix 2. are there any server log files that could peruse that could contain more information about the error? any developments with the tech support issue?

mklybor · ‎02-27-2014

figured this out, needed to re-validate the workspace server

mklybor · ‎02-27-2014

while trying to register tables on a newly defined ODBC connection I get the error: ERROR: CLI error trying to establish connection: [Vertica][ODBC] (10430) Not enough information provided to establish a connection to the data source and specified to not prompt for more information. ERROR: Error in the LIBNAME statement. here is the libname: LIBNAME VGPAMAS VERTICA DATABASE=GP_AMAS DSN=Vertica_GP_AMAS SCHEMA=public USER=dbadmin 1 ! PASSWORD=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ; I can connect to this database from the server that is running the sas mid tier using ISQL, so the ODBC setup seems OK. the ODBC env variables are defined in sasenv_local and the workspace manager was validated the libname has the correct odbc DSN and user. what else could be provided that is missing? I've gone through everything I could find in the manuals re: odbc and vertica and can't find what might be missing.

mklybor · ‎02-27-2014

in my 9.4 config manual, the vertica config steps consist of setting some shell variables to point to the .ini files. where should these be set? in the unix logon scripts for each of my users? in some SAS startup script? do any servers need to be restarted after setting these up? we have all of the odbc pieces installed and configured. thanks.

mklybor · ‎02-27-2014

we try to route all of our mobile traffic through a common front end and then proxy it to the appropriate web/app server. do you know the protocol that is used? and , assuming it is HTTP, what do the URLs look like?

mklybor · ‎02-27-2014

thanks, but I'm looking for installation / configuration documentation, not usage. in the SAS 9.4 install manual, the section on SAS/Access for Vertica talks about installing ODBC drivers and the like. As I understand it, that is not what we have. We should have "direct" access to Vertica, not ODBC (as was the case for 9.3 and earlier). specifically, pg. 58 in Configuration Guide for SAS 9.4 Foundation for UNIX Environments says that for Vertica access, an ODBC driver manager etc. must be installed. It was my understanding that ODBC was no longer necessary since we now have native Vertrica SAS/Access. could you clarify whether Vertica access is still ODBC for 9.4? thanks.

mklybor · ‎02-26-2014

Where can I find documentation about installing/conffiguring SAS/Access 9.4 for Vertica? In the general 9.4 install manual, SAS/Access section page 58, it only talks about Vertica ODBC. Could you direct me to documentation for the native vertica SAS/Access? I have a new 9.4 installation that we are just starting to use. SAS/Access for Vertica was supposed to be included and I an trying to validate that we have everything installed. Attempts to access Vertica content give me an error the looks suspiciously like it was trying to use ODBC, which is not set up.

mklybor · ‎02-26-2014

I am setting up VA for mobile access for the first time. Which server do I expose to the mobile devices? Is it the same server:port that I connect to as the VA Hub (in my case port 7980) as used to view reports via web browser? Is this documented anywhere?

Online Status	Offline
Date Last Visited	‎09-01-2015 07:11 AM

Re: SAS VA Mobile BI content issue

Re: SAS VA Mobile BI content issue

Re: SAS VA Mobile BI content issue

Re: SAS VA Mobile BI content issue

Re: SAS Access to Vertica

odbc error opening connection

Re: SAS Access to Vertica

Re: mobile access to VA reports: which server:port do I expose?

Re: SAS Access to Vertica

Re: SAS Access to Vertica

Re: SAS Access to Vertica

Re: SAS VA Mobile BI content issue

Re: SAS VA Mobile BI content issue

Re: SAS VA Mobile BI content issue

Re: SAS VA Mobile BI content issue

Re: SAS Access to Vertica

odbc error opening connection

Re: SAS Access to Vertica

Re: mobile access to VA reports: which server:port do I expose?

Re: SAS Access to Vertica

Re: SAS Access to Vertica

mobile access to VA reports: which server:port do I expose?