I have checked the stack trace, this error can be related with
CreateControlTable.
We can also find the following information for CreateControlTable:
private static System.Web.UI.WebControls.Table
CreateControlTable(System.Data.DataTable datatable)
It seems that the error message is related with the controls on your web
application.
Paulo, according to the stack trace, it is really hard for me to find out
more information. Can you help to collect some additional information?
Thanks for your effort and time.
1. Please share the sample code which will cause the NullReferenceException
on your side. I will perform more research based on the code.
2. Please let me know the .NET Framework version you installed on the
machine, 1.0 or 1.1.
We can check this information in the Add or Remove Programs in the
Control Panel.
I look forward to hearing from you soon. Have a nice day!
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)Working on a Windows 2000 5.00.2195 SP2 and .NET Framework 1.
The application is working fine. I'm having trouble only with the trace
web.config
<?xml version="1.0" encoding="utf-8" ?><configuration><system.web><compilation defaultLanguage="c#" debug="true" /><customErrors mode="RemoteOnly" defaultRedirect="Erro.htm" /><authentication mode="None" /><authorization><allow users="*" /><!-- Allow all users --></authorization><trace enabled="true" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" /><sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes
cookieless="false" timeout="20" /><globalization requestEncoding="utf-8" responseEncoding="utf-8" /></system.web><appSettings><add key="ConnectionString" value="whatever" /></appSettings></configuration>
Hi Steve
I haven't been able to test your solution yet because the problem only shows up in the prodution DB
This problem shows up in the production server (Win2k Server 2000) and in the test server (Win3k). Not in my machine (WinXPpro)
The same thing happens if I add Trace="True" to the @. Page directive of WorkLog.asp
Shouldn't tracing be independent of the application
Paulo Morgad
Hi Paulo,
Yes, generally speaking "Trace" is seperate from application code. However,
some times trace will also report errors when there are some issues with
the configuration or code.
According to your last information, the error does not appear on the
Windows XP machine, I suggest that we perform the following steps to
further narrow down this issue besides running the sample application:
1. Create one empty web application on the production or test server.
2. Enable Trace to the "@.Page" directive.
3. Now, please check if there is any error message when running the web
application.
4. If everything is OK, add code like following to Page_Load:
Trace.Write("test");
5. Run the web application again and check if there is any error message.
If there is any new finding, feel free to let me know. Thanks!
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Hi Steve
I created another web application in the the test server (Win2k3) with another DB (no Northwind still)
I added the Trace="true" attribute to the @.Page directive and it throws the NullReferenceExcepetion
Without the Trace="true" attribute to the @.Page, the page works fine (the trace doesn't)
Regards
Paulo Morgado
Hi Paulo,
You means even a simple project will also suffer the problem on the win2k3
server ? If so, I suspect that whether the ASP.NET is correctdly installed
or is corrupted on the server machine. Would you please try reinstalling
the ASP.NET via the
"aspnet_regiis -i" in command in the vs.net commandline prompt?
For more detailed info on the aspnet_regiis tool, you may view the
following reference in MSDN:
#ASP.NET IIS Registration Tool (Aspnet_regiis.exe)
http://msdn.microsoft.com/library/e...netiisregistrat
iontoolaspnet_regiisexe.asp?frame=true
If you have any new findings, please feel free to post here. Thanks.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
Hi Steve
I ran aspnet_regiis -i on the test server (Win2k3) but, now, all requests to an .aspx page get the HTTP 404 error. All .htm are served rigth
I restarted IIS but, still the same
Paulo Morgado
Hi Paulo,
You mean after run the
aspnet_regiis -i in the commandline, all the aspx page on your machine
can't be requested(return 404 error)? If so, it doesn seems so strange.
Have you installed both .net framework1.0 and 1.1 on this machine? If so,
which version's regiis tool have you used?
the one under
F:\WINDOWS\Microsoft.NET\Framework\v1.0.3705
is for 1.0
and the one under
F:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
is for 1.1
I think you can directly go to the
F:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 folder and
run
aspnet_regiis -u to remove the asp.net and
then run
aspnet_regiis -i again to install and see whether it helps.
Also, since the 404 error is generally returned by IIS, I recommend that
you have a check in the IIS log to see whether it can provide any clues.
Thanks.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
Hi Steve
Got ASP.NET working. Aplication Server\Internet Information Services (IIS) MAnager\Web Service extensions\ASP.NET v1.1.4322 -> Allow
The System.NullReferenceException on trace details remains
Regard
Paulo Morgado
Hi Paulo,
If you select "clear current trace", and then add some information to the
trace log and thow the trace details again, Can this fixed the problem?
Luke
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
0 comments:
Post a Comment