Mike Dopp

I know, I know, Everyone and their dog has one of these (Blog posts about IIS SMTP Setup). So of course I couldn't leave my fifi (my dog (virtual of course(made up for the story))) out.

I have been messing around with email alerts from all my ASP.NET 2.0 Applications of course and of course I love the IIS server piece of Windows xp - 200x. One thing that has always beguiled (had to look up that word to make sure proper use) me is the SMTP server. Now all of you Windows Web Masters (System Administrators of the Web) are going to roll your eyes at me. That's  cool this post is mostly a reminder to me. 

When Setting up ASP.NET 2.0 Web Apps in SMTP Here is the configuration you want to put into your web.config.

Make sure the <network host="the IP address of the server not localhost or 127.0.01" />for whatever reason and I am sure there is a good one this does not work.

<system.net>
    <mailSettings>
      <smtp deliveryMethod="Network" from="esupport@yourcompany.com">
        <network host="your IP address"  port="25" userName=you@yourcompany.com/>
      </smtp>
    </mailSettings>
  </system.net>

SMTP Side Make sure you setup Relay to just the IP address of your server and you could add the localhost.

All will work and the world can now be spammed by another IIS Server.

So here is a question why would you want to add your Meta Tags via code? Kinda silly right? Cause if you were a great developer you probably have a whole list of meta tags you have created for your portfolio of web sites right?

Well if you are the developer who has those templates you most likely will stop reading here and think this mikedopp character is kinda wierd or is one of those "because you can" type people. I know I am adding much too much fluff to this whole entry and spending too much time with words so here is the code to add meta tags to your on load event of either your master pages or just to that web site that you need to get out the door tonight.

private void AddMetaTags()
    {
        if (this.Page != null)
        {
            base.Title = Server.HtmlEncode(this.Page.Title);
            base.AddMetaTag("keywords", Server.HtmlEncode(this.Page.Keywords));
            base.AddMetaTag("description", Server.HtmlEncode(this.Page.Description));
        }
    }

As an added bonus you could just create a large list of meta tags in your web.config file or another dot config file within your application or site that is just read into the site on_load.

There is also the possibility of having a large SQL/XML table that holds all your tags and is read in based upon the name of the page and content that is requested.

#Region ---This is where I go on a rant--- Feel free to get some popcorn and a diet mountain dew---

