|
| |
Some of us have had a difficult time getting the 60 Minute Intranet Kit
(60Mik) to fly. Several problems have been experienced by many, including
me. Below is a brief discussion of these problems as I have experienced
them.
 | The 60Mik template fails to appear in the FrontPage list of web
templates. Consequently, one cannot start the wizard to build the
60Mik. This definitely turns the 60Mik into a 60Hour-ik, a
60Day-ik, or even a 60Month-ik. Microsoft has issued a KB article that
is supposed to cure the problem--Q235421
- FP2000: 60 Minute Intranet Kit Does Not Appear in FrontPage.
The article points out that the 60Mik installation package assumes that both
FP and 60Mik are installed in their default directories. If
FrontPage is not installed in the expected directory, the 60Mik will not put
its wizard in the proper directory. Hence, the solution is to move the
60Kik Wizard folder from where it was installed to the FrontPage 2000
template folder. Many have reported that this cured all their
problems. It did not work for me. Turns out, the instructions
are to move the directory to the following path. That path was
there. I so moved the Wizard folder there. It still did not
appear in FrontPage. Turns out, I had forgotten that I had installed
FrontPage to a different disk. One does have that option. Once I
finally moved the 60Mik Wizard folder to the specified directory where
FrontPage was actually installed, the template appeared in FrontPage and I
could select it to create the 60Mik. The moral of this tale is that,
if there are no other wizards or templates already in the folder in which
you are moving the 60Mik Wizard folder, then find out where you have really
installed FrontPage, and move it to where the existing templates really are. |
| When I finally found the round tuit, and started to create the 60Mik, I
first created a virtual web server for it. I then called up
FrontPage, selected the 60Mik template, specified the web server for it to
use, gave it all the business data, and plunked the magic finish
button. There was a protracted sproing, and then it started spewing
error messages to the effect that executable could not be loaded to the
directory, OK? Well, not OK, but how long do you want to look at said
message. And it does this for a whole bunch of directories. When
I looked at the physical web site, the directories had been created, but
they were all empty. Just hunky-dory. I then spent some time
trying to set permissions so that it could do its thing. But after
several attempts, concluded that it was not going to happen. It had
already been 6 months since I had downloaded the package. I had dark
thoughts. Finally, one bright afternoon, perhaps from reading a
message on the board, or perhaps from that mysterious processing that goes
on below consciousness, the thought materialized that the 60Mik runs on PWS.
If it was designed to run on PWS, which on my Win2K workstation, had
appeared as a Default Web Site, perhaps it would fly on my Default Web
Site on the server. Quick as a flash, I called up the 60 Mik Wizard
out of its Oaken directory, directed it to build the 60Mik on the server's
Default Web Site, plunked the magic Finish button, and it whirred and
clicked, transferred files and applications for quite some time, and finally
said the 60Mik had been successfully installed. Everything seems to
work, except the news doesn't show, but I can edit the individual news
items. So, it could have been a 60Minute-ik, if I had just had a
default workstation using a default PWS, etc.
|
60 MIK Redux
A long time after this had become the 60,000MIK, I solved the unwillingness
of IIS to configure virtual web servers, which had prevented me from deploying
the 60 MIK to its own web server. I figured that it was time to see if
this package really worked as it should. So, from my workstation, I opened
FP2000, chose to make a new web, designated the VWS as the target, chose the 60
MIK template, answered the business questions and let it rip. It whirred
and clicked as usual, and finally said it had created the web. I browsed
to it, and it had a few problems, but all was there. This time it took
less than 60 minutes to get it up and running. Wait for your lucky day,
then install and deploy the product. It will probably be a nicer
trip. Be prepared to ask for advice in the public intranet newsgroup.
|
