Jack is Here, asp.net findings

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries Tagged ‘Server’

Access to an MPIO-controlled storage device fails on a Windows Server 2008-based computer after you disconnect and then reconnect all data cables

Symptoms
Consider the following scenario:You connect a Windows Server 2008-based computer to a storage device that is controlled by Microsoft Multipath I/O (MPIO).You use a third-party device specific module (DSM) for MPIO.You disconnect all data cables and then reconnect them.In this scenario, access to the storage device fails. Therefore, applications that try to access the storage device crash or receive an exception. This problem persists until you restart the Windows Server 2008-based computer.
Resolution
Hotfix informationImportant Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesNo prerequisites are required.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.File information notesThe files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Collapse this tableExpand this table
VersionProductMilestoneService branch6.0.6000.16xxxWindows VistaRTMGDR6.0.6000.20xxxWindows VistaRTMLDR6.0.6001.18xxxWindows Vista SP1 and Windows Server 2008 SP1SP1GDR6.0.6001.22xxxWindows Vista SP1 and Windows Server 2008 SP1SP1LDRService Pack 1 is integrated into Windows Server 2008.The MANIFEST (.manifest) files and MUM (.mum) files that are installed for each environment are listed separately. MUM and MANIFEST files and their associated security catalog (.cat) files are critical to maintaining the state of the updated component. The security catalog files are signed with a Microsoft digital signature. (The attributes of these files are not listed.)All supported x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMpio.infNot applicable3,76004-Feb-200900:45Not applicableMpio.sys6.0.6001.22368104,41604-Feb-200906:06x86All supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMpio.infNot applicable3,76804-Feb-200900:44Not applicableMpio.sys6.0.6001.22368128,48004-Feb-200906:30x64All supported Itanium-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMpio.infNot applicable3,76403-Feb-200923:42Not applicableMpio.sys6.0.6001.22368282,60804-Feb-200905:07IA-64

A memory leak occurs when an ADO Recordset object calls the UpdateBatch method