However since the only search provider that reads meta tags is MSN Live search and not google as I have been told (I still don't believe that).

There is no point to this post. So go ahead an move on to the next post on how to put all your keywords in a database and read them into the page content based on the same factors (for Google of course).

#EndRegion---End of rant

If you don't know by now you can reset your web applications and or web sites with a simple change to the web.config. For example you can FTP(if remote or hosted) to your server and edit the web.config by adding a space or removing a space. Basically you want the application your using editing with think something has changed since you touched the document. Save the form after this has happened and IIS will recycle the application / web site.

This however can be tedious and just well feel like a bit of hacking. So what I have come up with is not rocket science and you most likely do not want in a easy to access area on your web form.

I add this little snippet to a button event on the form. So when ever the site needs a cleansing for what ever reason I push the button of recycle.

public bool RecycleApplication()
   {
       bool Success = true;

       //Method #1
       //   It requires high security permissions, so it may not
       //   work in your environment
       try
       {
           HttpRuntime.UnloadAppDomain();
       }
       catch (Exception ex)
       {
           Success = false;
       }

       //if (!Success)
       //{
       //    //Method #2
       //    //   By 'touching' the Web.config file, the application
       //    //   is forced to recycle
       //    try
       //    {
       //        string WebConfigPath = HttpContext.Current.Request.PhysicalApplicationPath + "\\\\Web.config";
       //        IO.File.SetLastWriteTimeUtc(WebConfigPath, DateTime.UtcNow);
       //    }
       //    catch (Exception ex)
       //    {
       //        Success = false;
       //    }
       //}

       return Success;

   }
   protected void Button1_Click(object sender, EventArgs e)
   {
       RecycleApplication();
   }

Once again probably not a standards compliant and not an elegant way of recycling the application / web site. However it does the job.

This has been pooled together from a number of resources:

What is ASP.NET?

Microsoft ASP.NET is a server side technology that enables programmers to build dynamic Web sites, web applications, and XML Web services. It is a part of the .NET based environment and is built on the Common Language Runtime (CLR) . So programmers can write ASP.NET code using any .NET compatible language.

What are the differences between ASP.NET 1.1 and ASP.NET 2.0?

A comparison chart containing the differences between ASP.NET 1.1 and ASP.NET 2.0 can be found over here.

Which is the latest version of ASP.NET? What were the previous versions released?

The latest version of ASP.NET is 2.0. There have been 3 versions of ASP.NET released as of date. They are as follows :

ASP.NET 1.0 – Released on January 16, 2002.

ASP.NET 1.1 – Released on April 24, 2003.

ASP.NET 2.0 – Released on November 7, 2005.

Additionally, ASP.NET 3.5 is tentatively to be released by the end of the 2007.

Explain the Event Life cycle of ASP.NET 2.0?

The events occur in the following sequence. Its best to turn on tracing(<% @Page Trace=”true”%>) and track the flow of events :

PreInit – This event represents the entry point of the page life cycle. If you need to change the Master page or theme programmatically, then this would be the event to do so. Dynamic controls are created in this event.

Init – Each control in the control collection is initialized.

Init Complete* - Page is initialized and the process is completed.

PreLoad* - This event is called before the loading of the page is completed.

Load – This event is raised for the Page and then all child controls. The controls properties and view state can be accessed at this stage. This event indicates that the controls have been fully loaded.

LoadComplete* - This event signals indicates that the page has been loaded in the memory. It also marks the beginning of the rendering stage.

PreRender – If you need to make any final updates to the contents of the controls or the page, then use this event. It first fires for the page and then for all the controls.

PreRenderComplete* - Is called to explicitly state that the PreRender phase is completed.

SaveStateComplete* - In this event, the current state of the control is completely saved to the ViewState.

Unload – This event is typically used for closing files and database connections. At times, it is also used for logging some wrap-up tasks.

The events marked with * have been introduced in ASP.NET 2.0.

You have created an ASP.NET Application. How will you run it?

With ASP.NET 2.0, Visual Studio comes with an inbuilt ASP.NET Development Server to test your pages. It functions as a local Web server. The only limitation is that remote machines cannot access pages running on this local server. The second option is to deploy a Web application to a computer running IIS version 5 or 6 or 7.

Explain the AutoPostBack feature in ASP.NET?

AutoPostBack allows a control to automatically postback when an event is fired. For eg: If we have a Button control and want the event to be posted to the server for processing, we can set AutoPostBack = True on the button.

How do you disable AutoPostBack?

Hence the AutoPostBack can be disabled on an ASP.NET page by disabling AutoPostBack on all the controls of a page. AutoPostBack is caused by a control on the page.

What are the different code models available in ASP.NET 2.0?

There are 2 code models available in ASP.NET 2.0. One is the single-file page and the other one is the code behind page.

Which base class does the web form inherit from?

Page class in the System.Web.UI namespace.

Which are the new special folders that are introduced in ASP.NET 2.0?

There are seven new folders introduced in ASP.NET 2.0 :

\App_Browsers folder – Holds browser definitions(.brower) files which identify the browser and their capabilities.

\App_Code folder – Contains source code (.cs, .vb) files which are automatically compiled when placed in this folder. Additionally placing web service files generates a proxy class(out of .wsdl) and a typed dataset (out of .xsd).

\App_Data folder – Contains data store files like .mdf (Sql Express files), .mdb, XML files etc. This folder also stores the local db to maintain membership and role information.

\App_GlobalResources folder – Contains assembly resource files (.resx) which when placed in this folder are compiled automatically. In earlier versions, we were required to manually use the resgen.exe tool to compile resource files. These files can be accessed globally in the application.

\App_LocalResources folder – Contains assembly resource files (.resx) which can be used by a specific page or control.

\App_Themes folder – This folder contains .css and .skin files that define the appearance of web pages and controls.

\App_WebReferences folder – Replaces the previously used Web References folder. This folder contains the .disco, .wsdl, .xsd files that get generated when accessing remote web services.

Explain the ViewState in ASP.NET?

Http is a stateless protocol. Hence the state of controls is not saved between postbacks. Viewstate is the means of storing the state of server side controls between postbacks. The information is stored in HTML hidden fields. In other words, it is a snapshot of the contents of a page.

You can disable viewstate by a control by setting the EnableViewState property to false.

What does the EnableViewState property signify?

EnableViewState saves the state of an object in a page between postbacks. Objects are saved in a Base64 encoded string. If you do not need to store the page, turn it off as it adds to the page size.

There is an excellent article by Peter Bromberg to understand Viewstate in depth.

Explain the ASP.NET Page Directives?

Page directives configure the runtime environment that will execute the page. The complete list of directives is as follows:

@ Assembly - Links an assembly to the current page or user control declaratively.

@ Control - Defines control-specific attributes used by the ASP.NET page parser and compiler and can be included only in .ascx files (user controls).

@ Implements - Indicates that a page or user control implements a specified .NET Framework interface declaratively.

@ Import - Imports a namespace into a page or user control explicitly.

@ Master - Identifies a page as a master page and defines attributes used by the ASP.NET page parser and compiler and can be included only in .master files.

@ MasterType - Defines the class or virtual path used to type the Master property of a page.

@ OutputCache - Controls the output caching policies of a page or user control declaratively.

@ Page - Defines page-specific attributes used by the ASP.NET page parser and compiler and can be included only in .aspx files.

@ PreviousPageType - Creates a strongly typed reference to the source page from the target of a cross-page posting.

@ Reference - Links a page, user control, or COM control to the current page or user control declaratively.

@ Register - Associates aliases with namespaces and classes, which allow user controls and custom server controls to be rendered when included in a requested page or user control.

This list has been taken from here.

Explain the Validation Controls used in ASP.NET 2.0?

Validation controls allows you to validate a control against a set of rules. There are 6 different validation controls used in ASP.NET 2.0.

RequiredFieldValidator – Checks if the control is not empty when the form is submitted.

CompareValidator – Compares the value of one control to another using a comparison operator (equal, less than, greater than etc).

RangeValidator – Checks whether a value falls within a given range of number, date or string.

RegularExpressionValidator – Confirms that the value of a control matches a pattern defined by a regular expression. Eg: Email validation.

CustomValidator – Calls your own custom validation logic to perform validations that cannot be handled by the built in validators.

ValidationSummary – Show a summary of errors raised by each control on the page on a specific spot or in a message box.

How do you indentify that the page is post back?

By checking the IsPostBack property. If IsPostBack is True, the page has been posted back.

What are Master Pages?

Master pages is a template that is used to create web pages with a consistent layout throughout your application. Master Pages contains content placeholders to hold page specific content. When a page is requested, the contents of a Master page are merged with the content page, thereby giving a consistent layout.

How is a Master Page different from an ASP.NET page?

The MasterPage has a @Master top directive and contains ContentPlaceHolder server controls. It is quiet similar to an ASP.NET page.

How do you attach an exisiting page to a Master page?

By using the MasterPageFile attribute in the @Page directive and removing some markup.

How do you set the title of an ASP.NET page that is attached to a Master Page?

By using the Title property of the @Page directive in the content page. Eg:

<@Page MasterPageFile="Sample.master" Title="I hold content" %>

What is a nested master page? How do you create them?

A Nested master page is a master page associated with another master page. To create a nested master page, set the MasterPageFile attribute of the @Master directive to the name of the .master file of the base master page.

What are Themes?

Themes are a collection of CSS files, .skin files, and images. They are text based style definitions and are very similar to CSS, in that they provide a common look and feel throughout the website.

What are skins?

A theme contains one or more skin files. A skin is simply a text file with a .skin extension and contains definition of styles applied to server controls in an ASP.NET page. For eg:

<asp:button runat="server" BackColor="blue" BorderColor="Gray" Font-Bold ="true" ForeColor="white"/>

Defines a skin that will be applied to all buttons throughout to give it a consistent look and feel.

What is the difference between Skins and Css files?

Css is applied to HTML controls whereas skins are applied to server controls.

What is a User Control?

User controls are reusable controls, similar to web pages. They cannot be accessed directly.

Explain briefly the steps in creating a user control?

· Create a file with .ascx extension and place the @Control directive at top of the page.

· Included the user control in a Web Forms page using a @Register directive

What is a Custom Control?

Custom controls are compiled components that run on the server and that encapsulate user-interface and other related functionality into reusable packages. They can include all the design-time features of standard ASP.NET server controls, including full support for Visual Studio design features such as the Properties window, the visual designer, and the Toolbox.

What are the differences between user and custom controls?

User controls are easier to create in comparison to custom controls, however user controls can be less convenient to use in advanced scenarios.

User controls have limited support for consumers who use a visual design tool whereas custom controls have full visual design tool support for consumers.

A separate copy of the user control is required in each application that uses it whereas only a single copy of the custom control is required, in the global assembly cache, which makes maintenance easier.

A user control cannot be added to the Toolbox in Visual Studio whereas custom controls can be added to the Toolbox in Visual Studio.

User controls are good for static layout whereas custom controls are good for dynamic layout.

Where do you store your connection string information?

The connection string can be stored in configuration files (web.config).

What is the difference between ‘Web.config’ and ‘Machine.config’?

Web.config files are used to apply configuration settings to a particular web application whereas machine.config file is used to apply configuration settings for all the websites on a web server.

Web.config files are located in the application's root directory or inside a folder situated in a lower hierarchy. The machine.config is located in the Windows directory Microsoft.Net\Framework\Version\CONFIG.

There can be multiple web.config files in an application nested at different hierarchies. However there can be only one machine.config file on a web server.

What is the difference between Server.Transfer and Response.Redirect?

Response.Redirect involves a roundtrip to the server whereas Server.Transfer conserves server resources by avoiding the roundtrip. It just changes the focus of the webserver to a different page and transfers the page processing to a different page.

Response.Redirect can be used for both .aspx and html pages whereas Server.Transfer can be used only for .aspx pages.

Response.Redirect can be used to redirect a user to an external websites. Server.Transfer can be used only on sites running on the same server. You cannot use Server.Transfer to redirect the user to a page running on a different server.

Response.Redirect changes the url in the browser. So they can be bookmarked. Whereas Server.Transfer retains the original url in the browser. It just replaces the contents of the previous page with the new one.

What method do you use to explicitly kill a users session?

Session.Abandon().

What is a webservice?

Web Services are applications delivered as a service on the Web. Web services allow for programmatic access of business logic over the Web. Web services typically rely on XML-based protocols, messages, and interface descriptions for communication and access. Web services are designed to be used by other programs or applications rather than directly by end user. Programs invoking a Web service are called clients. SOAP over HTTP is the most commonly used protocol for invoking Web services.

So I and my coworkers (Joe Levi and Angela Perry) were fast installing Commerce Server 2007 sp1(you know I shouldn't leave out the sp1. It gives it an edge.(besides that I could get sued!)) We arrived at the 8 minute mark of go ahead and create my database when this happened:

 

 

"---------------------------
Error
---------------------------
An error occurred when configuring the feature 'Administration Database'. The configuration log file may have more details about the error.

Error Summary:

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_Sites_s_Name".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_errstr1".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@site".

Must declare the scalar variable "@res_id".

Must declare the scalar variable "@localized_string_errstr4".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

The variable name '@site_id' has already been declared. Variable names must be unique within a query batch or stored procedure.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_errstr5".

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@res_id".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_connstr_db_Catalog".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_num_full_text_catalogs".

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_SystemProps_s_Description_AppDefaultConfig".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_S_BizTalkSourceQualifierID".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_S_BizTalkOrderDocType".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_S_BizTalkSubmittypeQueue".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_S_WeightMeasure".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_i_SitePrivacyOptions".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_i_CurrencyDisplayOrderOptions".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_AnonymousUserDefaultCatalogSet".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_i_AddItemRedirectOptions".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_i_PaymentOptions".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_i_ShipToLevelOptions".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_i_BaseCurrencyLocale".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_i_SiteTicketOptions".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_i_HostNameCorrectionOptions".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_AltCurrencySymbol".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_f_AltCurrencyConversionRate".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_AltCurrencyCode".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_SMTPServerName".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_i_DelegatedAdminOptions".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_RequiresASCIIIdentifiers".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_connstr_db_TransactionConfig".

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_SystemProps_s_Description_Transactions".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_connstr_db_Campaigns".

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_SystemProps_s_Description_BDSecurity".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_SystemProps_s_Description_AuthManager".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_Logon_Form".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_u_cache_size".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_auth_profile_name".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_Auth_HelperDir".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_Help_Form".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_Migration_Form".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_AutoCookie_Form".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_d_CookieExpirationDate".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_AuthManager_EncryptionKey".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_u_CookieDomain_Scope".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_max_err_count".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_delivery_method".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_msg_per_hour".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_pcf_file".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_perf_interval".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_i_NumOfRetries".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_i_Interval".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_SystemProps_s_Description_GlobalDatawarehouse".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_SystemProps_s_Description_connstr_db_dw".

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_SystemProps_s_Description_connstr_db_Analysis".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_SystemProps_s_Description_ConnStr_OLAP".

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_SystemProps_s_Description_ConnStr_OLAP_HA".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_SystemProps_s_Description_SiteDatawarehouse".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_SystemProps_s_Description_BizDataService".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_ExtendedProps_s_Description_s_ProfileServiceConnectionString".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@localized_string_SystemProps_s_Description_Address".

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Incorrect syntax near '0x0a0d'.

Must declare the scalar variable "@s_CurrentVersion".

Must declare the scalar variable "@s_CurrentVersion".

Must declare the scalar variable "@s_CurrentVersion".

Must declare the scalar variable "@s_CurrentVersion".

Must declare the scalar variable "@s_CurrentVersion".

Must declare the scalar variable "@s_CurrentVersion".

---------------------------
OK  
--------------------------- "

 

If you stuck around this long. Means you either read the entire error and you are a Microsoft Premier support professional or you are just about to hit that comment button and send me an email saying dude that is a error when creating a database and you don't have proper permissions. Yes I know that and that last statement really was one sentence.

Mostly the reason for this post is showing you the length and sheer wowness (Angela I know "wowness" is very poor SEO. However I am assuming Joe is laughing.) of the error. The only way to correct this error that I know (because I am not a SQL admin (even though I play one at another job)) is to run the sql scripts that were used to create the database in the first place one at a time until the database stops freaking out.

This little rant brought to you by Commerce Server 2007  and the corresponding Service pack 1.

almost forgot the social bookmarking tags:

I love Yahoo for this and the YUI Install it on your blog today.

Yahoo Media Player.

I being a very intelligent web developer (This is true). Decided it might be fun to delete the Default Web Site in IIS6.0 not thinking much of it. Of course it wouldn't have mattered at all, at least until I decided to install commerce server 2007 enterprise on the production server that I had deleted the Default Web Site.

Why was this a problem you ask? Wow good question. Here's the long and short of it.

When installing Microsoft Commerce Server 2007 sp1 you can get about oh I'd say 5 minutes into the install until you get to Web Site configuration settings. You put your user name in the little sign in box as well as your password like any good little wizard following monkey. Then terror err I mean error strikes you. The error says hey idiot I cannot find your "Default Web Site" you cannot continue. Well gall darn you say I will just right click on the web site folder and create a new web  site called "Default Web Site". Ah doesn't that feel better? You say to the Monkey wizard (Commerce Server 2007 sp1 config wizard). No says the error again. So you jump up and down screaming at the server. What the brown bananas do you mean its right there!

Well turns out that there is a super er... uber  secret metadatabase that keeps a ID stored for every site created and the one you just created "Default Web Site" is W3SVC/890987799887.... on and on for about 6 more decimals. Problem is Windows likes the "Default Web Site" to be W3SVC/1. What do you do? Uninstall IIS? Holy foolish that would be.

Try this before moving on.

There is a fun little vb script built just for this occasion. "adsutil"! Remember it and love it.

First we need to make sure there for whatever reason isn't a W3SVC/1 already there ( I know you are saying: but the story you took me down this long path and....) No worries its always good to dot your T's and Cross your I's or is that wrong too?

Go to your nearest command prompt.

make sure you are at the root of C:\

cd\Inetpub\AdminScripts

once there run this: cscript adsutil.vbs enum w3svc/1

If it comes back with "path requested could not be found" you know your hosed.

Try this: cscript adsutil.vbs enum w3svc

All kinds of data will fly by and the world will turn upside down (unless you are in Australia. However if you are there you are smart enough not to delete the web site in the first place.).

You should get: w3svc/Info w3svc/Filters and at least one w3svc/### where the number is the interesting part.

To find your new default web site number will take some looking up. Hunt by using this: cscript adsutil.vbs enum w3svc/### putting the numbers you saw in the list.

Ok the good part.

Create the new W3SVC/1

     cscript adsutil.vbs create_vserv W3SVC/1

Copy it

    cscript adsutil.vbs copy W3SVC/### W3SVC/1

Set It

    cscript adsutil.vbs set w3svc/1/ServerComment "Default Web Site"

So now you have a new Default Web Site and you now know not to delete it again or there will be consequences.

I believe it was Joe Levi who was running into vista vs. Visual Studio 2005 memory issues while compiling our latest build of www.lifetime.com . We both run Vista as our development environment (We watched all the sessions at mix07 and vista looked like it worked fine with Visual Studio 2005 + 2 hours of patches).  We did some MSDN surfing and found a way to clear the memory within Windows Vista ( basically it kills all idle running applications).

Here is how:

Create a shortcut:

Add Location of Shortcut:

"%windir%\system32\rundll32.exe advapi32.dll,ProcessIdleTasks"

Click Next, Change the name of your shortcut:

To:

Then Finish.

Extra Credit:

  Set up a the windows task manager to run this task every oh half hour or so.

Feel free to use the XML provide to update your task. Courtesy of Joe Levi:

<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
  <RegistrationInfo>
    <Date>2008-02-26T10:20:16.4557818</Date>
    <Author>*Add Your Info Here*</</Author>
    <Description>%windir%\system32\rundll32.exe advapi32.dll,ProcessIdleTasks</Description>
  </RegistrationInfo>
  <Triggers>
    <TimeTrigger id="502f2271-c7c8-428a-9ac6-47359a741e19">
      <Repetition>
        <Interval>PT30M</Interval>
        <StopAtDurationEnd>false</StopAtDurationEnd>
      </Repetition>
      <StartBoundary>2008-02-26T07:00:00</StartBoundary>
      <ExecutionTimeLimit>PT30M</ExecutionTimeLimit>
      <Enabled>true</Enabled>
    </TimeTrigger>
  </Triggers>
  <Principals>
    <Principal id="Author">
      <UserId>*Add Your Info Here*</UserId>
      <LogonType>InteractiveToken</LogonType>
      <RunLevel>HighestAvailable</RunLevel>
    </Principal>
  </Principals>
  <Settings>
    <IdleSettings>
      <Duration>PT10M</Duration>
      <WaitTimeout>PT1H</WaitTimeout>
      <StopOnIdleEnd>true</StopOnIdleEnd>
      <RestartOnIdle>false</RestartOnIdle>
    </IdleSettings>
    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
    <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
    <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
    <AllowHardTerminate>true</AllowHardTerminate>
    <StartWhenAvailable>true</StartWhenAvailable>
    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
    <AllowStartOnDemand>true</AllowStartOnDemand>
    <Enabled>true</Enabled>
    <Hidden>false</Hidden>
    <RunOnlyIfIdle>false</RunOnlyIfIdle>
    <WakeToRun>false</WakeToRun>
    <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
    <Priority>7</Priority>
    <RestartOnFailure>
      <Interval>PT5M</Interval>
      <Count>3</Count>
    </RestartOnFailure>
  </Settings>
  <Actions Context="Author">
    <Exec>
      <Command>%windir%\system32\rundll32.exe</Command>
      <Arguments>advapi32.dll,ProcessIdleTasks</Arguments>
    </Exec>
  </Actions>
</Task>

Enjoy!

   This past MIX was my sophomore year. I had the chance to go to MIX07 last year. In fact have a glance at my RSS feed for that. I traveled once again with Joe Levi, courtesy of Lifetime Products.

The great things about MIX was the sessions. I did however enjoy the keynotes as they do always get you fired up for the rest of the conference as well as giving you a chance to see what and where Microsoft is going with the .NET framework as well as ASP.NET.

My feet are still blistered and I still am morning the loss of my Hacked Zune.

However the experience was awesome. I am hoping to be at MIX09 for my Junior year there.

I can't forget to give a friendly shout out to my new friends in the .NET community. I even made some friends from company's like:

WeatherBug  Tamir Melamed

Godaddy David Koopman

Jinx.com Scott "Brolo" Benner

Yahoo! Joshua Jacobson

CodeSmith Eric Smith

MotionCloud Pureum Kim

Koda Software  Tor Langlo

RogerGuess

Geoffrey Emery

Alec Bryte

And More...

Favorite Session:

ASP.NET MVC - Scott Hanselman

Least Favorite:

  WPF Development. Not because it was bad but it was the last session and I was exhausted.

Overall it was a great experience.

By the way check out a great Elvis/Johnny Cash impersonator

Thanks again Lifetime and Microsoft.