" the object 'reporsitoryItemBreadCrumbEdit1' returned null for the property 'History' but this is not allowed. "
I used devex in form. I ran the program and it gave me this error. How can I fix?
Related
I am trying to push some data into CRM utilizing the logic app and the parameter fields.
Some of the fields get pushed through, while others do not. I am trying to understand what is the logic behind this?
All of the fields go through except the LeadPM field. I get this error:
"message": "Syntax error: character '"' is not valid at position 1 in '("Yu li")'."
This is what I have done so far:
When I got this error, I added "" and this did not work, so then I added '' and this did not work either. I finally did not add any quotes and am still getting this error. Any insight on this would be greatly appreciated.
JSON PARSE
It seems the value of your FeaturePM is " and it can't be stored in Lead PM directly. You need to add a \ to escape it. Change the value of FeaturePM to \" and then put it into Lead PM.
This is not the same as the other question because the advice in the other question fails to work for me. I'm specifically trying to determine what's different in my case that this doesn't work.
I'm working in Classic ASP. According to the docs I find online (here and elsewhere: https://www.w3schools.com/ASp/asp_ref_error.asp ), the ASP error object should have the following properties, among others:
Description: Returns a short description of the error
File: Returns the name of the ASP file that generated the error
Line: Returns the line number where the error was detected
Number: Returns the standard COM error code for the error
I have the following test code. Note error_log() is a custom function that writes text to a log file.
on error resume next
blah
if err.number > 0 then
error_log( err.number )
error_log( err.description )
error_log( err.file )
error_log( err.line )
end if
on error goto 0
The first two lines, number and description, are written as expected; but file and line are not. As best I can tell, the latter two properties are simply not available to my copy of ASP/VBScript. Why don't I have these properties?
I'm running what I believe is the latest (circa 2000) version of classic ASP VBScript. Straight from the horse's mouth: VBScript 5.8 build 16384
EDIT: attempts to run Server.GetLastError() fail. It appears I don't have that command for some reason. [CORRECTION: it runs but seems to have no data. See examples below]
New Minimal Example:
On Error Resume Next
blah 'This is our error. unrecognized variable'
Set error = Server.GetLastError()
response.write error.file
On Error Goto 0
response.end
This results in a blank screen. No error data is written.
Another test. Note "error" vs. auto-generated "err":
On Error Resume Next
blah 'This is our error. unrecognized variable'
Set error = Server.GetLastError()
response.write error.number
response.write " | "
response.write err.number
response.write "<br>" & vbCrLf
response.write error.description
response.write " | "
response.write err.description
response.write "<br>" & vbCrLf
response.write error.file
response.write " | "
response.write error.line
On Error Goto 0
response.end
Result:
0 | 500
| Variable is undefined
| 0
For starters, per user Lankymart, there is a difference between the automatic err object and the object returned by Server.GetLastError(). For this we need the latter of the two.
It seems that Classic ASP returns a slightly different error code: 500.100; so if you want to capture error data, you have to make an error page explicitly for that sub-code.
Info found here: https://stackoverflow.com/a/9407559/339440
Classic ASP has always returned a 500.100 status if there is a script
error[...].
If you want to catch Classic ASP script errors and be able to read the
Server.GetLastError() object in your custom error page (say for
logging) you need to provide a handler specifically for 500.100.
If you don't specify a custom 500.100 error then IIS will fall back to
your custom (or its own) 500 error page but Server.GetLastError()
won't provide any useful information about the error.
So error referencing "in place" doesn't work, and catching the standard 500 error doesn't work. You need to explicitly catch the 500.100 code. On a regular 500 error, Server.GetLastError() returns an object with no data in it -- which is exactly the problem I've been having.
So I made a copy of my site's 500 error page, and modified it to also write to my error log. Then in IIS I set that new file to be the error page for 500.100 errors. It appears to be working.
This doesn't entirely solve my problem, as I was trying to create a sort of try ... catch routine that could run inline. But it does give me the ability to simply log errors, which is very useful.
In my Flex 4 application I have a spark text input. When the user pastes data from clipBoard it throws error if the clipBoard contains a different format (other than string). This is the error message i am getting.
"TypeError: Error #1009: Cannot access a property or method of a null object reference.
at spark.components::RichEditableText/handlePasteOperation()
[E:\dev\4.0.0\frameworks\projects\spark\src\spark\components\RichEditableText.as:3611]"
Is there any way to handle this?
Thanks
Manoj
It looks like this is a known problem. The only suggestion I could find was from rdermer on one of those threads:
If you have a local copy of TLF 1.1
you can work around it by adding a
test at line 346 of TextClipboard.as.
Replace
endArray.push(curFlElement); with
if (curFlElement)
endArray.push(curFlElement); That prevents the bug - but the
underlying cause needs more
investigation.
I've begun using ASPUnit to unit test my classic ASP code. This is all good and I'm happy. The only problem is with the error messages it displays when a test generates a runtime error. For example, if I've not defined a variable somewhere in my function I get the error:
Microsoft VBScript runtime error (500): Variable is undefined
What would be more useful is if it could tell me which file/line the error occurred on. I know that I can get this information from the ASPError object which is returned by the Server.GetLastError() and elsewhere in my project I have a custom 500 error page which makes use of this method to automatically report crashes to Fogbugz. However when I try to access Server.GetLastError anywhere else the information returned is blank. For example, the following code will output zero rather than the expected 4.
<%
Option Explicit
On Error Resume Next
aVariable = "hello"
Dim errObj : Set errObj = Server.GetLastError()
Response.Write errObj.Line
%>
Is this the correct way to access ASPError or is it only possible on custom error pages? Is there a better way to get error messages reported within ASPUnit?
To the best of my knowledge the ASPError object does not get populated until your current page finished processing. Its meant to only be used on the 500 error page only. So theory is when you get an error if you've set up your 500 page then IIS will do an internal redirect to that page to allow you to at least record the error. Then and only then is the ASPError object available. I've had crazy ideas of using a xmlhttprequest to try to grab the page but thats just not the way it works.
In short there is not much you can do to get that error message details that you want.
Using JScript server side you can use try catch's which give you access to a exception object but even thats not much good to you, no line numbers or anything. Rubbish.
I am doing .net application which is in vb.I am getting an runtime error when running in Internet Explorer,but its running in mozilla. Error as following
Error:SysArgumentTypeException:Object
of type
'AjaxControlToolKit.Animation.Length
Animation' cannot be converted to type
;AjaxControlToolKit.Animation'.Parameter
Instance.
Error is getting in MicrosoftAjax.debug.js
if(!this.isInstanceOfType(instance)) throw Error.argumentType('instance',ObjectgetType(instance))
What may be the reason for this error.What can i do to resolve this? Can anybody help?
The error indicates, that you are trying to cast a type called Length Animation to a type called Parameter. In VB and VB.NET, the cast is tried implicitly if the types of an assignment doesn't match. Please have a further look at the stack-trace to find the exact line of the error.
PS: I didn't know that there could be spaces in a .NET type name...