I am trying to create a file location in SAP Data Services designer using SFTP protocol, but it shows an error:
The field <fl_gcs_refresh_token> cannot be empty. Please enter a value. (BODI-1220393)
I searched the internet, and found that it has relation with Google Cloud storage even though I am not using it.
Related
I am using Arcgis Online. I want to migrate my feature layers (data which stored in esri's internal database) to external database.
Can anyone help me to figure out how I can do it? Also how can I use external database in my Application(PostgreSQL/Neo4j).What I need is, to host my own database server like neo4j and use as a replacement of feature-table provided by ArcGis.
Thanks,
Tarni
You have many options for downloading data from ArcGIS Online.
If you do not have many feature services, the easiest way would be to go to "My Content", then find your feature service. You should see an "Export Data" option towards the top-right.
If you have multiple feature services, you could repeat the directions above, but choose "Open in ArcGIS Desktop". This will download a file that will set up the connection in ArcMap for you. You can also hit the services directly from ArcGIS Desktop by going to "My Hosted Services" in ArcCatalog and logging in.
Another option is to use a Python script. This may be best if you have alot of data, and if the data is updated frequently. Check out https://github.com/tedrick/SyncSurvey for an example of getting data repeatedly from a feature service.
[i am getting error
"Type error:Cannot read property 'statuscode' null at process response call back"
while creating table in microsoft azure storage explorer when using external storage,while locally table is creating perfectly.please help.][1]
while creating table in Microsoft azure storage explorer when using external storage, while locally table is creating perfectly.
Please have a try to check whether the network is smooth. The error message indicates that can’t get the response status from the azure storage. It seems that something wrong with the network. If the network is smooth, please try to create the storage table again. If the issue is still repro, please have a try to troubleshoot with following ways:
Try to download the latest version of Microsoft azure storage tools
Create another storage account and try it again
Please have a try to use another computer to check it.
I created an schema in Schema Workbench and publish with no errors, but when I got in BI Server with the standard user admin, I choose New->jpivot, then it display the name of the schema I created but it does not display the cube. For reference the error I get from catalina.out is:
17:11:45,174 ERROR [PentahoDataSourceResolver] PentahoXmlaServlet.ERROR_0002 - IDatasourceService.UNABLE_TO_INSTANTIATE_OBJECT
org.pentaho.platform.api.data.DBDatasourceServiceException: javax.naming.NameNotFoundException: Name [Esquema Salario] is not bound in this Context. Unable to find [Esquema Salario].
Name [Esquema Salario] is not bound in this Context errors usually appear if you use JNDI name, which is not defined on your system. So, I assumed, that this is the name of the datasource, which you reference while publishing Mondrian schema files to BI server.
Xml file with Mondrian schema definition generated by Schema Workbench does not contain any information regarding how to connect to database. So, you need to specify these details when you upload your schema file on BI server (It's done on step 4 below).
But first you have to create the connection itself (steps 1-2):
Create new JDBC datasource:
Define connection parameters:
If cubes still don't appear after these steps, you may republish your cube: follow same steps as in step 1, but select "Analysis" instead of "JDBC" in the end.
Upload the xml file, generated by schema workbench and select the datasource, which you have created on step 2. .
If cube still does not appear - check your log again. If you see the same Name is not bound error, you may try to restart your BI server application (new connections usually get recongnized immediately, but if you had a connection with same name before, than you might need to restart tomcat).
If that does not work, than once again, check log files. I guess, you'll have some different error in this case.
I had the same problem as the OP (blank screen when clicking New View) with the latest version of Pentaho BI server 7.1 (latest at the moment) and even with the 6.0 version one, Pivot4J SNAPSHOT 1.0 plug in version (latest as of today), Schema Workbech 3.14 (latest as of today).
And as, in line with OP, my catalina.out log was also spitting the Name [DatasourceName] is not bound in this Context. Unable to find [DatasourceName].
After several trials and errors I noticed the problem showed up when I checked the "Register the XMLA Data Source" when publishing the schema on Schema Workbench. So to fix the problem I just unchecked it before publishing.
Another way to fix this is going to the Manage Datasources option on the BI server, Import Analysis, choosing the schema created by Schema Workbench, AND manually setting the data source parameter value EnableXmla to false and saving changes. Now the schema should show up when clicking on Create New > Pivot4J view.
I created an Access front end for a SQL DB on my PC for use throughout my company. I am using a file ODBC connection and putting both the ODBC file and the Access file on a shared network drive.
When I load the access file, for some reason it seems to default to using my windows login credentials and pulls in the data perfectly. When a user attempts to open the file, they receive an error message saying "ODBC --call failed.". I can open the Linked Table Manager for them and check 'ask for new location' then specify the ODBC file and it all works fine...however it doesn't seem to save anything. I get the error each time someone other then myself opens this file.
Any idea what could be wrong? I am not an Access guy by trade, it just seems to be the tool we need for the moment.
--EDIT: For Clarification I am using a file ODBC connection
--Edit 2--
Riddle me this. So I have been troubleshooting this issue and I came across something interesting. I was logged in as one of my users and did the following:
Create a new access file that references a file ODBC connection on the desktop.
Create 3-4 linked tables in the access file, using the ODBC file on the desktop.
Save and close the access file.
Re-Open said file.... and I get an ODBC connection error! Right after everything was fine in a fresh file!
Anyone ever experience this?
i assume you didn't install the ODBC correctly on each users PC.
you should create the ODBC-definition. You can create the relevant statements directly in the registry, see this branch
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI
if you give the same name as on your developer machine, then it works. that's how i do it with my client applications that i develop on my machine and then install it at client site
After beating my head against the wall having this same issue, I finally discovered I had a checkbox on the Access form that defaulted to NULL. Since I put the backend into SQL, the checkbox fields cannot be NULL but the 'ODBC Call Failed' message did not help. I finally tried to add a record directly on the table via Access and it gave more information. I set all the checkboxes to default to zero and it resolved the problem!
Well, I was able to narrow the issue a bit. Access for some reason keeps trying to use Windows Credentials instead of the username in my ODBC file. I can't find a way around it, but I was able to resolve the issue by creating logins on my SQL Server for the windows users that need access.
I am not incredibly happy about needing to manage more logins, but that's what i did to resolve this issue.
I don't mean to resurrect the dead, but I had this same error stem from a different issue.
I was using an ODBC connection. When running the file using the 'Design' run button it worked fine. When I tried using the Navigation Pane and double clicking on it, the error would happen.
The structure of my query was the problem; I was porting a SQL server query over and the single quote ' parameter passing was not well received in Access. Changing these over to double quotes " made it work.
I'm taking my first crack at creating an External list in Sharepoint 2010. I've taken 3 training classes in Sharepoint 2010, and am now trying to transfer my knowledge to my own development environment. I've followed the steps for creating my External Content type in Micorosoft sharepoint designer. I am connecting the External Content Type to a table in an external SQL Server Database. I've created a list specifying this External Content type. I've also given all authenticated users permission. I've verified that BCS is running, and all looks good. I've also checked and double checked the steps I used in creating the external content type and list, by referring to the lab manual from my Sharepoint class.
When I try to navigate to display the list, I get this very informative error message:
Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator.
Correlation ID:b7c91266-bbbc-4703-8704-beccbbd92de0
I've tried opening this page in Sharepoint Designer but this doesn't seem to help me. Has anyone experienced this problem before? Any gotcha's that I should be looking for.
Whenever you see a correlation ID, then you should be able to get more information on the failure in the ULS output. Search for that Correlation ID in the logs and you should get plenty of additional information.
If you don't find much in the ULS logs, then change the settings to log additional information.
you need to check selection of primary key of sql tables while retrieving data to list.
To capture the error being thrown, use the SharePoint LogViewer app from CodePlex: http://sharepointlogviewer.codeplex.com/
You need to run it on your server and hit the Play Button at the
top. This starts the Live Monitoring.
Refresh your page that will give you the error with the Correlation ID.
Stop The LogViewer and filter the results by the Correlation Field.
Copy and paste the ID from your browser into the filter field.
You will now see a list of what errors are being thrown in relation to the Correlation ID.
I hope this helps out!