Anthony
|
| Posted: 08/27/2004, 9:40 AM |
|
I attempted to follow the Quick Start Tutorial, but got nowhere. I then attempted to publish an example that came with Studio 2.3.2.24. Neither worked.
I am getting two different error messages; both deal with Libraries not registered and it seems to have an issue with a line in the Classes.asp file
set mMessages = Server.CreateObject("Scripting.Dictionary")
I have search through the forums and the MSDN Library. I have installed the latest scripts and unregistered and registered several dll's.
I am running on a 2000 server. Service Pack 3, Latest MDAC, .net...etc.
Is there any hope?
|
|
|
 |
DonB
|
| Posted: 08/27/2004, 12:39 PM |
|
Your server is not granting permission to the scripting objects. The 0179
indicates you most likely have not published the web to a folder designated
as "Application" type in the IIS control panel (that is, the folder no doubt
appears as a yellow folder symbol instead of the blue globe symbol).
Fixing the 179 should take care of the 178.
--
DonB
http://www.gotodon.com/ccbth
"Anthony" <Anthony@forum.codecharge> wrote in message
news:6412f641471488@news.codecharge.com...
> I attempted to follow the Quick Start Tutorial, but got nowhere. I then
> attempted to publish an example that came with Studio 2.3.2.24. Neither
> worked.
>
> I am getting two different error messages; both deal with Libraries not
> registered and it seems to have an issue with a line in the Classes.asp
file
> set mMessages = Server.CreateObject("Scripting.Dictionary")
>
> I have search through the forums and the MSDN Library. I have installed
the
> latest scripts and unregistered and registered several dll's.
>
> I am running on a 2000 server. Service Pack 3, Latest MDAC, .net...etc.
>
> Is there any hope?
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
 |
Anthony
|
| Posted: 08/30/2004, 9:22 AM |
|
Thanks for the reply.
I haven't seen a 179 error. It is mainly the 177 that is the problem.
Server object, ASP 0177 (0x8002801D)
Library not registered.
/employee/Classes.asp, line 2949
I have changed the folder options and the properties in IIS and nothing has changed.
|
|
|
 |
DonB
|
| Posted: 08/30/2004, 9:52 AM |
|
Oops, I can't read. Anyway, the 177 is in the same realm as 179 -
permissions too restricted to allow creating an object. Look further at the
application protection level (try "Low" if it's Medium or High). Check the
account (probably IUSR_xxx where "xxx" is the servername) and that it has
rights to execute in the web folder containing the application (if "medium"
protextion, then the IWAM_xxx account is applicable). Check the execute
permissions is "script only".
There are a number of potential issues with IIS's permissions on COM objects
that requires using the dcomcnfg tool to resolve. That's all detailed at
support.microsoft.com if you search there for the errors you noted.
Normally this is not necessary unless you, or someone else, has tinkered
with the IUSR_xxx accounts, changed to other accounts or altered the IIS
configuration in some way.
--
DonB
http://www.gotodon.com/ccbth
"Anthony" <Anthony@forum.codecharge> wrote in message
news:64133543bbf5b1@news.codecharge.com...
> Thanks for the reply.
>
> I haven't seen a 179 error. It is mainly the 177 that is the problem.
>
> Server object, ASP 0177 (0x8002801D)
> Library not registered.
> /employee/Classes.asp, line 2949
>
> I have changed the folder options and the properties in IIS and nothing
has
> changed.
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
 |
|