asp.net on server 2003 with IIS NOT installed, System.DllNotFoundException: Unable to load DLL (aspn

[EP]

When running my asp.net hosting service (asp.net without IIS), on server
2003 with IIS not installed, I get the following when trying to process a
request.
"System.DllNotFoundException: Unable to load DLL (aspnet_isapi.dll)."

Of course the dll is able to be found, it's still in the framework directory
and for grins I even put it in my service's local directory. This is apparantly
server 2003 not allowing asp.net to be run if IIS was not installed. Is
there any way around this?

This works on win2000, xp with and without IIS, and on server 2003 with IIS.

 

[Juan T. Llibre]

If you can get ASP.NET to run without IIS having been installed,
unless you are running another web server which can host the
ASP.NET processes, like Cassini, I'll give you a medal.

How do you expect ASP.NET to run, if not on IIS ?
Did you write a web server for ASP.NET to run on ?

re:

for grins I even put it in my service's local directory

I find that illogical actions are not a source of humor.
OTOH, I grin at what you attempted to do... ;-)

 

[EP]

Well I've been working on this since yesterday, and found the solution about
10 minutes after posting here!!!
If anyone else has this problem, simply run aspnet_regiis with IIS uninstalled,
and your asp.net runtime will start working again.


In response to Juan, yes our service hosts it's own web server which was
loosly based on cassini, and exposes web services.



Hello Juan,

 

[Juan T. Llibre]

re:

If anyone else has this problem, simply run aspnet_regiis with IIS uninstalled, and your
asp.net runtime will start working again.

Huh ?

Didn't you say that you are *not* running IIS ?
As its name indicates, aspnet_regiis registers asp.net with IIS!

If there's no IIS, it can't register asp.net with it.

re:

In response to Juan, yes our service hosts it's own web server which was loosly based on
cassini, and exposes web services.

I figured as much.
I don't understand how aspnet_regiis can register it with your web server, though.

If your web server is based on Cassini, it should run asp.net files out of the box.

 

[EP]

Yes, that is what one would think. But in reality, server 2003 is different.
aspnet_regiis apparantly does some registry settings or sets other switches
which the asp.net framework looks for while on 2003.

And yes, one would think that aspnet_regiis wouldn't have any effect if iis
is not there, but it does.

If your web server is based on Cassini, it should run asp.net files
out of the box.

one would think so, But it doesn't. The .net framework behaves differently
on server 2003, which is why the sp1 redistributable for .net 1.1 has a different
redistributable file for server 2003.

while it's counter-intuitive, put very simply... if you uninstall IIS and
no not run aspnet_regiis, you get DllNotFound(asp_isapi.dll). Once you run
aspnet_regiis, it works.

 

[Juan T. Llibre]

re:

the sp1 redistributable for .net 1.1 has a different
redistributable file for server 2003.

It does ?

http://www.microsoft.com/downloads/...4f-088e-40b2-bbdb-a83353618b38&displaylang=en

says differently...

"Supported Operating Systems: TabletPC; Windows 2000; Windows 2000 Advanced Server;
Windows 2000 Professional Edition ; Windows 2000 Server; Windows 2000 Service Pack 2;
Windows 2000 Service Pack 3; Windows 2000 Service Pack 4; Windows 98; Windows 98
Second Edition; Windows ME; Windows NT; Windows Server 2003 Service Pack 1 for
Itanium-based Systems; Windows Server 2003, Datacenter Edition for 64-Bit Itanium-Based
Systems; Windows Server 2003, Datacenter x64 Edition; Windows Server 2003, Enterprise
Edition for Itanium-based Systems; Windows Server 2003, Enterprise x64 Edition; Windows
Server 2003, Standard x64 Edition; Windows XP; Windows XP 64-bit; Windows XP for
Itanium-based Systems Version 2003; Windows XP Home Edition ; Windows XP Media
Center Edition; Windows XP Professional 64-Bit Edition (Itanium) ; Windows XP Professional
64-Bit Edition (Itanium) 2003; Windows XP Professional Edition ; Windows XP Service Pack
1;
Windows XP Service Pack 2."

All operating system get the same .Net Framework's SP1.

Maybe you're operating on assumptions, instead of facts ?

 

