P
Paul
Hi,
I am not sure if this is the correct group to be posting this to so I
will give it a try.
I have FrontPage 2000 and FrontPage 2002 that I use to modify my web
sites with from two different places. Is there a problem with doing
this or should I stick with only one version? If this is a problem,
what are the issues?
My Web presents provider just upgraded from windows 2000 to windows
2003. I am having so many problems with the site now, I am about to
have a breakdown. Because I use FrontPage, I have sub webs defined.
I have always had a global.asa file inside of one of these sub webs
and it has worked fine, well almost. Since the conversion, I have
been having problem with something called an "Application Starting
Point". I don't know anything about this, could someone explain the
relationship between this and the global.asa file. Do I really need
this sub web to have an application starting point defined? Was this
an issue in windows 2000? How is it different in 2003 verses 2000?
Here is some of the things I am experiencing.
1). I have custom errors define for the domain. After the conversion
they where working fine in the domain but not in the sub web. In the
sub web, I was getting the default errors. After many days of
complaining about this, They created an application starting point and
the problem went away. Kinda!
2). I create an object in global.asa with this line of code:
<Object Runat="Server" Scope="application" ID="dOnlineUsers"
ProgID="Scripting.Dictionary"></Object>
This object is used through out the sub web to track pieces of
information. This object intermittently ceases to exist and no one
can tell me why. The is no code that destroys it. It should persist
as long as the application is active. If I modify the global.asa file
a little bit and save it, the object comes back. Someone at the
support center tried removing the application starting point ant it
stopped working all together. I converted the sub web to a folder and
then back to a sub web and it still did not work. Only creating an
application starting point got it back again. Yet after a while the
object just ceases to exist and everything is in kayos because most of
the pages depend on it. After almost two weeks of working on it, the
support center asked me if I was saying that the code in the
global.asa file was changing on me.
3). I have a control center at my web presents provide that allows me
to change the file permissions in the folders in the web. I don't
fully understand what it is doing, but I am told it is changing the NT
permissions. There is a User called Everyone that can have Read,
Write, Execute and delete permissions assign to it. I have some
folders in the sub web and the domain that have files that are written
to from some asp code. In order for it to work, the permissions have
to be set to include Write or there are permission errors generated.
I also have a folder that I remove all permissions from the Everyone
user so that I am challenged for a user name and password. I went
through the domain and had to set all of these permissions after the
conversion because they where all set to the default of Read, Execute
and nothing was working. I was going through the web pages with a
browser and found that things stopped working again. I checked the
permissions and they had changed. I was not in FrontPage or the
Control Center when this happened. This has happened several times
since the conversion. I have to check them every hour to make sure
the permissions are correct. Most of the times, I change them back
and call support to see why they changed. They see that I changed
them and say that I did it. Today, I was not in FrontPage, nor was I
in the Control center and they changed. I did not change them back
and this time when I called, they could not explain how they got
changed. Latter I got an email with this explanation:
The only way file permissions can be changing is if Front
Page is doing it when you are publishing, you are trying to use 2
different
systems to control access one is the control center which is changing
NT
file permission and the other is FrontPage which uses its own security
but
is also effects NT file permissions.
And I just got finished telling them that I don't use the publish
option and I wasn't in FrontPage or the Control center when It
happened.
I have come to the conclusion that these people are not capable of
solving this problem or they just don't want to or don't care. I also
know That I can't solve it either. So here I am, asking if someone
could please help me unravel this mystery.
Thanks,
Paul Coleman
I am not sure if this is the correct group to be posting this to so I
will give it a try.
I have FrontPage 2000 and FrontPage 2002 that I use to modify my web
sites with from two different places. Is there a problem with doing
this or should I stick with only one version? If this is a problem,
what are the issues?
My Web presents provider just upgraded from windows 2000 to windows
2003. I am having so many problems with the site now, I am about to
have a breakdown. Because I use FrontPage, I have sub webs defined.
I have always had a global.asa file inside of one of these sub webs
and it has worked fine, well almost. Since the conversion, I have
been having problem with something called an "Application Starting
Point". I don't know anything about this, could someone explain the
relationship between this and the global.asa file. Do I really need
this sub web to have an application starting point defined? Was this
an issue in windows 2000? How is it different in 2003 verses 2000?
Here is some of the things I am experiencing.
1). I have custom errors define for the domain. After the conversion
they where working fine in the domain but not in the sub web. In the
sub web, I was getting the default errors. After many days of
complaining about this, They created an application starting point and
the problem went away. Kinda!
2). I create an object in global.asa with this line of code:
<Object Runat="Server" Scope="application" ID="dOnlineUsers"
ProgID="Scripting.Dictionary"></Object>
This object is used through out the sub web to track pieces of
information. This object intermittently ceases to exist and no one
can tell me why. The is no code that destroys it. It should persist
as long as the application is active. If I modify the global.asa file
a little bit and save it, the object comes back. Someone at the
support center tried removing the application starting point ant it
stopped working all together. I converted the sub web to a folder and
then back to a sub web and it still did not work. Only creating an
application starting point got it back again. Yet after a while the
object just ceases to exist and everything is in kayos because most of
the pages depend on it. After almost two weeks of working on it, the
support center asked me if I was saying that the code in the
global.asa file was changing on me.
3). I have a control center at my web presents provide that allows me
to change the file permissions in the folders in the web. I don't
fully understand what it is doing, but I am told it is changing the NT
permissions. There is a User called Everyone that can have Read,
Write, Execute and delete permissions assign to it. I have some
folders in the sub web and the domain that have files that are written
to from some asp code. In order for it to work, the permissions have
to be set to include Write or there are permission errors generated.
I also have a folder that I remove all permissions from the Everyone
user so that I am challenged for a user name and password. I went
through the domain and had to set all of these permissions after the
conversion because they where all set to the default of Read, Execute
and nothing was working. I was going through the web pages with a
browser and found that things stopped working again. I checked the
permissions and they had changed. I was not in FrontPage or the
Control Center when this happened. This has happened several times
since the conversion. I have to check them every hour to make sure
the permissions are correct. Most of the times, I change them back
and call support to see why they changed. They see that I changed
them and say that I did it. Today, I was not in FrontPage, nor was I
in the Control center and they changed. I did not change them back
and this time when I called, they could not explain how they got
changed. Latter I got an email with this explanation:
The only way file permissions can be changing is if Front
Page is doing it when you are publishing, you are trying to use 2
different
systems to control access one is the control center which is changing
NT
file permission and the other is FrontPage which uses its own security
but
is also effects NT file permissions.
And I just got finished telling them that I don't use the publish
option and I wasn't in FrontPage or the Control center when It
happened.
I have come to the conclusion that these people are not capable of
solving this problem or they just don't want to or don't care. I also
know That I can't solve it either. So here I am, asking if someone
could please help me unravel this mystery.
Thanks,
Paul Coleman