I have a remote database and a copy of nopcommerce running locally (from Visual Studio). During the first run I hit the install button and the page still appears to be loading some 40 minutes later.
I looked into the database and all the tables seem to be there. I didn't bother to copy sample data, so there shouldn't be that much stuff to be done beyond creating tables?
So the question is how long should the installation last? Maybe it is ok to assume that it's done and I can ignore the part where page still appears to be loading?
Your assumption about "it's done and I can ignore the part where page still appears to be loading" is absolutely correct. Usually installation takes 1-4 minutes (depends on your hosting specifications).
But we also experienced this issue several times when the installation page hangs (but we know for sure that it's already completed).
It can take 5 minutes or more to install NopCommerce on remote database when running Nop on local machine. It's probably better to do the installation on local DB (or put Nop on the same remote server as the database).
In my case Nop would hang after the installation was done, but likely it should not happen with a local DB (the hang is probably caused by the long installation time).
Related
I've been trying for the lase week to use GitHub from NB from a Windows 10 machine. Very little success.
The problem is the first Push step (Next) seems to time out will trying to connect, giving a Fail to Connect error. If Next is clicked again it often seems to connect... no more "failed to connect" message. However, the Finish step fails with a "cannot open git receive pack" message. On rare occasion, both steps succeed.
I am aware that there have been reported Windows 10 page load load time issues from the beginning, so am suspicious. But I report this thinking I am probably not the only person with the problem. For now, NB GitHub is useless. Too bad.
Turns out I had a network issue. Recently page loads and other Internet operations have been slow, and finally stopped altogether. I rebooted my cable modem, presumably resulting in a new IP from my ISP (Spectrum). And now the Push is working
Try first the first push from a Git for Windows in a CMD session, possibly using a simplified PATH, for testing.
If that does work, check if NetBeans has the same issue (pushing to a GitHub repo) with an HTTPS and/or an SSH URL.
I must have done over 100 installs of DNN (dnnsoftware.com) now, and I have never seen the "wizard" complete correctly. It always hangs at 28%. Upgrades usually hang at the 53% level.
This appears to be a user interface fault, because if I wait long enough - how long? - I can navigate to the site and all is working perfectly. If I don't wait long enough, some part of the installation process restarts and gives me a site without a superuser account.
The installation process does not appear to have been adequately tested. Anyone know how to get the "wizard" to complete correctly?
I haven't experienced this high of failure rate with the installation or upgrade.
In order to diagnose the problem, do an upgrade. Before applying the upgrade, set the AutoUpgrade key in the web.config to "false". Then initiate the upgrade by going to:
[baseurl]/install/install.aspx?mode=upgrade.
Instead of the simple progress bar, you will get a detailed report of the extensions and items being installed or upgraded.
Before installing, make sure your file permissions are set appropriately on the website folder and you follow all of the steps as per the installation guidelines.
Also, if it turns out the issue is timeouts during the install due to a slow server, try increasing the execution timeout in the web.config in the <httpRuntime> node. The default executionTimeout is "1200" which is 20 minutes. if your upgrade or installation is taking longer, increase the value.
Looks like using the deinstall option would wipe out the entire HOME & BI cluster.
While we are trying to restore down to the 11.1.1.6 previous installation.
Windows platform. We were using the software-only in-place upgrade.
[Solved] The cleanest way, turns out, is to repeat the process multiple times while eliminating the reasons causing it to stick, one-by-one. It then rolls forward nicely, simply logging "this has been already upgraded". Also noticed that some of the Java installs have the sticky "finish" button - which is resolved by simply killing the javaw process. Happened on 2 out of 4 GUI installation steps during the upgrade.
I've been working on a VB.NET/VS2008/AJAX/SQL Server project for over 2 years now without any real issues coming up. However, we're in the last week of our project doing some heavy stress testing and the project starts failing once I get about 150 simultaneous users. I've even gone so far as to create a stripped down version of the site which only logs in a user, pulls up their profile and then logs off. That still fails under stress. When I says "fails" I mean the CPU's are spiked and the App Pool eventually crashes. This is running on a Windows 2008 R2 duo quad server w/ 16 gig of memory. The memory never spikes but the CPU tops out.
I ran YSlow on the site and it pointed out that I needed to compress the .axd files, etc... I did that by implementing Gzip compression on everything but that's what got me to the 150 users. I run YSlow now and it says everything is "A".
I'm really not sure where to go from here. I'd be more than willing to share the stripped down version of the site for anyone to review. I'm not sure if it's the server, my code or the web.config.
I know it is a bit late but have you considered increasing the number of worker processes in the application pool of your site to form a web garden? You can do this on the IIS Manager.
Setup TFS 2010 on a pretty oldish server (actually an oldish desktop machine running server 2003 - single core, pre Core2 P4 so outdated...)
I'm finding a first adding and first getting of a website with about 700 files is quite slow (over 20 mins already over a VPN line).
Once you do that, the checkin / checkout operations are reasonably ok.
One thing I haven't done yet is get one of the guys at work to make a change and for me at home to do a get latest. We were running VSS up to this and that operation used to be a killer!
Anyway, few questions:
1)We set it up as a basic installation on server 2008 express. Would there be any performance gain with full sql server 2008?
2) We have the option of moving the drive to a better core 2 machine that should be a lot faster - will that make any difference?
Or are we simply running into a typical slowness of TFS over a LAN (bearing in mind we as a team work mainly in the office but sometimes from home over VPN when the speed issue seems to get worse).
TFS in it self isn't slow. We run a TFS on a dedicated VM and with the other VM's on the actual server also taking up ticks, or TFS is decently fast and reliable. Even when checking in and out code, running reports etc... So maybe the 2 core machine would help, but your P4 shouldn't be that bad in running it. 700 Files should be fairly quick within a minute or so. I think its your VPN that makes it slow. Everyone knows how slow VPN's can be.
Just an update. We moved to a faster machine (since we were getting one anyway). The speed of the machine makes no difference.
The good news is, its only slow the first time you add a project to TFS or take it down from TFS.
Daily checkin / checkout is fine. Also, doing a get latest from home is much improved over VSS - it no longer does that horrible freeze while it spends 10 mins figuring out if files have changed.
It was worth the upgrade for this alone.