J'ai obtenu cette erreur d'un de mes services de Web d'ASP.NET quand j'ai essayé de chercher quelques données d'une base de données à distance. J'ai essayé de rechercher en ligne une difficulté possible à cette question mais n'en ai trouvé aucun convaincre et ai ainsi pensé à éditer la solution qui a résolu la question.

Veuillez noter que cette solution peut seulement être efficace si vous corrigez votre service de page/Web d'ASP.NET et attachez manuellement le processus d'ouvrier.

1. Attache au processus d'ouvrier.

2. L'aspnet_wp.exe étant accentué le coup « choisissent… » bouton sur le côté droit supérieur.

Vous obtiendrez « le type choisi de code » dialogue avec « déterminez automatiquement le type de code pour corriger » choisi. Maintenant pour qu'ASP.NET emploie « a contrôlé » le type de code en vérifiant le checkbox « contrôlé ».

Essayez-le encore et il devrait fonctionner sans « EXÉCUTENT la permission niée' sp_sdidebug' sur objet, maître de `de base de données', dbo de `de propriétaire'. » erreur.

Espoir qu'il aide. Faites-moi savoir de toutes les questions ou solutions alternatives dans les commentaires.

Designers with the ability to code and developers with a dash of design skills — the rise of a third, more flexible role is at hand that cannot be pigeonholed solely as a developer or designer.

Read further.

Chris Sells, one of my favorite Microsoftie, puts out 6 bulleted list of unpublished tips on getting interviewed at Microsoft. Here are those at a glimpse,

• Your interviewer cares most about 1) how you think and 2) what you feel, so be vocal about both.
• Don’t be afraid to ask clarifying questions.
• Let the interviewer know how you feel about the job.
• Answer questions from your own experiences.
• You have to like us, too.
• Don’t talk about money during the interview.

You can read the details of these bullet points from here. You can also read his “Published Microsoft Interviewing Tips” from here.

tags: Microsoft, Interview, Interview Tips, Tips, Tips and Tricks, Chris Sells

This killed me for a while. I had an ASPX (Master) page that includes some headers and footers from legacy ASP pages (reusability, maintainability). Those ASP pages were so badly designed to embed multiple forms and each forms within that does HTTP POST. So messy that I even thought of rewriting those whole headers and footers but I can’t since that will leave us with 2 sets to maintain.

When I started using the headers and footers in the ContentPlaceholder in my Master Pages it kept complaining about this error,

Invalid postback or callback argument. Event validation is enabled using <pages enableEventValidation=”true”/> in configuration or <%@ Page EnableEventValidation=”true” %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.

After looking around for help there was nothing that lead me to a solution. Accidentally I found out by myself that it was because of the embedded <form>s that it complained. After working around with those forms to make sure that only one <form> get rendered on the