WinBatch Tech Support Home

Database Search

If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.

TechHome

ADSI
plus

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Error 243: Not a property of the object.

Keywords:   Error 243 Not a property of the object.

Question:

How about error 243...what is that?

Answer:

Error 243 is "Not a property of the object."

You get this if you try to set or get a property that does not belong to an ADSI object.

Question (cont'd):

Is it possible that my ADSI programs work well on NT4.0 servers with SP4 or SP5 and maybe not so well with SP6a loaded. I seem to have this problem. The program runs great on our development machines (SP4) but on servers with SP6a we get the 243 error. It almost seems as if it can't find the metabase. Our program prints the report header, the report footer, but nothing in between. It's supposed to be printing a few pieces of info from the metabase (servercomment, path, serverbindings). We know that these peices of info are present.

Besides, there is error checking in the event that these pieces of info (properties) are not present. We've tested our error checking with missing info, seems to be OK.

Later...

Well, I loaded SP6a onto our dev server and our ADSI program worked fine. On a customer's system they get an error 243. Is it possible somehow that their system doesn't have localhost? It has to, doesn't it?

They are running an active Web site. In our program we use the AdsPath=IIs://localhost/w3svc/web#

That path should be common to all IIS servers, shouldn't it?

Answer:

"localhost" is a place holder and should work as long as the script is run on the machine also running IIS.

Which property are you trying to access and are you trying to set or get the property?

Question (cont'd):

Well, like I say, it works great on all of our development machines. We sent the program to a client and within the first 5 seconds they get the 243 error. We are getting the Web index, ServerComment, ServerBindings, and the root\Path I checked, and all of of these items are mandatory in the metabase except the ServerComment. But we have error checking in place to handle that - and the error checking works. I can't figure out why it won't work on this clinet's machine. For some reason the program cannot get into the metabase.

Answer:

Have you checked ADSI client and IIS versions? I can't duplicate the problem here either.
Article ID:   W14513
Filename:   Error 243.txt
File Created: 2000:07:19:11:38:08
Last Updated: 2000:07:19:11:38:08