[EP]

Well juan, I posted a problem and the resulting solution. I'm not sure why
you refuse to accept my first-hand experience. Have you tried it? I'm also
not sure why you feel it necessary to try to prove me wrong in a situation
that you have no experience in. It almost seems you have some religious
belief about the way that asp.net works on server 2003 and the way the service
pack is distributed. I'm very sorry if I've disappointed you, and didn't
mean to make your belief system come crashing down.

It does ?

Yes it does.
Microsoft .NET Framework 1.1 Service Pack 1 for Windows Server 2003
http://www.microsoft.com/downloads/...F7-2CB7-4864-8623-A1038563DF23&displaylang=en

http://www.microsoft.com/downloads/details.aspx?familyid=a8f5654f-088e
-40b2-bbdb-a83353618b38&displaylang=en

says differently...

You posted a list of special editions of server 2003, for x64 and itanium.
Ok, i'll be more specific. I am running server 2003 standard edition. I
am not running one of the special cases from your list....

Windows Server 2003 Service Pack 1 for Itanium-based Systems;
Windows Server 2003, Datacenter Edition for 64-Bit Itanium-Based Systems;
Windows Server 2003, Datacenter x64 Edition;
Windows Server 2003, Enterprise Edition for Itanium-based Systems;
Windows Server 2003, Enterprise x64 Edition;
Windows Server 2003, Standard x64 Edition;

Maybe you're operating on assumptions, instead of facts ?

no, i am operating on facts and first-hand experience. I'm sorry you assumed
otherwise.

Thanks
-Eric

 

[richard.hein]

Ha! That was a very funny, and enlightening thread. Juan, you really
have to think before you post. You're an ASP.NET MVP for pity's sake,
so before you start being a smart-ass do some extra research.

 

[Juan T. Llibre]

re:

Well juan, I posted a problem and the resulting solution.

That part I accepted.

re:

I'm not sure why you refuse to accept my first-hand experience.

Because I can't stand incorrect information being disseminated ?

You posted that :

the sp1 redistributable for .net 1.1 has a different redistributable file for server
2003.

That's plainly incorrect.
I did *not* refer to your other statements.

re:

Ok, i'll be more specific. I am running server 2003 standard edition.

OK, where is the "special" sp1 edition for server 2003 standard edition ?

re:

"It almost seems you have some religious belief about the way that asp.net works on
server 2003 and the way the service pack is distributed."

I'll skip answering that.

When you find a special sp1 edition for
server 2003 standard edition, I might change my mind.

 

[Juan T. Llibre]

Think again, and then post again.
See the reply just sent to EP's post.





Ha! That was a very funny, and enlightening thread. Juan, you really
have to think before you post. You're an ASP.NET MVP for pity's sake,
so before you start being a smart-ass do some extra research.

 

[EP]

I'm not sure why you refuse to accept my first-hand experience.

Because I can't stand incorrect information being disseminated ?

which incorrect information?

That's plainly incorrect.
?

OK, where is the "special" sp1 edition for server 2003 standard
edition ?

my god...

Microsoft .NET Framework 1.1 Service Pack 1 for Windows Server 2003
http://www.microsoft.com/downloads/...F7-2CB7-4864-8623-A1038563DF23&displaylang=en

If you look at the operating sysems on that page, it lists "Windows server
2003". It is for all version of server 2003 other than the special editions
you listed.

 

[EP]

and another thing...
you keep telling me i'm wrong and am posting incorrect information, but have
you installed sp1 on 2003? Have you distributed a product cd that included
dotnet and it's service packs? Have you tried installing the link you sent
on a normal version of 2003? I have.

 

[EP]

What does he need to think about?

Juan please put your theories to the test...
Install server 2003 without IIS and try cassini, it won't work
try using that servicepack you posted on server 2003 (not itanium or x64),
it will tell you it can't install

 

[Juan T. Llibre]

re:

have you installed sp1 on 2003?

Since it was in Beta.

 

[Juan T. Llibre]

re:

my god...

You *still* have not answered my question :

Where is the "special" sp1 edition for server 2003 standard edition ?

You stated that :

the sp1 redistributable for .net 1.1 has a different
redistributable file for server 2003.

