|
|
 Posted 03/11/2005 06:03:17 |
|
|
Forum Newbie
Group: Forum Members
Last Login: 29/06/2006 03:53:29
Posts: 5,
Visits: 10
|
|
| When installing on Windows 2000 Advanced Server I get the following screen when I go to the default.aspx <%@ Page language="vb" CodeBehind="default.aspx.vb" Inherits="InstantKB.InstantKB_UserDefault" %>
<% @Register tagprefix="InstantKB" Tagname="Application" src="controls/application.ascx" %>
<InstantKB:Application runat="server"/> The same directory copied to a Windows XP machine works fine. I have installed the .NET Framework and tried this on two Windows 2000 Advanced Servers with the same result.
|
|
|
|
| Posted 03/11/2005 15:23:10 |
|
|
Support Supremo
Group: Customers
Last Login: 13/11/2008 12:44:07
Posts: 568,
Visits: 2,507
|
|
steveh (11/3/2005)
When installing on Windows 2000 Advanced Server I get the following screen when I go to the default.aspx <%@ Page language="vb" CodeBehind="default.aspx.vb" Inherits="InstantKB.InstantKB_UserDefault" %>
<% @Register tagprefix="InstantKB" Tagname="Application" src="controls/application.ascx" %>
<InstantKB:Application runat="server"/> The same directory copied to a Windows XP machine works fine. I have installed the .NET Framework and tried this on two Windows 2000 Advanced Servers with the same result. Dear Steveh, I've already seen this type of problem when people install the IIS after the .NET Framework. I would suggest you to unistall the IIS and .NET Framework, install the IIS and then install the .NET Framework. If it's not the solution, please open a ticket in http://my.instantasp.co.uk so that we can investigate.
|
|
|
|
| Posted 04/11/2005 06:34:42 |
|
|
Forum Newbie
Group: Forum Members
Last Login: 29/06/2006 03:53:29
Posts: 5,
Visits: 10
|
|
| I only needed to reinstall the .NET Framework and it seems to have fixed the problem. However instead of installing .NET Framework 1.1, I have installed .NET Framework 1.0. Thanks for your help
|
|
|
|
| Posted 04/11/2005 07:21:03 |
|
|
Support Supremo
Group: Customers
Last Login: 13/11/2008 12:44:07
Posts: 568,
Visits: 2,507
|
|
steveh (11/4/2005)
I only needed to reinstall the .NET Framework and it seems to have fixed the problem. However instead of installing .NET Framework 1.1, I have installed .NET Framework 1.0. Thanks for your help I'm glad to hear you've solved the problem! Many thanks for your feedback!
|
|
|
|