Do Not Install Greenstone 2.85 as Administrator in Window 7 Ultimate 32-bit
I removed greenstone 2.84 from my machine in prep for the new version. The old version had worked fine and had been installed as admin to c:\program files\greenstone. I also got another laptop over xmas for testing win stuff so i installed 2.85 to that. It runs Windows 7 Home Premium 64 bit (argh why so many versions?) and the install was straightforward and ended up in c:\program files\greenstone so i didn't anticpate any problems.
Cannot initialize Network (reason WSASYSNOTREADY)
So we shut down greenstone and removed the software and tried the install again with the same result. We shut it down and then checked to see if anything was conflicting with it's web server. We opened a terminal window and ran netstat:
And oddly enough there were 2 instances of a web server running on port 80. We ran a ports check cports using and found two processes listed but when we went to kill them in the windows task manager they were not there! Looks like greenstone did not clean up after itself!
Only a hard reset got rid of them. We next did an install of Greenstone but not as the administrator and this installed the program to users\gnickers\greenstone and it ran fine. We shut it down and checked the active ports with netstat and the httpd instance had shut down correctly.
So the change is that unlike 2.84 the new version cannot be installed using admin privileges (which makes sense). Would have be nice to put this in the release notes.
Those who are installing greenstone for the first time may also run into the problem of some other program using port 80 which is the standard port for web traffic. Older versions of Skype were bad for doing this.
To check type cmd in the start text box and press ENTER. The run netstat using the above syntax. The cports program (search on Google) provides more info that netstat but you must run it as admin. If you have Skype using port 80 set your skype options in the Connection tab to use a different port such as 34378 or something. A list of ports is available on Wikipedia and other sources.
The other solution is to install Greenstone and then select Start > Programs > Greenstone 2.85 > Greenstone Server and select File, Settings from the menu. Now change the Port Number from 80 to something like 8080 or some other port not in use.
I removed greenstone 2.84 from my machine in prep for the new version. The old version had worked fine and had been installed as admin to c:\program files\greenstone. I also got another laptop over xmas for testing win stuff so i installed 2.85 to that. It runs Windows 7 Home Premium 64 bit (argh why so many versions?) and the install was straightforward and ended up in c:\program files\greenstone so i didn't anticpate any problems.
Ran Greenstone-2.85-windows.exe as Administrator and it installed OK to c:\progam files\greenstone but when I ran the GLI and the following error message was returned:
So we shut down greenstone and removed the software and tried the install again with the same result. We shut it down and then checked to see if anything was conflicting with it's web server. We opened a terminal window and ran netstat:
C:\Users\gnickers>netstat -an |find /i "Listening"
TCP 0.0.0.0:135 0.0.0.0:0
TCP 0.0.0.0:445 0.0.0.0:0
TCP 0.0.0.0:3390 0.0.0.0:0
TCP 0.0.0.0:5357 0.0.0.0:0
TCP 0.0.0.0:17500 0.0.0.0:0
TCP 0.0.0.0:34378 0.0.0.0:0
TCP 0.0.0.0:49152 0.0.0.0:0
TCP 0.0.0.0:49153 0.0.0.0:0
TCP 0.0.0.0:49154 0.0.0.0:0
TCP 0.0.0.0:49155 0.0.0.0:0
TCP 0.0.0.0:49156 0.0.0.0:0
TCP 127.0.0.1:80 0.0.0.0:0
TCP 0.0.0.0:135 0.0.0.0:0
TCP 0.0.0.0:445 0.0.0.0:0
TCP 0.0.0.0:3390 0.0.0.0:0
TCP 0.0.0.0:5357 0.0.0.0:0
TCP 0.0.0.0:17500 0.0.0.0:0
TCP 0.0.0.0:34378 0.0.0.0:0
TCP 0.0.0.0:49152 0.0.0.0:0
TCP 0.0.0.0:49153 0.0.0.0:0
TCP 0.0.0.0:49154 0.0.0.0:0
TCP 0.0.0.0:49155 0.0.0.0:0
TCP 0.0.0.0:49156 0.0.0.0:0
TCP 127.0.0.1:80 0.0.0.0:0
And oddly enough there were 2 instances of a web server running on port 80. We ran a ports check cports using and found two processes listed but when we went to kill them in the windows task manager they were not there! Looks like greenstone did not clean up after itself!
Only a hard reset got rid of them. We next did an install of Greenstone but not as the administrator and this installed the program to users\gnickers\greenstone and it ran fine. We shut it down and checked the active ports with netstat and the httpd instance had shut down correctly.
So the change is that unlike 2.84 the new version cannot be installed using admin privileges (which makes sense). Would have be nice to put this in the release notes.
Those who are installing greenstone for the first time may also run into the problem of some other program using port 80 which is the standard port for web traffic. Older versions of Skype were bad for doing this.
To check type cmd in the start text box and press ENTER. The run netstat using the above syntax. The cports program (search on Google) provides more info that netstat but you must run it as admin. If you have Skype using port 80 set your skype options in the Connection tab to use a different port such as 34378 or something. A list of ports is available on Wikipedia and other sources.
The other solution is to install Greenstone and then select Start > Programs > Greenstone 2.85 > Greenstone Server and select File, Settings from the menu. Now change the Port Number from 80 to something like 8080 or some other port not in use.
1 comment:
Hi
Thanks for the solution. It works. I change the port in Greenstone Server
Post a Comment