Problem running post-install step.

[Zy Danielson]

Error message "Problem running post-install step" when installing from Windows Installer. After installation, attempting to display the test page at 127.0.0.1:8885/index.cfm (I used port 8885 instead of the default 8888) gives ERR_CONNECTION_REFUSED.

Not sure what I did wrong or what to do from here. I am using Windows 10.

Please advise.

Thanks,

Zy

[Bilal]

What happens when you uninstall and rub the install with default values.
Thereafter you can easily change the tomcat we port.

[Zy Danielson]

Okay, I uninstalled and tried to install using default values. It accepted 8888 as the port, but said port 8009 (Tomcat APJ Port) was already in use. So I changed that to 8008.

Same error as before when attempting to load the test website.

If I am to install using all three default ports, I will have to go about finding out what is already using port 8009, and I'm not sure how to do that. I am a CFML developer since the days of Alliare, but I'm not all that well versed in Windows or Tomcat.

Any help you can give is appreciated. Or at least steer me in the right direction.

Thanks,

Zy

[Bilal]

Ok the fog is lifting.
Most likely you have another peace of software that is using tomcat and running.
This is conflicting with your attempted install.
Your tomcat logs in the Lucee install directory will tell you which ports failed in binding and most likely stopping the start of tomcat. There are a few ports that Tomcat uses by default (8005, 8009, and 8080) the Lucee install only changes the 8080 to 8888.
If you just wish to experiment with Lucee I would suggest you put it on Virtual Machine, that way you don't have to change anything on your local. Otherwise there sever.xml file in the configure directory has all the ports.
You can change all of them to different values and check whether tomcat will start and respond on web port.

Hth,
Bilal

[Zy Danielson]

Hello Bilal. An update on where I went with this and a further problem that has developed.

First of all, I am trying to replace two things:

1) The Railo 4 development environment on my Windows 10 machine.

2) The Railo 4 production environment running on a customer's ancient Windows Server 3 machine.

I ran into the initial problems concerning #1 when I started this thread. I solved it in probably an unusual way. I had Wampserver installed, but was not using it. So I started that service and configured it to start at boot time. Then I started the Lucee service manually and it ran fine. That bypassed the Tomcat problem since the Lucee installation itself was actually good. (Thank goodness!)

But now I am working on the #2 part of the problem. I held my breath (figuratively speaking) and attempted to download and install on my customer's Windows Server 3 machine. I got the error I have attached as err001.JPG over and over, a total of about 5 times. Then it told me the install was not successful. Lucee is there, but when I went in to try to start the service manually, I got the error I have attached as err006-Tomcat-Timout.JPG. I'm pretty much stuck on getting Lucee to run on my customer's server.

All I wanted to do is respond to the Railo fork by replacing Railo 4 with Lucee. As you can see, I'm not making much progress on my customer's production machine. Is there any further advice you might offer me?

Appreciation in advance,

Zy

[Zy Danielson]

Further Problem and worse:  Lucee won't uninstall from the Windows Server 3.

I had decided to uninstall and reinstall unchecking the IIS option, since the repeating error during the install seemed to be about IIS. But when I attempt to uninstall either using the uninstall option from the Lucee menu or from Control Panel > Add or Remove Programs, I get the attached error message.

Please tell me what I need to do to get rid of this bad installation so that I can start over.

Thanks,

Zy

[Zy Danielson]

More information and install.log

I've been saying Windows Server 3. Apologies, it is actually Windows Server 2003. See attached SystemProperties.JPG.

I did a new install over the old one without uninstalling, since the uninstall would not run. I did get more success, but the Lucee service will still not start. When I attempt to start it manually it gives a path not found error. See attached ManualStartError.JPG.

It did appear to successfully create an uninstall file this time, but I have not run it yet. Instead, I have uploaded the install.log file itself, in case that sheds more light for you. (It doesn't for me, as I'm not a Windows Server systems type guy.) See attached install.log.

[Bilal]

Zy,

for uninstallation:

please check you service control panel and see whether lucee is installed as service (which I am guessing it is).

