Microsoft Chart Controls on shared hosting with .net framework 4.0 installed. "The resource cannot be found."
Locally it works just fine. I confirmed that the dlls are on the server.
I have tried changing all settings in the web.config and ImageLocation parameters. No luck.
Any suggestions?
To troubleshoot the issue first make sure that the chart assemblies are installed in the GAC.
Then try to hit the server with server/yoursite/chartimg.axd?i=0.png&g=0 from the browser (use these exact parameters). If you get "The resource cannot be found" then the handler is not installed properly: look for the issue in your web.config and try again until you get "System.ArgumentException: The image is not found". This means the handler is installed properly and works as expected.
Then render the page which contains a chart control where Chart.ImageStorageMode = UseHttpHandler. If you get an exception please post the exception stack here as well as your major controls layout like: "the chart is placed in update panel, which is placed in a user control, which is placed in update panel in the page".
Related
I have read other posts with people having issues with the 404 Not Found error when building their own local version of NuGet.Server. None of them specifically asked about what I am seeing as an issue.
I followed the instructions at https://learn.microsoft.com/en-us/nuget/hosting-packages/nuget-server and get the Default page just like it said. The only changes I made to the web.config were to set the requireApiKey=false since this will be a local server.
When I click on the "Click Here to View Packages", and get the 404 Not Found error, I noticed something on the page. It looks like it is trying to resolve to the same URL that is shown as the link for the Package Manager (https://localhost:44375/nuget), but then adds "Packages". Which might seem okay until you look at the "Physical Path" that is listed. It has a physical folder called "nuget" which is not there and was never created in the instructions or during the install of the NuGet.Server package.
Here is a screenshot of the 404 page.
There was nothing in the documentation about adding that folder, and it was not added when NuGet.Server was installed. Is this a configuration issue that I cannot seem to find, a setup step missed in the instructions or a bug in the NuGet.server ?
I'm currently running TYPO3 version 8.7.18 and running a site_package that was made by using the site package builder: link
Whenever I try to add a form by using the default backend forms module I get the default message Oops, an error occurred! along with that the following error
TYPO3\CMS\Form\Domain\Configuration\FormDefinition\Converters\AddHmacDataConverter not found
Searching for the issue I get several hits on the Gitlab but these do not provide any solution.
Along with this setup, I've added the forms module as a static include in my top-level template.
do you have a composer installation or an extension manager build up?
If a class is not found you may need to rebuild the autoloader information.
My error turned out to be caused by a corrupt installation. I've had to upload the file AddHmacDataConverter.php in the following path /public_html/typo3/sysext/form/Classes/Domain/Configuration/FormDefinition/Converters. A very weird error indeed.
For those that came here with the same error, make sure to check that folder. Apart from that add the news as a static inclusion in your top domain. You could also follow #Bernd Wilke's idea which s to disable the extension, clear all system caches (and additionally remove typo3/temp/autoload and then active the extension again.
I have a label in my project
When I queue a build, and put the label in the "Source Version" field, prefixed with a L, it always comes up the following error:
500: TF14064: Could not find label mylabel#$/.
Anyone been able to get this functionality to work?
Most likely the problem is that your label is not collection-scoped and therefore you need to provide a scope with your label. If you created your label in Visual Studio, the scope is probably project-scoped. So for example if your label is 'mylabel' and your project name is 'myproject' then in the Source Version field you should enter this:
Lmylabel#$/myproject
Here are a couple links that help explain labels and scopes if you are interested.
https://msdn.microsoft.com/en-us/library/9ew32kd1(v=vs.100).aspx
http://teamfoundation.blogspot.com/2008/03/label-scope-revealed.html
I'll update the Microsoft Connect Page with this information too.
I can reproduce this issue and have help you submit a feedback on Microsoft Connect Page, you can track the status here: https://connect.microsoft.com/VisualStudio/feedback/details/2345698/500-tf14064-could-not-find-label-error-occurs-when-queue-a-build-with-specified-label
I was facing the same issue for TFS build and the error says like: “Cannot find the current label tfs build”.
How to resolve the issue:
Go to Configuration of your TFS build
Make the Label sources as true
Build the solution now and it's building fine.
Please reach out if any issues.
I am new to Click Once Application deployment so I think I may have a simple problem. I have a window app that I created and deployed successfully as a ClickOnce App using Vis. Studio 2010 and deploying to a web service. I made some changes to the app and changed the deployment location so I started the click Once Process over. Now when I deploy I get an error. The app builds fine, runs fine in VS 2010, when I deploy files are created. Double clicking the App.application file will start the install of the app with a .Net framework error.
"Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.
System.UriFormatException: Invalid URI: The URI is empty..."
I have double checked and triple checked the Publish Foldre Location and INstallation Folder URL to make sure they are pointing in the correct places and using the correct format. I double and triple checked the Updates dialog box when you click the Updates button. The combobox for the Application Updates matches the Installation Folder URL. "\MyServer\Users\Administrator\Desktop\Transfer\Deploy\" I double checked to make sure the required files are correct. Security settings did not change.
What could I be missing?
It seems you missed one backslash in your installation folder URL:
\\MyServer\Users\Administrator\Desktop\Transfer\Deploy\
Please make sure that if you are using some image/sound or log files then its Build Action must be "Content" type.
When using a local NuGet server, whenever I try to install an individual package from that server, all I get is this error: "The remote server returned an error: (404) Not Found."
The packages are all there in the filesystem and the feed itself sees all the packages appropriately. I can even browse the package directly!
What am I missing?
I did just upgrade from NuGet server 1.4 to 1.5, but I've seen this happen before. Touching the package files used to help, but that does not appear to be the case now.
EDIT: Actually, I hadn't seen that exact error before...I've seen this one, intermittently, that touching the package tended to fix.
On Windows Server 2008, I was having the same issue. I switched the Application Pool from "ASP.NET v4.0 Classic" to "ASP.NET v4.0". The install-package command worked fine after the change.
sigh...
http://blogs.thesitedoctor.co.uk/tim/2011/09/02/Nuget+Server+On+IIS6+Returns+404+When+Downloading+Package+After+Upgrade.aspx
EDIT: In case the link ever dies...I am hosting my NuGet server in IIS6, which wasn't set up to properly handle extensionless URLs. And since the semantics of downloading individual packages changed from a direct file link to an extensionless route, I started getting 404s. Adding the wildcard mapping described in the article fixed it instantly.
I've been trying to figure this for a couple of hours...
Checked the IIS logs and discovered that URLScan was blocking the route:
GET /Rejected-By-UrlScan ~/api/v2/package/
URLScan doesn't accept any route not starting with '/'. The best I could do was to remove the URLScan from the list of ISAPI filters for the website in the IIS Manager.
I was having the same issue on Windows Server 2008.
Problem was in my own package MyPackage.nupkg that I saved without version.
MyPackage was visible in PackageManager but it was getting 404 error on install.
Fix:
I saved it with name MyPackage.1.0.0.nupkg (1.0.0 is current version) and problem was fixed.
I had the same problem, srv 2008 R2. Changed the application pool to Integrated from Classic and all works fine now.
My problem was same as image above. I could go to the site on url
http://localhost:3407/nuget/Packages
but not
http://localhost:3407/api/v2/package/{package name}/1.0.0.0
I encountered this error while trying to download Signal-R after update Nuget, however it was just that I had not checked the "Allow Nuget to download missing packages during build" option in package manager settings. Once that was that set it all worked fine again.
It could be this as well -
You are trying to refer to a url like : http://yourdomain/application/nuget/packages
Then you should change it to :
http://yourdomain/application/nuget
This is a common mistake.