I have followed the exact steps mentioned here for Ubuntu 14.0.4. I've got the mongodb,elastic search,graylog server/web/collector up. Unfortunately when I hit the web ui http://:9000 and login through the admin, I am unable to see the collector component all together. I'm attaching the screenshot of the System tab. What am I missing?
The latest repository they had, was installing an older version of the server, which didn't support the collector functionality. I had manually downloaded the tar files, and it worked.
Related
Publishing package in my local system is taking much longer time than expected. It is taking around 15-20 minutes to publish, and sometimes it is throwing an error, UNABLE TO READ DATA like this.
I also tried even after Restart Application from Apply Updates screen but still same issue. How I can solve this?
You might want to try to disable web site building.
In Visual Studio, go to web site property pages and deactivate the following 2 configurations:
Uncheck Build Web site as part of the solution
Before run startup page - no build.
See http://asiablog.acumatica.com/2016/09/make-compilation-of-extension-library.html
I am trying to set up thingworx composer on a Linux machine.
In the Application logs the Server is ON and db is initialized.
But when in the browser I try to open composer, then it is stuck at the landing page (the black page with Thingworx logo in green) and doesn't go to the Composer Home page.
#Tarun if you are still facing the problem, then try restarting the tomcat and db servers. Make sure that there exists 'Thingworx' folder under Tomcat install dir/webapps folder, as upon successful installation Thingworx will automatically creates a folder over there.
Considering the Thingworx directory exists, try to access the apache tomcat's catalina logs and look for any errors at the End of File.
Have you tried clearing the browser cache? If this is a migration/upgrade, you may have a prior UI cached in your browser and it is conflicting with the version you are currently trying to install.
Additionally, checking the Security Log and Application Log for any warnings or errors may provide more insight into why the server is not loading Composer.
Make sure that JAVA_HOME environment variable is set and Thingworx related folders have write permission of the user. Also, this can be caused of license problem. Make sure your license.bin file exists in ThingworxPlatform folder and platform-settings.json file is valid.
For further assistance, you can create a ticket from PTC Support.
I am getting stuck while creating a new plugin project in liferay, eclipse get stuck everytime and console displaying only [ivy:resolve] message
It appears that the Ivy resolve process inside of the Liferay Plugins SDK is failing when it tries to create a new process.
Go into your Liferay Plugins SDK folder and open the ivy-settings.xml file. Notice that it points to some online repositories. It seems that your system is having trouble connecting to those remote repositories. See the log messages about the failing certificates (when its trying to connect to the https:// server of jboss repository ).
Maybe will be any special configuration required for connecting to those repositories, proxy...
Try from here
I've tried on a couple of different servers to install Web Deploy and it works to the extent that I need it to, but I haven't identified what the missing steps are.
Where it falls down is after installing what appears to be the requisites here:
http://www.iis.net/learn/install/installing-publishing-technologies/installing-and-configuring-web-deploy
There is only occasionally the option for "Configure for Web Deploy Publishing" in the context menu on the site. Does anyone have a guide for this for proper deployment? How to enable the option?
Deployment in these cases is not through WebPI. I have to download packages separately and install manually. Can't find something that details this with current links, screen shots or advice.
Base Windows Server 2008 server with nothing special installed. Happy to clarify anything if anyone has any ideas.
The fix (provided by Kristina Olson of Microsoft) was to uninstall Web Deploy and then make sure all the pre-requisites are in place. There is mention of this in this article:
http://www.iis.net/learn/install/installing-publishing-technologies/installing-and-configuring-web-deploy
Key points:
Make sure Web Management Service handler component in IIS is installed and enabled
Make sure PowerShell v2 is installed
Database dependencies need to be installed
Make sure to select the complete install
I have a small solution that is composed out of 2 main projects a Mvc4 Web Api and a silverlight 5 Application. I've configured and deploy the application initially on the Azure platform and it all went great, but ever since when I deploy again the silverlight project does not get pushed and the online site has the old version.
I should mention all works great with the azure simulator on my local dev machine.
Anybody had a similar issue?
Regards,
I would suspect first (as Simon suggests) that the browser likely still has the previous client cached and loads that instead of downloading your new client.
You can use the version number in the code on your page that hosts the silverlight app to help. While it's easy for you to clear the cache - you don't really want to have to tell users to do that whenever you update.
Set the version to whatever your latest assembly version is (silverlight client project assembly), this will force the browser to download the client if the cached version is a lower number.
<param name="source" value="AppPath/App.xap?version=2.0.0.6"/>
Ok,
So after pulling my hair out, I finally figured out.
I have to change the build configuration to release in VS do a rebuild and then do publish because apparently the azure project does not do rebuild on the project when you publish it.
To solve this issue you'll need to identify the source of the problem (is it a client side problem where you have a caching issue or not). Even though you say caching isn't the problem we'll need to be sure about this first.
What I suggest is that you do the following first:
Activate Remote Desktop on your role
Connect through RDP and save this file to the role: http://support.microsoft.com/kb/841290 (fciv.exe)
Find the *.xap file (usually in E:\sitesroot) and get its checksum (using fciv.exe)
Modify the Silverlight project locally (maybe change a label or move around an element) to make sure its hash has changed.
Redeploy the application
Connect through RDP and use fciv.exe to get the checksum of the *.xap file once again
Compare both checksums
If the checksums are different, then it means that the deployment worked correctly and the Silverlight xap has been updated. If the checksum is the same, the problem lies with the deployment.
Please let us know the result so we can help you find the solution.