If so, note the service name down. 

If the uninstall program does not fire you can manually remove the service.

To do so use  sc command

sc.exe delete <service name>

i.e.

sc.exe delete lucee

in windows 2003 you may need to download the Windows Resource Kit if not already installed to have the sc command.

Then, simply delete the lucee directory with files.

To remove the entry from the Add/Remove programs control panel I would google a bit. But most likely a registry change has to occur:

http://windowsxp.mvps.org/AddRemove.htm

I am not sure whether the latest installer supports Win 2003; however, you can do a war install  into a standard tomcat install instead.

This would require in general:

1) Install JRE

2) Install standard Tomcat service

3) Download and copy WAR file into the app directory, tomcat will expand and start it

4) Adjust tomcat to run expanded War file as default site

5) optional: Install connector to IIS 

Steps 1 and 2 should provide inside whether another service is interfering with Tomcat, which from your descriptions is very likely. 

HTH,

Bilal

[Zy Danielson]

Thank you. I was able to remove the service with sc.exe and deleted the directory with files. Then I attempted a fresh install using the installer without the IIS box checked. But unfortunately, I got the same result. So I removed the service and directory again. (This may answer the question of whether the current version of the installer supports Windows Server 2003. If so, then it appears it doesn't.)

Now I am preparing to follow the instructions you gave me for a war install. But I know very little about this process.

First of all, looking in Add/Remove Programs, I notice the following entry:

Java 2 Runtime Environment Standard Edition v1.2.2

This appears to have been installed in 2008. If I assume this is a good installation, then I need a compatible Tomcat.

Looking at https://tomcat.apache.org/whichversion.html, it appears that I will need the archived version 5.5.36 of Tomcat, which supports Java versions 1.4 and later. The next higher version of Tomcat (6.0.45) requires support of Java 5 and later. See attached table ApacheTomcatAndJREcompatibility.JPG.

Would you agree that I should extract the Apache Tomcat version 6.0.45 from the archive and install that?

- or -

Should I uninstall the JRE that is there now (v1.2.2) and install a later version of that to go with a later version of Tomcat?

Now, from researching the Oracle site, I find this: "Oracle has tested and certified the Java SE Development Kit 6 (JDK™) and the Java SE Runtime Environment 6 (JRE™) on the platforms listed on the table below." In that table, under Windows (32 bit) section, it lists Windows Server 2003 (R2, SP1, SP2). My customer has SP2. This would indicate that the Java SE 6 JRE might be a better option? (This, in turn, would allow installation of Tomcat 7.0.67, if I'm understanding that table correctly.)

I would suppose the answer depends on what will best support and allow the Lucee service to run. I hope you will be able to tell me that.

Thank you for your patience with me, Bilal, and thank you for all your help up to this point.

Best regards,

Zy

[Jordan Michaels]

Maybe this has already been said, but Windows 2003 stopped being supported by MS a while ago. You should really not be setting up new systems using it. Even the MS Extended Support has ended for it:

https://www.microsoft.com/en-us/server-cloud/products/windows-server-2003/

"Windows Server 2003 extended support ended on July 14, 2015"

For your own safety, you should not be using Windows 2003.

-Jordan

--
Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html
---
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/05b6091a-9534-43e7-a2ec-3a1a84e0cf16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Bilal]

Zy,

I would agree with Jordan that going on a supported version of Windows is probably a good plan. If you don't want to run it yourself you can do a cloud version on EC2 (Amazon) for cheap.

Having said that, I am not sure that Lucee is supported on Java 1.5. I have not run it with anything lower than 1.7. You can have multiple version of the JRE/JDK on the same windows instance. Just ensure that you are not changing the JAVA_HOME or PATH environmental variables. During the Window 2003 era we used to put JRE on the machine to support browser apps not for server services, especially if it has not been updated it would be a good sign for that. Checking might be a good idea.

It is very very likely that you have a previous installation of software on this machine that is blocking tomcat, thus you cannot use the standard ports. So, during the installation of Tomcat use different ports and ensure that Tomcat can start. Without this, you will not be able to proceed to the Lucee steps.

Nonetheless, I have recorded a video that goes through the Lucee deploy process with Tomcat from scratch (on Windows 7). If you wish to do the connector bit, please review the documentation re:Windows 2003. Again, not a good idea to run something unsupported.

https://youtu.be/-0lx1ZyJxaI

HTH,

Bilal

[Zy Danielson]

Hi Jordan,

Yes, I totally agree with you. However it's not my call. This is a very stubborn customer. I'm not in the position to refuse to work for him just because he's not ready to upgrade his server. I started telling him years ago that this would happen. He wasn't ready to move until the support actually ended. Now for the most entertaining part: the software he is using to run his entire business off that server is written in Clarion for DOS. And DOS isn't even supported anymore as a standalone OS. So you are correct, this customer is behind times and he knows it. However the system designed in Clarion is proprietary and quite complex. There is nothing out there "off the shelf" that can replace it. However, he is going to  use AccountMate, which will do for most of his systems except for his proprietary knitting machine modeling, and his real time pricing system for the products he manufactures and sells. What I'm doing is developing an Intranet to replace the proprietary code that will then feed information to the AccountMate software. So this Lucee Intranet is the step that will free him from Clarion. Once that is done, he will happily upgrade both his hardware and OS to the most current versions. It has been an interesting journey!

Bilal,

I'm about to review what you gave me in your last post now. Somehow I'll get Lucee running on that server so that we can complete the Lucee front end to AccountMate to prepare him for hardware/OS upgrade.

So, back to the present problem, getting Tomcat/Lucee running on his current setup.

I'll keep you posted until I reach success.

Again, thank you for your patience with me, and for all your help so far along the way.

Zy

[Zy Danielson]

Okay, as I was afraid of, the current version of the JRE would not install correctly on Windows Server 2003. So I removed it and successfully installed the JRE 1.6.0.45. certified by Oracle to run on the Windows Server 2003 SP2 32 bit. I installed it in the default C:\Program Files\Java\jre6.  This appears to be running correctly as shown in

cmd > c:\windows\system32 java -version: java version "1.6.0_45"

Next I installed the version of Tomcat that is listed in the Apache Tomcat documentation (see attaced ApacheTomcatAndJREcompatibility.JPG). This was version 5.5.36. I used all default ports and installed following your video presentation. However, the Tomcat service did not start. When I attempted to start the service manually, I got the error shown in the attached TomcatStartupError.JPG. The error is "Error 3: The system cannot find the path specified."

Interesting to note this is the same error I was getting with the current Windows Installer from the Lucee site.

This time, however, I don't see any log files showing the problem.

Are we back to port conflicts? I'm not sure how to go about investigating this, and I don't see any indication of an error suggesting a conflicting port.

At this point, I'm wondering if I should just forget this whole thing and use Lucee Express on my customer's machine to run the Intranet until we reach the point where he's ready to upgrade both his hardware and OS. Unless, of course, you have a suggestion of the next step I should take in trying to get Tomcat5 to start.

I'm not one to give up on a problem, but this one has me completely stumped. I'm beginning to feel reluctant to ask you good folks to spend more time helping me.

That said, any further advice you may have will certainly be appreciated.

[Zac Spitzer]

try running netstat to show what ports are listening with which associated processes

also being windows 2003, a reboot might help

--

Love Lucee? Become a supporter and be part of the Lucee project today! - http://lucee.org/supporters/become-a-supporter.html
---
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/47d9c0b8-ad38-4e53-ae55-fa5c02837869%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Zac Spitzer
+61 405 847 168

[Jordan Michaels]

If there are no log files found in your Tomcat/logs/ directory, then the
'path that cannot be found' probably has to do with your JRE settings.

I'd check your tomcat service control and see what your JRE settings
are. Are all your JRE paths pointing to the correct locations?

Warm Regards,
Jordan Michaels

> --
> Love Lucee? Become a supporter and be part of the Lucee project today! -
> http://lucee.org/supporters/become-a-supporter.html
> ---
> You received this message because you are subscribed to the Google
> Groups "Lucee" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to lucee+un...@googlegroups.com

> <mailto:lucee+un...@googlegroups.com>.

> To post to this group, send email to lu...@googlegroups.com

> <mailto:lu...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/lucee/47d9c0b8-ad38-4e53-ae55-fa5c02837869%40googlegroups.com
> <https://groups.google.com/d/msgid/lucee/47d9c0b8-ad38-4e53-ae55-fa5c02837869%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Zy Danielson]

Zac:

> try running netstat to show what ports are listening with which associated processes

See attached netstat.rtf which contains the output of netstat -a -n

Searching for default ports 8005 and 8009 produces nothing.

Searching for port 8080 only finds 18080, which I assume has nothing to do with 8080?

> also being windows 2003, a reboot might help

Thank you. Tried that, but no difference.

Jordan:

See attached VerifyingDirectoriesAndFiles.rtf

As you can see, I have verified that all files and/or directories exist where the Tomcat Service Control expects them to be.

If you look at attached set.txt which is the output of c:\set you can see there is no direct path specified to C:\Program Files\Java\jre6\bin\client\jvm.dll but does this matter?

Neither is there a JAVA_HOME environment variable. But do I need one?

Seems like I have done all I can think to do here. Any further suggestions?

Thanks,

Zy

[Jordan Michaels]

Hi Zy,

> but does this matter? Neither is there a JAVA_HOME environment
> variable. But do I need one?

It would only matter if this were the user account that's attempting to
start up Tomcat. IIRC the service control uses the Windows 'system' user
by default. If environment variables are required, it'd be a requirement
of the 'system' user's environment.

> I have verified that all files and/or directories exist

I concur, your JVM settings look okay as far as what they are in the
service control. Remind me, did you say there were no log files in the
Tomcat logs directory? If your JVM is set correctly then you should be
getting SOME kind of output in your Tomcat catalina.out log file.

I also notice you're running off the "F:" drive letter. Is that a remote
share of some kind? Does the Windows 'system' user have the permissions
it needs on that drive/share?

Warm Regards,
Jordan Michaels

On 02/19/2016 09:37 AM, Zy Danielson wrote:
> Zac:
>
> > try running netstat to show what ports are listening with which
> associated processes
>

> See attached *netstat.rtf* which contains the output of netstat -a -n

>
> Searching for default ports 8005 and 8009 produces nothing.
>
> Searching for port 8080 only finds 18080, which I assume has nothing
> to do with 8080?
>
>
> > also being windows 2003, a reboot might help
>
> Thank you. Tried that, but no difference.
>
>
> Jordan:
>

> See attached *VerifyingDirectoriesAndFiles.rtf*

> As you can see, I have verified that all files and/or directories exist
> where the Tomcat Service Control expects them to be.

> If you look at attached *set.txt *which is the output of c:\set you can

> see there is no direct path specified to C:\Program
> Files\Java\jre6\bin\client\jvm.dll but does this matter?
> Neither is there a JAVA_HOME environment variable. But do I need one?
>
> Seems like I have done all I can think to do here. Any further suggestions?
>
> Thanks,
> Zy
>
>

> --
> Love Lucee? Become a supporter and be part of the Lucee project today! -
> http://lucee.org/supporters/become-a-supporter.html
> ---
> You received this message because you are subscribed to the Google
> Groups "Lucee" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to lucee+un...@googlegroups.com
> <mailto:lucee+un...@googlegroups.com>.
> To post to this group, send email to lu...@googlegroups.com
> <mailto:lu...@googlegroups.com>.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/lucee/2917cb8d-8f48-4a0c-90d4-e682bc7191da%40googlegroups.com
> <https://groups.google.com/d/msgid/lucee/2917cb8d-8f48-4a0c-90d4-e682bc7191da%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Zac Spitzer]

Can you attach netstat -b which shows the executable name associated with the port?

To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/56C776BE.2070208%40viviotech.net.

For more options, visit https://groups.google.com/d/optout.