ASP -- Server.CreateOb ject("MSWC.Next Link" problem on Vista with IIS 7

[John Connic]

Hi All:

I just setup a new machine with Vista Business Edition and IIS 7.
I had to turn on IIS 7 attributes including the IIS Manager. Not sure what
options I needed I turn them all on that even remotely look like I might
need them.

The IIS Manager looks total foreign to me but eventually I figure how to add
a virtual folder. I then started making script files in html, javascript and
vbscript. I would run them through IIS 7 using the URL:
http://localhost/../filename. This all worked fine and I was able to try
most of the code that I had used on IIS 6 under XP.

I then start adding ASP server-side calls to the script. I tried several
objects: Request, Response..etc. and they worked fine. The problem started
when I started using the Server object.

In particular when I added the line:

objCLC = Server.CreateOb ject("MSWC.Next Link")

When I add this line the Web Browser indicates that there is server problem.
I believe that these calls are from an activex object so is it possible that
somewhere in the IIS 7 configuration I haven't allow permission for activex
objects?

Any help will be greatly appreciated

[Jon Paal [MSMD]]

make sure Nextlink.dll is installed on the machine

[John Connic]

Hi Jon:

I did check for it in the system32 folder and it was not their. Is there
somewhere else I should look?
Also, if it is not there what do I do to get installed. I have Vista
Business Edition and in the install/open section under the Control Panel I
checked all the options including "ASP.NET", shouldn't that install it ?

"Jon Paal [MSMD]" <Jon nospam Paal @ everywhere dot comwrote in message
news:13******** *****@corp.supe rnews.com...

make sure Nextlink.dll is installed on the machine

[Daniel Crichton]

John wrote on Mon, 16 Jul 2007 10:17:30 -0400:

Hi All:

I just setup a new machine with Vista Business Edition and IIS 7.
I had to turn on IIS 7 attributes including the IIS Manager. Not sure what
options I needed I turn them all on that even remotely look like I might
need them.

The IIS Manager looks total foreign to me but eventually I figure how to
add a virtual folder. I then started making script files in html,
javascript and vbscript. I would run them through IIS 7 using the URL:
http://localhost/../filename. This all worked fine and I was able to try
most of the code that I had used on IIS 6 under XP.

I then start adding ASP server-side calls to the script. I tried several
objects: Request, Response..etc. and they worked fine. The problem started
when I started using the Server object.

In particular when I added the line:

objCLC = Server.CreateOb ject("MSWC.Next Link")

When I add this line the Web Browser indicates that there is server
problem. I believe that these calls are from an activex object so is it
possible that somewhere in the IIS 7 configuration I haven't allow
permission for activex objects?

Any help will be greatly appreciated

The MSWC components were part of the old IIS Resource Kit installation, they
are not shipped with IIS. They were also part of PWS. Unless you can find
the old installation for IIS4 you won't be able to get this running on your
IIS7 setup, and even if you do find the old installation files there's no
guarantee that they'll work.

Dan

[Jon Paal [MSMD]]

these folks may be able to help with iis7 and classic asp questions

http://forums.iis.net/1044.aspx

[John Connic]

Hi Dan:

Thanks for your help. So what you are saying IIS 7.0 doesn't fully support
ASP and that there is some other mechanism for creating objects! Is this
also true that you can not create any objects with server.createob ject or is
next link the only case?

I did look on my XP machine which I believe has IIS5 and the nextlink dll is
there. As far I know I didn't install a IIS SDK to make this happen. It is
possible that I have put a VS SDK on this machine at some time. Maybe there
is IIS7 SDK ?
"Daniel Crichton" <ms****@worldof spack.comwrote in message
news:%2******** ********@TK2MSF TNGP05.phx.gbl. ..

John wrote on Mon, 16 Jul 2007 10:17:30 -0400:

Hi All:

I just setup a new machine with Vista Business Edition and IIS 7.
I had to turn on IIS 7 attributes including the IIS Manager. Not sure

what

options I needed I turn them all on that even remotely look like I might
need them.

The IIS Manager looks total foreign to me but eventually I figure how to
add a virtual folder. I then started making script files in html,
javascript and vbscript. I would run them through IIS 7 using the URL:
http://localhost/../filename. This all worked fine and I was able to

try

most of the code that I had used on IIS 6 under XP.

I then start adding ASP server-side calls to the script. I tried several
objects: Request, Response..etc. and they worked fine. The problem

started

when I started using the Server object.

In particular when I added the line:

objCLC = Server.CreateOb ject("MSWC.Next Link")

When I add this line the Web Browser indicates that there is server
problem. I believe that these calls are from an activex object so is it
possible that somewhere in the IIS 7 configuration I haven't allow
permission for activex objects?

Any help will be greatly appreciated

The MSWC components were part of the old IIS Resource Kit installation,

they

are not shipped with IIS. They were also part of PWS. Unless you can find
the old installation for IIS4 you won't be able to get this running on

your

IIS7 setup, and even if you do find the old installation files there's no
guarantee that they'll work.

Dan

[Bob Barrows [MVP]]

John Connic wrote:

Hi Dan:

Thanks for your help. So what you are saying IIS 7.0 doesn't fully
support ASP

No, what he is saying is it might not support "stuff" that was included
after-the-fact, such as the MSWC components. I've been developing with
ASP for years and i've never used these things.

And given the new ASP.Net world, you are unlikely to get much sympathy
for the failure to support deprecated components.

and that there is some other mechanism for creating
objects!

Huh? How did you come to that interpretation?

Is this also true that you can not create any objects with
server.createob ject or is next link the only case?

Read what he said closely: NextLink _might_ be _one of_ the relevant
cases. The only way to find out is to make sure it is properly
installed.
Server.CreateOb ject works fine for properly installed, supported, dlls
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Daniel Crichton]

