I have created a shiny app on my computer that runs with no error. Now, I deployed the same app to the shiny server we have in our organization, and i cannot initiate the app. I receive the following error message:
transpose listening on http://127.0.0.1:43202
Warning: Error in tabPanel: argument "tabName" is missing, with no default
65: tabPanel
Execution halted
here are my questions:
(1) I do use shinydashboard and shinydashboardplus libraries in my app and both are installed on the shiny server as well so this shouldnt be a problem since tabsetPanel and tabPanel are in these libraries, correct?
(2) tabPanel and tabSetPanel do NOT have a tabName argument. so what is this error specially because the app does work on my computer with no issue.
I know probably I need to provide the code but I cannot at the moment unless i significantly take stuff out of it (government property) but I was hoping someone can help considering the fact that it works on my computer but it doesnt when i deploy it.
Just a quick note that the R version installed on my laptop is 3.5.2 but the one on the server is 3.6! can this be an issue?
Thanks!
I think a library bs4Dash was masking tabSetPanel which is quite confusing because i didnt have that problem running the app on my laptop...
Related
Have created a GAE standard Java Project using Eclipse IDE. This is the most basic one and I have not made any changes to it.However when I am trying to debug it, its geting an error.Error message being shown is that port 8080 is already in use.I think I have been able to properly install the GAE plug-in. Could someone please point what the issue is and a solution as well? Sc shot: https://i.stack.imgur.com/w2Xhz.png
This error means that a process is already using the port 8080, so your app can not use it.
You can either use another port or find the process that is using the port and terminate it so the port is free for your app to use. You can follow these instructions for this last approach, which is the one I recommend.
I've been installing our very own ArcGIS Enterprise instance on AWS.
The instance I chose is ArcGIS Enterprise on Ubuntu.
It is important to mention that this installation was conducted without using Cloudbuilder. I know it is a tool that automates the process but I was introduced to it only after I have already started to attack my current instance problems head-on. So, please don't advise me to restart the whole process from scratch using it.
The current status of my instance is that my ArcGIS Server is working. I can access it, upload services and we have already started using it in out Staging environment.
I have authorized all of the software on the server and verified it is licensed. The Portal for ArcGIS is my main problem.
Whenever I try to access it externally(from my office computer) it seems to redirect to the internal IP for some reason, and then times out on that request.
for example typing(from my browser):
https://[dns address]:7443/arcgis/home
redirects to:
https://[internal IP]:7443/arcgis/home
and this times out. (...took too long to respond error)
The funny thing is I can access the portaladmin area.
it's only the portal itself which doesn't work.
Also, another curious thing is that if I type without using the ports, I can access a window but exceptions are thrown in the browser.
For example:
https://[dns address]/arcgis
This will lead to a window where the ArcGIS world icon can be seen but nothing else loads and there are exceptions for "resource not found" 404 on some of the components of this page.
Any ideas? What further information should I include to answer this question?
I've looked everywhere but Esri's documentation is not very forthcoming with examples and information to understand what it is I did wrong.
Also, I don't think this is a ArcGIS software issue. It looks like this might be a proxy issue. Anyone else experienced something like this?
Thanks!
I found the solution.
It was a combination of two problems:
Tomcat that was running the web adaptor service was crashing because of an entirely different and unrelated issue.
The Portal was missing a web adaptor configuration and therefore did not have the WebContext property set with the web adaptor URL.
After fixing both of these problems, I was able to access the portal correctly.
I'm receiving an error that's nearly identical to what's posted in How to solve DEP6500 while deploying a solution with multiple projects to an emulator or Lumia 950xl:
The issue isn't resolved and I've got further detail to add here in the hope that it might resolve & clarify both questions (that question is presently the top hit when I search for DEP6500)
AFAICT, mine really appears to be a VS15 solution deployment configuration issue.
I have a single solution with five projects: three apps, a class library, and a win runtime component:
First trivial app, references #2
Universal class library, references no other project directly, but attempts to use an AppServiceConnection to connect to #4
Second trivial app, just a hello world, references absolutely nothing
Third trivial app, references #5, meant to be used via an AppServiceConnection
Universal windows runtime component, references nothing
Really, what I want to be able to do is start with nothing deployed to the device, select "Deploy Solution", and have all three apps successfully deployed.
Based on the rest of the description below, I'm clearly misconfiguring this solution, but for the life of me I don't see where.
At the solution level, if I configure any combination of two or more of the three apps to deploy, I get the DEP6500 error when I try "Deploy Solution" - actually, two DEP6500 errors when three apps are configured to deploy.
If I configure only one of the three apps to deploy, deploying the solution works just fine.
If I uninstall every deployed app and deploy just #1, as you might expect, it has trouble at runtime when it tries to use #4.
If, instead, I deploy just #1 and then deploy just #4, #1 runs just fine.
As I said earlier, if #1 and #4 are both configured to deploy, deploying the whole solution fails.
The third app, #3, is really uninvolved in this whole mess, I only added it to better characterize the problems deploying #1 and #4.
Seeing as each deploys just fine individually and all three can be deployed to my device at the same time if I deploy them one at at time, how can I configure Visual Studio 15 to deploy all three when I run "Deploy Solution"?
Finally, it would help to find out what type of port the IDE referring to when I produces the error in question:
DEP6500 : A specified communication resource (port) is already in use by another application. 0x89731800
helpful smaller questions may be: that is that port used for? when is it opened? how long is it open? how can I configure VS15 in a way that avoids port collisions between apps during full-solution deploys?
The issue here was that Visual Studio 15 just doesn't appear to be able to time the deployment correctly when you ask it to do a full deploy of every project in one action.
In this case, manually deploying each project one at a time yields a good result.
I suspect the "port" in question has to do with device deployment, as I can do a full deploy to my local machine without issue but see the DEP6500 error on deploys to my Lumia 950XL.
My aim was to be able to do a full deploy from a single VS15 menu option and that's still not technically working consistently, but I suppose I've found a workaround in as much as a piecemeal manual deploy is working everywhere.
I recently began using GWT 2.7 in Eclipse Luna and I was running my projects seamlessly while testing them in localhost:8888, the thing is, when I tried to test them (any of them, even a new app with only the autogenerated content) with another device on the same local network using (pc running eclipse ip):8888 I get a message like this:
The page at (ip):8888 says: Couldn't load (app) from Super Dev Mode server at http://(ip):9876. Please make sure this server is ready. Do you want to try again?
This also happens when I try to access to the app in the pc running eclipse with (its own ip):8888.
I've checked these four similar questions, but they didn't have any really helpful answers, these are a few things I've tried or discovered already:
I enabled the 9876 port on the firewall
I've deleted the .nocache.js and .devmode.js so that they're generated again
I noticed that when this problem occurs it's because the browser can't get the (ip):9876/recompile-requester/(app) file
I tried deploying the app to GAE and it doesn't work there either, nothing that happens on the modules Java code runs (And for some reason, I get a "Uncaught java.lang.ClassCastException" message on the chrome console, but this only happens on the deployed version, it doesn't happen on localhost:8888 or in (local ip):8888)
But nothing has worked and the four questions I mentioned are pretty much the only things related to this I've found, so I really don't know what else to try.
As Thomas pointed out, the problem I had was that from GWT 2.6 onwards, if you want to test from other devices in the same network, you have to whitelist the addresses you'll be using in each *.gwt.xml file using a command line like this:
<set-configuration-property name="devModeUrlWhitelistRegexp" value="http://(localhost|127\.0\.0\.1|192\.168\.150\.(\d{1,3}))(:\d+)?/?.*" />
I also had to add a -bindAddress 0.0.0.0 attribute to the run config for it to work.
So today, whenever I try to sign My Blackberry app using the WebWorks packager, I get this error...
"General failure. Please try again. Server may be unavailable".
My proxy settings have not changed and I have been using the same command line instruction with success before.
I've also checked the status of the Blackberry signing server using the following link...
http://isthesigningserverdown.com/chart/index.php?sigType=RBB or RCR or RRT
And everything appears to be online!
So, where could I be going wrong? Here's the command line instruction I've been using. First, I navigate to my Blackberry build folder and run the following instruction against it...
bbwp appname.zip –g <password> –o z:\projects\appname\signed
It goes through through parsing the various elements. The signing tool pops up and then the error is generated.
So, after a couple of days of banging my head against the wall-the answer finally came to me. I'm on a MAC but am also using a Windows virtual machine for Blackberry developement, which is running on another network altogether and this specific network is using a firewall, which, according to the network administrator, is currently experiencing a severe technical problem.
The way round it was to sign my Blackberry app using configured proxy settings to communicate with the signing server and viola! It worked!