Bug?

[SWSDEV]

My component build fine, but after deploying it IIS6 had a problem compiling it.

Attached is a screen shot of the config for the given database component

Event code: 3007
Event message: A compilation error has occurred.
Event time: 9/19/2009 11:10:42 PM
Event time (UTC): 9/20/2009 5:10:42 AM
Event ID: e2562709944f493b8b5c7235f95bb290
Event sequence: 199
Event occurrence: 2
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/2/ROOT-2-128978968599375000
Trust level: Full
Application Virtual Path: /
Application Path: C:\Documents and Settings\All Users.WINDOWS\Application Data\3CX\Data\Http\Interface\ivr\
Machine name: TFS2

Process information:
Process ID: 4928
Process name: w3wp.exe
Account name: NT AUTHORITY\SYSTEM

Exception information:
Exception type: HttpCompileException
Exception message: c:\Documents and Settings\All Users.WINDOWS\Application Data\3CX\Data\Http\Interface\ivr\CellsAgent_Debug_52\Main_MF_databaseAccessComponent1_DoIt.aspx(134): error CS1010: Newline in constant

Request information:
Request URL: http://localhost:5484/CellsAgent_Debug_52/Main_MF_databaseAccessComponent1_DoIt.aspx?dataSource=&database=cellsagent.com&parameterCount=1&parameter_0=100650&password=8Trh76&server=TFS2e2562709944f493b8b5c7235f95bb290CSQLEXPRESS&userName=cellsagent.com
Request path: /CellsAgent_Debug_52/Main_MF_databaseAccessComponent1_DoIt.aspx
User host address: 127.0.0.1
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\SYSTEM

Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\SYSTEM
Is impersonating: False
Stack trace: at System.Web.Compilation.BuildManager.PostProcessFoundBuildResult(BuildResult result, Boolean keyFromVPP, VirtualPath virtualPath)
at System.Web.Compilation.BuildManager.GetBuildResultFromCacheInternal(String cacheKey, Boolean keyFromVPP, VirtualPath virtualPath, Int64 hashCode)
at System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath)
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

[VAD_Support]

Hi, this is probably a bug, can you provide us the file Main_MF_databaseAccessComponent1_DoIt.aspx where it is reporting it? Please, remove from it any sensitive information... Or just post here the line 134 (the one with the error).

 

[SWSDEV]

This problem happened when I put the explicit value for the parameter instead of a callflow variable.

Here's the line from the code. Looks like the problem is that it broke up the code into two lines for some reason.

string sqlStatement = String.Format("select PHONE from PROPERTYLISTINGS
where PROPERTYCODESID = {0}", args);

 

[VAD_Support]

OK, we'll check this.
Maybe you entered a ENTER character in the SQL statement text. Can you remove that new line from there and see if the error goes away?

 

[SWSDEV]

Yes, it was the carriage return (ENTER character).

It seems to me that should be made valid to put as SQL syntax.

 

[VAD_Support]

Absolutely, this is a bug that we'll fix in the next release.
Thanks for noticing about this.