Symptoms
Consider the following scenario:You have an SQL table that contains an identity column.You start an application that uses a Microsoft ActiveX Data Objects (ADO) client-side Recordset object to access the SQL database. This application calls the UpdateBatch method to insertseveral rows into the table.In this scenario, you find a memory leakoccurs.
If you use Performance Monitor (Perfmon.exe) to monitorapplication processes, you notice that the value of the Private Bytes counter continually increases. This is evidence of a memoryleak.
Resolution
Hotfix information A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesTo apply this hotfix, your computer must be running one of the following operating systems:Windows Server 2003 Service Pack 2 (SP2)Windows Vista Service Pack 1 (SP1)Windows Vista Service Pack 2 (SP2)Windows Server 2008Windows Server 2008 Service Pack 2 (SP2)Windows 7Windows Server 2008 R2For more information about how to obtain a Windows Server 2003 service pack or a Windows XP Professional x64 Edition service pack, click the following article number to view the article in the Microsoft Knowledge Base:
889100?(http://support.microsoft.com/kb/889100/) How to obtain the latest service pack for Windows Server 2003 For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791?(http://support.microsoft.com/kb/935791/) How to obtain the latest Windows Vista service packFor more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849?(http://support.microsoft.com/kb/968849/) How to obtain the latest service pack for Windows Server 2008Registry informationTo use the hotfix in this package, you do not have to make any changes to the registry.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.Windows Server 2003 file information noteIn addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.For all supported x86-based versions of Windows Server 2003
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll2.82.4635.0356,35211-Dec-200916:48For all supported x64-based versions of Windows Server 2003
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMsadce.dll2.82.4635.0622,59211-Dec-200914:42x64Wmsadce.dll2.82.4635.0356,35211-Dec-200914:42x86For all supported IA-64-based versions of Windows Server 2003
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMsadce.dll2.82.4635.01,212,41611-Dec-200914:41IA-64Wmsadce.dll2.82.4635.0356,35211-Dec-200914:41x86Windows Vista and Windows Server 2008 file information notesImportant Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only “Windows Vista” is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under “Windows Vista” on the page. Always refer to the “Applies To” section in articles to determine the actual operating system that each hotfix applies to.The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Collapse this tableExpand this table
VersionProductSR_LevelService branch6.0.600 1.22xxxWindows Vistaand Windows Server 2008SP1LDR6.0.600 2.22xxxWindows Vistaand Windows Server 2008SP2LDRService Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.For all supported x86-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll6.0.6001.22581454,65611-Dec-200914:53Msadce.dll6.0.6002.22286454,65611-Dec-200914:28For all supported x64-based versions of Windows Server 2008 and ofWindows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll6.0.6001.22581589,82411-Dec-200915:11Msadce.dll6.0.6002.22286589,82411-Dec-200914:28For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll6.0.6001.225811,175,55211-Dec-200914:54Msadce.dll6.0.6002.222861,175,55211-Dec-200914:28Windows 7 and Windows Server 2008 R2 file information notesImportant Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under “Windows 7/Windows Server 2008 R2″ on the page. Always refer to the “Applies To” section in articles to determine the actual operating system that each hotfix applies to.For all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll6.1.7600.20595561,15213-Dec-200908:56For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll6.1.7600.20595749,56813-Dec-200911:12For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll6.1.7600.205951,335,29613-Dec-200908:25

Data storage

Data storage has become a hot technology, the Internet is following the heat wave after another technology that will network into the data-centric era. This article will present the popular data storage technologies are summarized summary and data storage trends and future data storage technologies have made some subjective forecast.

Server data storage through three stages: direct plug-in storage (DAS), storage area networks (SAN), Network Attached Storage (NAS). DAS is a CPU-centric computing is king of the times, adapt to the initial development of the computer industry, and for SAN and NAS, the biggest difference in the result is technically a special agreement or use of existing IP technology, and data sharing and other issues were considered, SAN has the advantage of the initial consideration to solve the problem of network bandwidth, while the NAS is more emphasis on versatility and data sharing considerations.

Fibre Channel SAN infrastructure is currently the only option to establish, but with new technology and market dual role in the future may be used G/10G Ethernet and / or InfiniBand architecture (the IBA) to achieve the SAN.

Currently, several existing and future network interconnection standards are to fight for market and competition, Infiniband several obvious competitor is the PCI-X, G/10G Ethernet, Fibre Channel, Rapid I / O , HiPPI-6400 (GSN). In data storage solutions, Infiniband will face G/10G Ethernet technology challenges.

From the initial server to the current focus on data archiving solutions, we can generally see a computer network server architecture trend that the current internal bus architecture will gradually die out, the formation of switched (fabrics) network development the direction of the trend in the first, data storage, computing and I / O is combined into one, and the current data storage part is independent, the future will be the I / O and computing further separation, the formation of data storage, computing , I / O throughput of the three pillars of the situation, this is the real server network architecture, is to be the SUN company’s “network is the computer” thesis.

Unhandled exceptions are caught by the Visual Studio JIT debugger instead of Dr. Watson or a third-party debugger after you install certain versions of SQL Server 2005

Symptoms
Consider the following scenario:You use the Dr. Watson program or a third-party debugger to catch unhandled exceptions that may occur when a program is running.You install one of the following Microsoft products:SQL Server 2005 Standard EditionSQL Server 2005 Developer EditionSQL Server 2005 Enterprise EditionSQL Server 2005 Workgroup EditionAny product that contains one of the previously listed products
(For example, you install Microsoft Windows Small Business Server 2003 R2 Premium Edition.)In this scenario, later unhandled exceptions are caught by the Microsoft Visual Studio just-in-time (JIT) debugger. For example, if a Data Execution Prevention (DEP) exception occurs, a dialog box appears that requires user intervention to either start JIT debugging or ignore the exception.
Resolution
This issue occurs because the SQL Server 2005 installation process calls the Visual Studio installation process. The Visual Studio installation process changes the default application debugger to the Visual Studio JIT debugger. This change occurs regardless of which debugger you previously used. You do not receive any notification that this change has occurred.

Php – A First Look

The PHP: Haipatekisutopurosessa is a server-side Web programming language, HTML and blends seamlessly with the. Both PHP, Unix and Windows servers, or it is Windows, and Active Server Pages (ASP) can be able to run on more accessible. Most full-service Web design company, has at least one PHP guru.

PHP uses are widespread, and can include any kind of server functionality that takes user’s input and displays or manipulates the input. Some pertinent examples of such work are message boards, auction sites, shopping carts, and more. This synopsis is meant to serve only as a gateway to other works; although the main goal is to give a reader enough information so they can make educated decisions about what their web developer should do. For those looking to get into PHP, there are many free tutorials and primers out there:

http://www.4webhelp.net/tutorials/php/basics.php, is a striking example
PHP generally uses the MySQL database system. MySQL server is a lot of Unix systems that are included on the side, and some of the Windows server.

Once a user knows the basics of PHP and its capacities, he can work with plenty of open-source scripts. Without having to actually build a script from scratch, one can get a fully functional website with a custom design (assuming the designer has HTML/graphics knowledge). Two of the most popular open-source (free) scripts for PHP/mySQL are PHPBB and osCommerce. PHPBB is forum software that is fairly common. It has all the main features of a message board and can have mods (modules) added for more features. OsCommerce is a shopping cart script that has support for many payment gateways, including some free ones like Paypal. The great thing about scripts like these is that they have a full community of developers – both beginners and professionals – that are there to help with installation and modification.

However, if a user doesn’t feel that he’s ready to take the plunge and work with PHP code, most web design firms are more than willing to work with open-source scripts. Others even have their own pre-made, or can work from scratch for an upgraded fee. Sometimes, an open source script simply won’t suffice because a user needs something tailored to his needs. Larger-scale online business and e-treps require capabilities that may be out of the reach of osCommerce.

In conclusion, PHP is a server-side scripting language widely used functions for web developers who offer to interact with their viewers. It may take years to master a technology like this, but there are many bargains out there for pre-made scripts or from the ground up technologies. This story serves as an introduction to PHP, later articles will go into further detail.