Hi am getting a lot of errors in the coldfusion exception log from bots trying to access files that no longer exists. Below an example:
"Error","ajp-nio-****","12/08/21","11:21:21","****","File not found: **** The specific sequence of files included or processed is: ****'' "
coldfusion.runtime.TemplateNotFoundException: File not found: ***
Is there a way to prevent coldfusion from logging TemplateNotFoundException's in it's exceptions logs?
Related
I am trying to add a data source in ColdFusion Administrator. After I fill out fields and click "Submit" I get this error:
Connection verification failed for data source: <connection name>
java.sql.SQLException: General error
The root cause was that: java.sql.SQLException: General error
Here is screenshot for more clarity:
I am not sure what could be the problem. All data appears to be entered correctly.
I have 2 questions:
Anybody knows what could cause this error?
How can I farther debug this error message? Are there some logs I can look at with more details, like a stack trace or something?
The problem was outdated .jar driver file. My database administrator provided me with new, updated version of .jar driver file and that solved the problem.
Driver in question was InterSystems Caché JDBC driver. I am not sure what versions they were (filename was the same - just CacheDB.jar). However, my "bad" .jar was 704 KB, and my "good" .jar is 2,019 KB.
I am also not sure what version of hotfix I am on, but I doubt it's the latest one at the moment of writing this.
I am using Visual Studio 2017 Enterprise on Windows 10.
And I have got these errors when I tried to use PM console.
The following error occurred while loading the extended type data file:
Microsoft.PowerShell.Core, C:\Windows\SysWOW64\WindowsPowerShell\v1.0\typesv3.ps1xml: The file was skipped because of the following validation exception: File C:\Windows\SysWOW64\WindowsPowerShell\v1.0\typesv3.ps1xml cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170..
Errors occurred while loading the format data file: Microsoft.PowerShell.Diagnostics, , C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Event.Format.ps1xml: The file was skipped because of the following validation exception: File C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Event.Format.ps1xml cannot be loaded because its operation is blocked by software restriction policies, such as those created by using Group Policy..
Errors occurred while loading the format data file: Microsoft.PowerShell.Core, , C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Help.format.ps1xml: The file was skipped because of the following validation exception: File C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Help.format.ps1xml cannot be loaded because its operation is blocked by software restriction policies, such as those created by using Group Policy..
Errors occurred while loading the format data file: Microsoft.WSMan.Management, , C:\Windows\SysWOW64\WindowsPowerShell\v1.0\WSMan.format.ps1xml: The file was skipped because of the following validation exception: File C:\Windows\SysWOW64\WindowsPowerShell\v1.0\WSMan.format.ps1xml cannot be loaded because its operation is blocked by software restriction policies, such as those created by using Group Policy..
Errors occurred while loading the format data file:
Microsoft.PowerShell.Diagnostics, , C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Event.Format.ps1xml: The file was skipped because of the following validation exception: File C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Event.Format.ps1xml cannot be loaded because its operation is blocked by software restriction policies, such as those created by using Group Policy..
Microsoft.PowerShell.Core, , C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Help.format.ps1xml: The file was skipped because of the following validation exception: File C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Help.format.ps1xml cannot be loaded because its operation is blocked by software restriction policies, such as those created by using Group Policy..
Microsoft.WSMan.Management, , C:\Windows\SysWOW64\WindowsPowerShell\v1.0\WSMan.format.ps1xml: The file was skipped because of the following validation exception: File C:\Windows\SysWOW64\WindowsPowerShell\v1.0\WSMan.format.ps1xml cannot be loaded because its operation is blocked by software restriction policies, such as those created by using Group Policy..
I removed %AppData%/Local/Microsoft/Visual Studio folder.
And reboot laptop, reopened Visual Studio but the same errors occurred.
Can you please fix this?
There is a tool which uses fabricate makefile and saxon as XSLT processor to run and build xslt based project. The program is executed using a main python script which executes several files. I have an issue that the python script is stopping when an error is encountered (for example if there is a syntax error in xsl template file, the error comes on screen and execution is stopped). I want the file to execute even when there is an error and log the error into file. I know how to log error into file but i dont know how to continue the execution of program even when error is encountered. Please answer to this question with example because it will be difficult to understand only theory.
I have a project which contains one cpp file and included few header files. Sonar squid sensor complains about parser error in the file, and I am getting the parser error messages in the output log with INFO statements.
After this when I get the number of lines of code from Decorator context of sonar it is giving me 1 line.
How can i make sure to skip the parser error, i tried
sonar.cxx.errorRecoveryEnabled=true
But still the error is displayed in log and i am getting the total lines as 1.
When ever there is a parser error in the files i am getting the value NCLOC = 1.0
I'm trying to use Profile Guided Optimization (PGO) with VS8. After instrumenting the DLL in question I copy it over to a machine that has our application installed and run the training scenario. I then copy the pgc training files back to my dev box and get the following error:
1>StdAfx.obj : fatal error LNK1270: invalid file; timestamp does not match file linked with /LTCG:PGINSTRUMENT
The MSDN entry for this error says:
invalid file; timestamp does not match file linked with /LTCG:PGINSTRUMENT
The same files passed to the linker when specifying /LTCG:PGINSTRUMENT must also be passed when specifying /LTCG:PGOPTIMIZE.
/LTCG:PGOPTIMIZE requires that the inputs be identical to the /LTCG:PGINSTRUMENT phase.
To resolve this warning, run /LTCG:PGINSTRUMENT, redo all test runs, and run /LTCG:PGOPTIMIZE, or, create the optimized image with /LTCG:PGUPDATE instead of /LTCG:PGOPTIMIZE.
Rerunning the tests doesn't solve the problem (although it sometimes appears for other files, not stdafx.obj).
Using /LTCG:PGUPDATE does work however I would like to understand what is causing the error, or failing that are there any drawbacks to using PGUPDATE rather than PGOPTIMIZE (I can't find anything relevant in the MSDN PGO page).