I have a site that I have developed in asp.net. On debugging the site now hosted using IIS7 I noticed a bug, I cannot reproduce this when I run it locally in vs, meaning I can't see the error. The bug occurs on the check box changed event of a devexpress check box. It connects to the database using devart.postgres sql component and linq. However, this is the same connection as anywhere else in the project. The same code works elsewhere in the project. The error I get is:
the requested name is valid, but no data of the requested type was found.
Part of my code is in an if statement that checks if a textbox is blank if so it does not run the code within the if statement, interestingly enough if the text box is blank the code runs, so it must be in the if statement? I commented out all of the code and tried again and it still would not run. Beginning to lost objectivity with this problem, hope you can help.
The error you have posted suggests that there is a problem resolving an address. For example, when you check that checkbox, something in your code tries to resolve a valid address, but the DNS server doesn't recognise it. Are you doing anything that would involve name resolution?
Can you share the code that causes this error?
Related
Here is the scenario:
I have a customer that needed a slight modification to a customized package my company did. So I:
Made a backup of the customer's data from the SQL database.
Setup a new installation of Acumatica using the same revision (Build 21.211.0033)
Restored SQL database to the new Acumatica Site
Ran simple tests, and I get strange errors.
When I try to navigate to a Service Order from screen: FS3001PL, I get the following error:
Here's the thing: Those fields do not exist on InventoryItem on the customer's site database where everything is running fine and I am not getting this error.
When I look at the source code of our customization, those fields ARE defined in the DAC extension. But they are never used (as far as I can tell) I tried commenting the fields out, same error. Put the fields back in, Same Error.
The wicked thing about the error, is that it does not throw anything that is catchable in the Visual Studio debugger. I am able to attach to the IIS process, and if I add an event to something like CacheAttached, my breakpoint is hit -- so I know I am in the right source for the DLL, this error does not get caught, even though I have the debugger set to break on any error. So I can't even see what the system is seeing that I am not.
Again This runs fine on the customer's site.
I don't even know how to debug this at this point.
Any ideas would be appreciated!
The issue is that they are in the DAC but not the SQL database. Used or not, once defined as a PXDB type field in the DAC, the cache tries to sync the SQL tables for all PXDB fields of the DAC with the database. Hence, your error. You need to either add them back to the SQL table or remove them from the DAC extension.
Check case on the field names and that it is in the right table. There is something misaligned between your SQL and your DAC.
In my web app I have a lot of gridviews and so on. Now I was trying to change some data format in the gridview, and the changes did not take effect when i debugged, either in Chrome nor Internet Explorer, it kept showing the same gridview as before. I tried to change the SQL data I was providing to it, and it actually changed, so the problem is when I'm altering in my web project.
Wondering what this could be, I did another test by removing the function that triggered when a button is pressed. When I debugged not only I did not get the error that usually comes with not assigning anything to a OnButtonClick but also when I pressed the button it did what it was doing before i removed the function.
Did this already happen to any of you?
Edit1. Now I tried to create an empty webform and when I debugged I get this error:
Error of analyzer
Description: Error parsing a resource required to make this request. See the
specific analysis error details below and modify your source file appropriately .
Are you hosting in IIS or debugging with Visual Studio's inbuilt server?
Try cleaning and rebuilding your code, then clearing your browser cache
Try deleting cache and cookies from (both of) your browsers.
Sometimes this gives problems when you are debugging because you will keep seeing previous parts of your current app.
Hi I am getting the error
"Sys.WebForms.PageRequestManagerServerErrorException: Input string was not in a correct format."
When pressing a delete button. But this error comes only in one web server. In other server it works fine. Again when locally running the application, there is no error but it will not firing the delete action. Any Idea??
Found elsewhere the suggestion to use an Image inside a Linkbutton.
Works well. ImageButtons inside Gridviews especially within update panels were always a pain.
http://forums.asp.net/t/1823287.aspx/2/10
Re: ImageButtons not working in IE10
Dec 05, 2012 04:38 PM|LINK
I couldn't get any of the above example to work for me, but I have an Image Button in a repeater within an update panel. Anyway, I just replaced the Image Button with a Link Button wrapping an Image and everything is working again.
Yes... This issue was solved by updating the .net framework to 4.5. The issue was with the framework with IE 10. Please check your server .net framework and Your local PC as well.
Just simply update the framework. I couldn't find any other solutions rather than this. :)
if the delete image button and you don't need to install the .Net framework 4.5. All the time we are not able to change the framework versions. If we have window server 2003 r2 then we can't install the .Net framework 4.5. So in this case we can change the Image button to Link button. Here is the same source for link button to show as like image button in the asp.net
<asp:LinkButton ID="deleterow" runat="server"
CommandArgument='<%#DataBinder.Eval(Container.DataItem,"Id")+","+DataBinder.Eval(Container.DataItem,"Facultykey") %>'
OnCommand="DeleteFaculty"
Visible='<%# EnableControls(DataBinder.Eval(Container.DataItem , "IsFacultyConfirmed"),2,DataBinder.Eval(Container.DataItem , "AFTId"),DataBinder.Eval(Container.DataItem , "FacultyKey"))%>' >
<asp:Image ID="Delete"
ImageUrl="../App_Themes/Blue/images/buttons/delete.gif"
runat="server"/></asp:LinkButton>
Since i personally suffer having windows server 2003 R2 and unable to install the .Net framework 4.5 and it will helps to solve the issue without touching the server config.
Hope this helps
i know this is old question, but for people who will come here in future and read this, I will describe how I solved it.
My application was working for several years without problems and suddenly clients started to notice 'forewer waiting', page not refreshing because of above mentioned error (Uncaught Sys.WebForms.PageRequestManagerServerErrorException: Input string was not in a correct format.)
I had hard time to discover what was main problem because there was no error while debugging .cs code. After searching a lot I discovered that someone proposed to disable PartialRendering...
(you can do it in .cs by ScriptManager1.EnablePartialRendering = false;
or in page by adding EnablePartialRendering="false")
So I disabled it, and voila... finally while debugging, error appeared in one function, and executiuon stopped like before but with more description. Cool, now I know where is enemy :-)
It is interesting that it wasn't hit at all while EnablePartialRendering is true.
Now execution wasn't stopped in Code Behind too, but finally some more text in browser window, this is what I got:
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.FormatException: Input string was not in a correct format.
Source Error:
Line 1209: Array.ConvertAll<DataRow, double>(
Line 1210: dt.Select(),
Line 1211: delegate (DataRow row) { return Convert.ToDouble(row[columnName].ToString()); }
Line 1212: );
Line 1213: return GetMedianFromArray(values);
Problem was in Line: 1211
Can someone see the code-behind of an .aspx website from a browser?
I have been told it is possible but i cant really find a way of doing it , viewing the page source only shows the presentation page..
So is there a way of doing it ? and how?
thank you
No, it is not possible to see the codebehind without physical or remote access to the server itself.
You could also in theory misconfigure the IIS server to display the source files, and that would cause them to be displayed, rather than compiled, but no idea why anyone would do that. IIS by default will not display them.
By default, IIS shows parts of your code (aspx or code-behind) when an exception occurs - along with the call stack of the exception. Any serious ASP.NET application hides this information from users by using specific error handlers to show the error information in another (often more user-friendly) format.
As others mentioned, it's not normally possible to see the code, as it's a server-side handler, compiled and run on the server, while client only sees the HTML output.
whenever i Response.Redirect("myexamplepage.aspx"); it either keep looping and then lastly show the page is unable to view or show this above error. However, if i Response.Redirect("http://www.google.com.sg"); it works.
I tried all the methods i found online such as the following:
Response.Redirect(url,false)
Redirecting url outside the try-catch
I'd also make sure that my project is running debug mode.
BUT i am still facing this problem. It is like so random because previously i dont have any problems redirecting to my url. Please provide me with solutions thanks.
This error occures most of the time when you are trying to redirect to a new page, while the current page is still trying to complete it's proces.
You can find more information about the issue right here:
http://support.microsoft.com/kb/312629/EN-US/
So change your code to the following:
HttpContext.Current.ApplicationInstance.CompleteRequest();
Response.Redirect ("myexamplepage.aspx", false);
As Rob Angelier said, the problem is related to an uncompleted process.
That means, make sure you move the Response.Redirect out of the using statement!
This may not be an actual answer to the specific question but I thought it would help others struggling with the same type of problem :)