Subject: RE: You are not authorized to view this page error
> The issue appears to be with Apache at this juncture, since I get the
> error with a index.html page.
>
> Do I need to do anything with Apache, or is the HTTP Error
> 403 - Forbidden error caused by XP configuration?
> The issue appears to be with Apache at this juncture, since I
> get the error with a index.html page.
>
> Do I need to do anything with Apache, or is the HTTP Error
> 403 - Forbidden error caused by XP configuration?
Are you running Apache with a specific user account other than SYSTEM? If
so
ror
with a index.html page.
Do I need to do anything with Apache, or is the HTTP Error 403 - Forbidden
error caused by XP configuration?
Andy
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 15, 2007 11:36 AM
To: CF-Talk
Subject: RE: You are not aut
> OK. It looks like I've got MX 7 and Apache 2.2 up and
> running, but when I try to access MX Administration, I get
> HTTP 403 error. I never completed the WSCONFIG.JAR upgrade
> without errors, but I was able to set the MX Server to Apache
> 2.2 via the Web Server Configuration Tool.
To u
> OK. The problem with the upgrade appears to be that the Jrun
> server can't be found:
>
> 08/15 08:36:41 error JRun server coldfusion cannot be
> found on host 127.0.0.1. Confirm that JRun server 127.0.0.1
> is started.
>
> What am I missing?
Make sure you've upgraded the jar file a
olmes [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 15, 2007 7:27 AM
To: CF-Talk
Subject: Re: You are not authorized to view this page error
Are you on windows or *nix?
Regardless, you'll need to do that upgrade successfully - the connector has
to be upgraded for Apache 2.2 to work.
On 8/1
Are you on windows or *nix?
Regardless, you'll need to do that upgrade successfully - the
connector has to be upgraded for Apache 2.2 to work.
On 8/15/07, Andy <[EMAIL PROTECTED]> wrote:
> OK. It looks like I've got MX 7 and Apache 2.2 up and running, but when I
> try to access MX Administration
OK. It looks like I've got MX 7 and Apache 2.2 up and running, but when I
try to access MX Administration, I get HTTP 403 error. I never completed
the WSCONFIG.JAR upgrade without errors, but I was able to set the MX Server
to Apache 2.2 via the Web Server Configuration Tool.
Can anyone point
8 matches
Mail list logo
