I just installed b2c_acc_plus recipe and after it i also installed powertools B2B add on. When i am trying to access the accelerator website, i am getting a message on browser "Server Error". However strangely the Platform site is working. The server logs are also not showing any error.
I changed the host file. In HAC/Extentions all the B2C and B2B extention are showing installed.
Before installing the B2B addons the B2C sites were working, server logs are showing cronjobs for B2C & B2B. Any idea what could be problem?
In case an error is thrown, the tomcat server logs are very helpful.
Not sure how you started the application with a recipe or by executing hybrisserver.sh (on linux) in the .../hybris/bin/platform folder. You can take a look in the tomcat logfile directly in .../hybris/log/tomcat/console<date>.log file.
Without this, it's very hard to providing help.
Try to set logging level to debug and make sure you're passing site name in the URL. E.g. .../yacceleratorstorefront?site=electronics
Where did you get trainingstorefront? If you are using OOTB accelerator, it would be yacceleratorstorefront.
Please try to hit below URL and it should work.
http://localhost:9001/yacceleratorstorefront/?site=electronics&clear=true
http://localhost:9001/yacceleratorstorefront/?site=apparel-uk&clear=true
for https please change the port to 9002.
Related
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 trying to install Umbraco by using the Azure Marketplace. There they offer a template for it. I am always receiving the error below. I tried to install it a couple of times now but I always get the same error.
Does anybody know what this error message means? Is anybody able to install Umbraco by using the template in the Azure Marketplace?
]
You're asking 2 questions above.
Please see my answers and proposed troubleshooting guide/workaround below:
The error message means that the MSDeploy process failed due to some error which renders it unable to deploy the web deploy package for your Umbraco web app.
Yes I am able to provision a Umbraco web app from the Azure Market successfully (Location: Central US) and couldn't reproduce your issue
Troubleshooting Guide:
Append .scm in front of the azurewebsites.net of your Umbraco Web App as shown below and go to the Url.
Click on the Diagnostic Dump. You will be prompted to download a .zip file
Extract the zip file. You should see 2 folders at root level
Go into
LogFiles\SiteExtensions\MSDeploy
You should see the detail log files for MSDeploy
Detailed MSDeploy log messages are in the appManagerLog.xml file.
If it is related to client side issue which can be resolved by yourself, you can try to resolve it and try again.
If it is related to server side issue, you should create a support ticket for Microsoft to look into with the detailed MSDeploy log which pinpoints the root cause which will help them a lot.
Hope this is useful.
A Microsoft employee confirmed this is a bug in the application currently. I have to wait for a fix.
I have encountered numerous problems with the Azure installer of Umbraco, try setting it up in VS2015 then publishing it to Azure. I have found that this works well.
I've been trying to use Web Deploy 3.5 to deploy an application to an IIS 6 web server without any luck.
I am connecting using a domain service account that is an administrator of the remote server, but when I attempt to deploy (or validate the connection in VS2012) I receive a "ERROR_USER_NOT_ADMIN" error instead.
I read that Web Deploy 2.0 had a bug in it where a domain user account could not be used, but surely that's fixed by now? Right?
Has anyone had any luck with IIS 6.0, Web Deploy 3.5 and domain user accounts?
Anyone else trying this (with the right password ;-) , there is an issue using non domain accounts that gives this message, and the link in the error wasn't much use for me....
There is a regedit (yes, I know it's dirty, but this was a dev machine), which gets this working.... I'd tried everything from the MS link with adding users to additional groups etc, but still didn't work, the solution below did though.
Take a look at http://networkprogramming.wordpress.com/2010/10/29/401-not-authorized-for-msdeploy%E2%80%8F-msdeployagentservice/
Well this is embarrassing. It looks like that error message is also returned if the password is incorrect.
Oh well, you live and learn!
Another possibility: The user's password has expired.
Either
go into the "local users" within computer management and make sure Password never expires is checked, OR
run this command for that user: WMIC USERACCOUNT WHERE "Name='YOUR-USERNAME-HERE'" SET PasswordExpires=FALSE
I keep getting the "There was an error installing the requested package. This can happen if the server does not have write access to the '~/Modules' or '~/Themes' folder of the web site. If the site is running in shared hosted environement, adding write access to these folders sometimes needs to be done manually through the Hoster control panel. Once Themes and Modules have been installed, it is recommended to remove write access to these folders." message when trying to install a module from the Gallery.
I've given the IIS_WPG full control of the Orchard.Web\Modules directory and it worked yesterday, but it doesn't today.
I'm running from Visual Studio 2010 SP1 and IIS Express.
EDIT: I've made sure the gallery path is: http://packages.orchardproject.net/FeedService.svc/
I came across the same issue. We had a custom theme and I had to change the version from 1 to 1.0 in the theme.txt file. Then I was able to install a module.
I fixed this problem by doing this:
Change the app pool user to NetworkService or to a custom user you
create. (I was using IIS not IIS Express)
Grant read/write permissions to the user on the folders (Modules and
Themes).
Make sure Dashboard > Settings > Gallery url is
http://packages.orchardproject.net/FeedService.svc/
That fixed it for me. Using ApplicationPoolIdentity did not work, even when I gave it the appropriate permissions (not sure why).
I hope that helps.
I've just installed Sharepoint Foundatuion on my W2008 64bit server and got it up and running as far as being able to access the Central Admin etc just fine.
I did have to disable 32 bit apps in the application pools for all the SP sites and also, following a tip on here, add a config option for bitness64 as a prerequisite for the services.
However whenever I try to access the "Sharepoint - 80" site itself (or another site collection I created in the admin tool), I am getting an unhelpful 500 error. The log doesn't add anything - I can't find anything to give me a clue as to what it's complaining about.
The server is a hosted VPS and all services like SQL are running locally (and are OK).
Any ideas where I look next?
M
This turned out to be an incorrect specification of the dependencies for the Sharepoint14Module in applicationHost.config
In order to locate the issue I enabled Failed Request Tracing on the server and examined the logs that get output as a result. The preconditions for the module were incorrectly specified (appPool1,bitness64;appPool2,bitness64 instead of appPool1;appPool2,bitness64). Fixing this the sites sprung in to life :)
M