John wrote on Tue, 17 Jul 2007 08:45:58 -0400:

Hi Dan:

Thanks for your help. So what you are saying IIS 7.0 doesn't fully support
ASP and that there is some other mechanism for creating objects! Is this
also true that you can not create any objects with server.createob ject or
is next link the only case?

IIS7 doesn't ship with the MSWC components. I use ASP and
Server.CreateOb ject without problems on IIS7 and IIS6 - but I know that I
don't have the MSWC components, so I know that calls to those won't work.
IIS fully supports ASP - but it doesn't let you instantiate components if
they're not installed!

I did look on my XP machine which I believe has IIS5 and the nextlink dll
is there. As far I know I didn't install a IIS SDK to make this happen. It
is possible that I have put a VS SDK on this machine at some time. Maybe
there is IIS7 SDK ?

Are you sure you didn't install the components from elsewhere on that other
machine? I have XP on my PC right here and there is no nextlink.dll, and I
do have IIS5 installed. I haven't installed the SDK, or the Resource Kit
tools.

Dan

[Mike Brind]

"Daniel Crichton" <ms****@worldof spack.comwrote in message
news:Oe******** ******@TK2MSFTN GP02.phx.gbl...

John wrote on Tue, 17 Jul 2007 08:45:58 -0400:

>Hi Dan:

Thanks for your help. So what you are saying IIS 7.0 doesn't fully
support
ASP and that there is some other mechanism for creating objects! Is this
also true that you can not create any objects with server.createob ject or
is next link the only case?

IIS7 doesn't ship with the MSWC components. I use ASP and
Server.CreateOb ject without problems on IIS7 and IIS6 - but I know that I
don't have the MSWC components, so I know that calls to those won't work.
IIS fully supports ASP - but it doesn't let you instantiate components if
they're not installed!

>I did look on my XP machine which I believe has IIS5 and the nextlink dll
is there. As far I know I didn't install a IIS SDK to make this happen.
It
is possible that I have put a VS SDK on this machine at some time. Maybe
there is IIS7 SDK ?

Are you sure you didn't install the components from elsewhere on that
other machine? I have XP on my PC right here and there is no nextlink.dll,
and I do have IIS5 installed. I haven't installed the SDK, or the Resource
Kit tools.

Mine appears in C:\Windows\syst em32\inetsrv on XP Pro with IIS 5.1. I
didn't knowingly install the SDK, unless it goes in as part of the full
install for IIS.

--
Mike Brind

[Mike Brind]

"John Connic" <jo*********@ng c.comwrote in message
news:%2******** ********@TK2MSF TNGP03.phx.gbl. ..

>
Now to issue at hand, do you or one of your Microsoft cronies know where I
can get this nextlink.dll that is causing the problem. Now from what Dan
told me the server.createob ject(..) construct appears to work OK but not
with "MSWC.NextLink" .

You can google 'nextlink.dll', and plenty of sites offer downloads:
http://www.dllbank.com/n/nextlink.dll-download.html, for example. Or you
can find an older machine that has it and copy it from there, registering it
on your new machine.

Server.CreateOb ject("...") will work for any installed and registered dll,
as Bob said.

MSWC was never "part of" ASP. It was a library of components that you could
use from ASP. That's why you have to use the built-in ASP Server object to
instantiate objects from the MSWC library.

--
Mike Brind