You have requested an outdated version of PayPal. This error often results from the use of bookmarks.Solved it by commenting this line on my code (when setting up the paypal form in GWT):
paypalForm.setEncoding(FormPanel.ENCODING_MULTIPART);
You have requested an outdated version of PayPal. This error often results from the use of bookmarks.Solved it by commenting this line on my code (when setting up the paypal form in GWT):
paypalForm.setEncoding(FormPanel.ENCODING_MULTIPART);
"computer localhost does not exist on the network (...)"
"Cannot connect to WMI provider"WTF is this supposed to mean? I have no clue what a WMI provider is. Anyway - the only resort I was left was good old Google. So I started googlin' like crazy and I found some crazy SOAB of an MVP on a msdn forum thread who was trying to convince some indian guy to reinstall Windows and SQLServer.
C:\Program Files\Microsoft SQL Server\90\Shared>mofcomp "C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof"
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="CurrencyConverter.aspx.cs" Inherits="CurrencyConverter" %>
aspnet_regiis -i
Real World Case: I don't feel much of a butcher these days: I was working on a web app [ASP.NET 1.1, SQLServer2000] developed by someone else and i realized butchery is a fine art and I still got a long way to go.
My main task was to speed things up. It was taking 18 seconds to load a single page, with an average amount of data (nothing major). I first tried to put some indexes on the DB (1), which didn't have any, but not having at the time much experience on DB indexing I put my life in the hands of the Enterprise Manager Index Tuning Wizard (painful experience), knowing it would have butchered my DB, but hopefully just a bit, speeding up things for me in the end. It happened, but from 16-18 seconds the guilty page went down to 12-13, which was something but not what I was hoping. The wizard claimed a 28% speed increase: true, but not enough.
After this delusion, I went on inspecting the trace (enable it setting Trace="true" in the top page declaration, or @ app level from web.config) and I noticed KBytes of useless stuff being sent back and forth as ViewState (2). The app had a coulple of user controls dynamically generated every Page.Load, so I just disabled the ViewState for those (EnableviewState = "false") and the app speed dramatically increased (50% in my case). Good, but still it was taking 6-7 goddamn seconds to load. I also took off the SmartNavigation="true" page property: it might be the pre-AJAX coolest thing but it's deprecated and it saved me almost 2 seconds: down to 5.
I started looking at the code, spotting un-necessary open/close operations for connections that could've been shared, loads of butchery in there, of the finest quality, and I noticed ALL the stored procedures were being recompiled (3) because of a massive use of temporary tables and dynamic SQL, even when non necessary (if the stored procedure is being recompiled there's no gain speed, ergo no point in having it as stored procedure). I didn't really want to change the code, a work of art is a work of art, so I decided to roam a little bit more through the trace looking for hot-spots.
I noticed the page was laoding pretty fast looking at the trace latencies. I put some Trace.Warn("HereandThere") but there was nothing major, the whole page was taking only around 1 sec to process and render, but I was still seeing the content trhough the browser after 5 secs. Then again a look at the ViewState and controls sizes and it happened: I saw a 900KB dropdownlist (4). Turned out that drop down was being populated with more than 10.000 record (yes > 10^4) and the browser was obviously taking forever (around 3 secs) to load it. Took that out (set up a popup with only the dropdown for that selection) and EUREKA: loading time went down to 1-3 secs, which considering shitty server and crappy network is more than acceptable (compare it with 18 seconds if you don't agree).
As I said, there was (and there is) a lot more to change and optimize in this app, as per stored procedures code and code behind, but the art is art and I wanna keep this mess untidy as long as I can, to inspire me and to remind me what butchery truly means.
This extremely annoying thing happened to me twice on different systems, and I think is somehow related to the installation of earlier Ajax.NET VS2005 extensions that somehow is messing everything up (bloody butchers). If you're able to spot Viz template directories, your first temptation would certainly be to copy all that zipped stuff over from the installation folders to the other Document and Settings path: just don't do that, it will solve nothing and you'll eventually end up losing all your templates. This 'cause the templates installation process involves more than just copying the stuff over to another directory. I was able to fix it using methods 1/2 on a system, but not on the other. Notice that with method 3 you are detaching Project Templates from your user account, but if it doesn't bother you and you don't know how or you just don't wanna bother messing with windows accounts, then this is your way to go.
*Remember to do a good Rebuild All, otherwise it would keep going with the old headers.
Another gift from our MS butchers here. This problem seems to be related to some member of some struct in some header of the Platform SDK which doesn't match with the header shipped with VC++. Quoting from one of the forum buddies "the OPENFILENAME-struct is longer in the header-file of the SDK than in the header-files shipped with VC++. So a memset(&m_ofn, 0, sizeof(m_ofn)); overwrites some data which leads to a crash", or something like that.
This is a tricky one because actually it will take you some time to figure out that the Access Violation is related to the CFileDialog (you wouldn't think of that, why should the CFileDialog stop working like that?). Moreover, if you have the Platform SDK installed since a long time definitely you wouldn't connect the three elements: Platform SDK - CFileDialog - Access Violation. It could be a known issue (it is indeed), but if you google just Access Violation you will obviously get a helluva result set.
A bit of a pain in the ass I'd say.