Where can that "special" SP1 edition be downloaded ?

Since you had, also, stated that :

i am operating on facts and first-hand experience.

Could you tell us where you got that "first-hand experience" from ?
Where did you download the "special" SP1 for Windows 2003 Standard Edition ?

 

[Juan T. Llibre]

re:

try using that servicepack you posted on server 2003 (not itanium or x64), it will tell
you it can't install

Really ? I wonder how I managed to do just that.

re:

Juan please put your theories to the test...

I'm glad to... check it out : http://asp.net.do/test/version3.aspx

 

[EP]

ok, i'll try this one last time... I posted the link twice.... in fact it's
even in your quoted reply!!!! You have reposted the title and link numerous
times in the quoted sections.....

Microsoft .NET Framework 1.1 Service Pack 1 for Windows Server 2003
http://www.microsoft.com/downloads/...F7-2CB7-4864-8623-A1038563DF23&displaylang=en

If you look on that page...
Supported Operating Systems: Windows Server 2003

 

[EP]

Juan please put your theories to the test...

I'm glad to... check it out : http://asp.net.do/test/version3.aspx

As we've been discussing framework 1.1 sp1, i'm surprised you posted an example
of the 2.0 framework working without IIS.

Ok, that page showed that you were running .net 2.0. The windows component
option (under add/remove programs) for asp.net installs and uninstalls asp.net
v1.1.4322. Uninstall that component and look at what happens to the following
registry key.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET

you will see that the registry entry for v1.1.4322 is deleted, so uninstalling
IIS, which requires unchecking the asp.net component as well, removes asp.net
1.1.4322. The 2.0 framework does not have this tie into the server 2003
add/remove programs component.

 

[EP]

if you really don't believe me or the download page about the sp1 version
for windows 2003, look at Aaron Stebner's blog (he's on the windows MCE team
at microsoft)... I hope you will accept the download page and his information...



http://blogs.msdn.com/astebner/archive/2004/11/17/259314.aspx

There are separate versions of SP1 - one for Windows Server 2003 and another
one for other Windows versions. The Windows Server 2003 version is available
in 18 languages, the other version is available in 22 languages. Do these
SP languages only apply to the setup UI or also to the framework bits (language
DLLs)?



There are a couple of really good points here that I forgot to address in
yesterday's post.



The first point is how the version of the .NET Framework 1.1 that is included
as part of the Windows Server 2003 OS compares and contrasts to the redistributable
version installed by dotnetfx.exe. Key points here are the following:



· The .NET Framework 1.1 is installed by the OS optional component
manager technology (OCM) using an INF file and sysocmgr.exe when installing
or upgrading to Windows Server 2003.

· The English language version of Windows Server 2003 contains the
equivalent of the bits installed by the v1.1 dotnetfx.exe.

· The non-English versions of Windows Server 2003 contain the equivalent
of the bits installed by the v1.1 dotnetfx.exe and the bits installed by
the matching language of the v1.1 langpack.exe.

· If you try to install the v1.1 dotnetfx.exe on Windows Server 2003,
it will block you from doing so with a message saying that it is already
part of the OS.

· If you try to install the matching language of the v1.1 langpack.exe
on a non-English Windows Server 2003, it will block you from doing so with
a message saying that it is already part of the OS.

· If you try to install a non-matching language of the v1.1 langpack.exe
on Windows Server 2003 it will install like on any other OS.



The second point is how the .NET Framework 1.1 service packs are packaged
and delivered. Because the version delivered by dotnetfx.exe is MSI-based
and the version delivered by Windows Server 2003 is OCM-based, there are
2 separate service packs - one targeting each installation technology. If
you use Windows Update to install .NET Framework 1.1 SP1, you should only
be offered one of the packages though, because Windows Update will examine
the OS you are running on and offer you only the package that applies to it.



Also, the .NET Framework 1.1 shipped in 22 languages, but Windows Server
2003 only shipped in 18 languages. That is why you see a discrepancy in
the number of languages offered for each service pack. The bits that are
patched by the two different sets of 1.1 service packs is identical.

 

[EP]

So Juan it's been fun, but I must leave this alone now. I wish you the best
of luck on your FAQ site, I'm sure your readers are getting very accurate
information.