Comments on: Value cannot be null.Parameter name:path1 http://itknowledgeexchange.techtarget.com/itanswers/value-cannot-be-nullparameter-namepath1/ Fri, 24 May 2013 17:13:17 +0000 hourly 1 By: 6969 http://itknowledgeexchange.techtarget.com/itanswers/value-cannot-be-nullparameter-namepath1/#comment-90394 6969 Fri, 01 Apr 2011 07:19:56 +0000 #comment-90394 value cannot be null parameter name path1 i m getting this error when i m printing report in visual studio 2008 with crystal report…i have reinstall the software

]]> By: carlosdl http://itknowledgeexchange.techtarget.com/itanswers/value-cannot-be-nullparameter-namepath1/#comment-76654 carlosdl Fri, 30 Apr 2010 14:31:48 +0000 #comment-76654 I read that this error could occur if the WINDIR environment variable is not set, or is incorrectly set on the machine. Could you check that ? (usually it should point to c:\windows\)

]]> By: meeta http://itknowledgeexchange.techtarget.com/itanswers/value-cannot-be-nullparameter-namepath1/#comment-76644 meeta Fri, 30 Apr 2010 05:26:39 +0000 #comment-76644 No. Other reports are also not working.
Same error for all reports.
I used dynamic crystal reports.

]]> By: carlosdl http://itknowledgeexchange.techtarget.com/itanswers/value-cannot-be-nullparameter-namepath1/#comment-76621 carlosdl Thu, 29 Apr 2010 17:57:34 +0000 #comment-76621 Are you able to run other reports on those machines ?

]]> By: meeta http://itknowledgeexchange.techtarget.com/itanswers/value-cannot-be-nullparameter-namepath1/#comment-76607 meeta Thu, 29 Apr 2010 09:10:10 +0000 #comment-76607 thnks for reply.

In project, I haven’t use ‘path1′ parameter .This problem occures on only some PC’s not on all PC’s. On development pc this problem doesn’t occures.

]]>