Showing posts with label DotNet. Show all posts
Showing posts with label DotNet. Show all posts

Tuesday, September 6, 2011

bench3

Error 0x80131700 Loading Troubleshooting Wizard | Fix Crashing Troubleshooting Wizard

The following article will explain how to fix if your Windows 7 Troubleshooting Wizard does not start.

If you experience this kind of problem that none of your Troubleshooting wizard starts to work. And even if you manually attempt to use the wizard you will see the following error message.

"An unexpected error has occurred.  The trouble shooting wizard can't continue."  Some times you will see (0x80131700) error code in advanced dialog box. So, what is the cause and what is the solution for this problem or error 0x80131700.

Solution:

Error code 0x80131700 is usually relevant to the old version of .NET Framework installed on your system. By default, the built-in version of Micorosoft .NET Framework is 3.5.1. You can reinstall Microsoft .NET Framework 3.5 Service Pack 1 through the following steps:

1) Click  the Start and type: features in the Search box.

2) Select "Turn Windows Features on or off " and click Enter.

3) Find Microsoft .NET Framework 3.5.1 and uncheck the box.

4) Restart the computer.

5) Repeat the step 1) to step 2.

6) Check the box before Microsoft .NET Framework 3.5.1.

7) Restart the computer.

If you still face problem, you can either download the Microsoft .NET Framework 3.5.1 package and install it or you can download the latest Microsoft .NET Framework package from this location.

Read More

Sunday, July 17, 2011

bench3

Installing .NET Framework In Windows Vista And Windows 7

If you have ever tried to install Microsoft's .Net Framework on Windows Vista or on Windows 7. If you have tried to install from the downloaded setup file, the installation will actually fail with a error message that .Net frame work needs to be installed from programs and features – Turn Windows Features on or off…

This article will let you know how you can install Microsoft's .Net framework and Security Update for .NET Framework 4 on Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2 for x64-based Systems (KB2160841).

Solution: Try the following steps:

  • Go To Control Panel (Refer Screen Shots)

Installing .NET Framework In Windows Vista And Windows 7 1

  • Go to Program and Features, click it.

If you want to install .Net Frame work for the first time, choose “Turn Windows Features on or off” From the left side on the windows as shown in the below Screen Shot.

Installing .NET Framework In Windows Vista And Windows 7 2

Then, browse to Microsoft .Net Framework Section and check all the check boxes related to .Net Framework and then choose Ok to Install.

Installing .NET Framework In Windows Vista And Windows 7

The installation will take time depending on your system performance.

Reboot your system once the installation is complete.

The above steps will help you only in case if you want to Install .Net framework for the first time. In case if you have already installed and want to repair it, or when you experience error installing .Net through Windows Update (KB2160841) follow the below steps.

After choosing Programs and Features menu in Control panel

  • Scroll down to Microsoft.Net Framework 4 Client Profile, right click it.
  • It will give you a choice of Uninstall/Change, click it.
  • Then, it will give a choice to Repair it, pick Repair   it.  It will take about 4-10 minutes to repair depending upon your PC Performance.
  • When completed, go to your update center, and see if you can update .Net frame work this time.

If this doesn't fix it, try to remove .Net Framework 4.0 with the .NET Framework Cleanup Tool

(http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx ), reinstall it and install the Updates.

Read More

Wednesday, December 29, 2010

bench3

.Net 4.0 Is Not Included In Service Pack 1 Of Windows Server 2008 R2

Is net 4.0 part of service pack 1? Answer is probably no. It is not part of Windows Server 2008 R2 SP1, but we can install it with the Installer.

It is an important feature, and why it's not included in Windows Server 2008 R2 SP1:  
.net Framework will be inlcuced into Windows WHEN a tool inside the Windows needs it. It makes sense because not many many programs need .net 4.0 runtime and not many were written in net 4.0? So, it is adjustable as long as we can use the installer to make use of it when ever required.
Note: .Net 4.0 was Released To Manufacturing (RTM) in March 2010 after Windows 7 is out, so No Windows 7 tool uses it. But, the next version of Windows, Windows 8 will mostly include it. 
Related Post:
Fact: Currently the amount of tools which use .net 4.0 is very small. But it will grow. .Net 4.0 was released with Visual studio 2010 this year, so it takes a time until the first programs use it.
Read More

Sunday, September 19, 2010

bench3

Installing Microsoft DotNet Framework 3.5 In Windows Server 2008

Your installation will stop with an error message (as shown in figure below) when ever you try to install Microsoft .NET Framework 3.5 On WINDOWS SERVER 2008 (x32/ X64) Version And Edition

The Error message will be this “You must use the Role Management Tool to install or configure Microsoft .NET Framework 3.5”.
What to do when you get this type of error message. Well, it is clearl said in the message that, you need to use the Role Manager Tool. 
  • 1. Start the Server Manager (also called as Role Manager) by clicking the Server Manager icon in the systray, or the Server Manager shortcut in directly the Start menu or in the menu Administrative Tools
  • 2. Choose Features
  • 3. Click on the check box "Microsoft .NET Framework 3.5"

  • 4. Click On Install. And Restart Your Server If It asks.
Read More

Saturday, January 16, 2010

bench3

Understanding The DotNet FrameWork

UNDERSTANDING THE .NET FRAMEWORK: The .NET Framework attempts to transform applications to online services that can be used over the Internet or in intranet environments. The underlying goal is to provide customized and comprehensive solutions to users regardless of a user's location or computer system. 

To achieve this goal, the server-centric approach to computing that currently defines the Internet must change. Another challenge is to break away from the concept of localized client-based applications. Looking into the future, a user should be able to log on to any system and get access to its data, applications, and even familiar settings. To realize this ability requires looking at applications and systems not as standalone entities but as services that are called on demand by the user. 

These application services could replace packaged software and be rented or leased over the Internet. Packaged software will probably not disappear, but Microsoft officials believe that this new model will radically affect the way businesses and consumers obtain up-to-date products and conduct business. Individual and corporate users conceptually will be able to get applications on demand through either a subscription or a rental arrangement. A prime example of how this could work is the automatic operating system update facilities provided by Windows XP and Windows Server 2003. When patches need to be applied, updates over the Internet can be applied automatically or interactively.

Foundation Technologies
The concepts underlying .NET are industry-standard technologies that should enhance its acceptance and interoperability. Microsoft believes that this approach is founded on the basic principles of common description, connection, communication, and discovery.
The eXtensible Markup Language (XML) is the centerpiece of the .NET strategy. This open standard is managed by the World Wide Web Consortium (W3C). Stated simply, XML changes the way in which applications talk to one another. It is designed to enable the development of applications that permit the easy exchange of data between any enabled computing devices. XML separates the underlying data from how the data is displayed. This schema effectively "unlocks" the data so that it can be reorganized, edited, and exchanged with any Web site, device, or enabled application.

In addition to XML, the .NET Framework utilizes other rapidly emerging standards:
  • The Simple Object Access Protocol (SOAP) was developed by Microsoft but turned over to the W3C for open standards management. SOAP enables communications and makes service requests.
  • The Web Service Description Language (WSDL) is a standard format that publishes function names, required parameters, and returned results from an XML Web service.
  • Discovery services are provided by the Universal Description, Discovery, and Integration (UDDI) standard. In theory, it makes it easy to locate XML services and facilitates. UDDI is the "yellow pages" of XML Web services.
Components of .NET and Product Layers
The .NET Framework consists of three primary layers. The universal run-time engine handles the lowest level of services, which includes thread management. Conceptually similar to Sun Microsystems's Java Virtual Machine, this engine manages environmental matters. A common class library rests on the universal run-time engine. The code objects can communicate with applications written in any programming language. This facility makes it possible to use large amounts of legacy code for .NET-enabled environments. Active Server Pages Plus is the highest layer and serves to separate scripts from Web-based code.

The .NET initiative was initially a vision exposed by Microsoft Chairman and Chief Software Architect Bill Gates. Unlike so many industry "visions" of the future, the concepts were soon transformed in a Framework with a wide range of Windows 2000-centric products. Products such as Microsoft Exchange 2000 and Microsoft SQL Server 2000 are the first component products to be released with .NET-enabling technology. As the following list shows, the complete suite of .NET products provides an impressive solution set. In addition to server back-end products, flagship customer products like Microsoft Office are emerging as .NET-enabled.

BACK-END APPLICATIONS AND TOOLS
  • BizTalk Server. This product uses XML to integrate Web services with business application logic and data.
  • Host Integration Server. This product is designed to communicate with legacy networks, applications, and data.
  • SQL Server. This advanced database provides more analytical support and data warehousing capacity than previous versions.
  • Visual Studio Family and C#. This is the next iteration of the Visual Studio suite and it encompasses the C# language, XML support, and other features. Probably more than any other offering by Microsoft, the Visual Studio .NET suite should ensure the viability of the .NET Framework and the success of the Windows Server family.
MID-TIER SUITES
  • Application Center 2000. This server product provides the management, scaling, and deployment of applications.
  • Commerce Server 2000/2002. This server is designed for greater Web site design including enhanced user tracking.
  • Content Management Server 2001. As the name implies, this manages Internet-based content delivery.
  • SharePoint Portal Server. This server is used to find, share, and publish information easily by employing a flexible portal solution model.
  • Exchange Server. This version expands its integration with Active Directory and provides more Web-enabled collaborative work and messaging.
  • Mobile Information Server. Mobile Information Server enables secure access to data on Exchange and Enterprise servers for mobile users.
FRONT-END TIER
Internet Security and Acceleration Server. This server provides caching of Web data together with firewall protection.

The development of applications that take full advantage of .NET is critical to its ultimate success.

The release of new versions of .NET Servers together with completely new products is anticipated to continue at fever pace. Don't be surprised if the names of the products just mentioned undergo change. As more .NET components are added, the ability of these products to take full advantage of underlying Windows Server functionality should be enhanced.

BackOffice Suite Moves Forward as Renamed .NET Products
The much ballyhooed BackOffice suite that supplemented Windows NT and Windows 2000 has quietly slipped to the very back of the office. Although the Back Office bundle is no longer marketed, the individual components are available. Several of these products have been renamed, as have other server products, including:
  • The Commercial Internet System is now Commerce Server.
  • The Exchange Server retains its name but with a new extension.
  • The Proxy Server is now the vastly enhanced Internet Security Acceleration Server 2000.
  • The Site Server can still be used as an intranet deployment tool primarily but is largely replaced by Commerce Server 2000.
  • The System Management Server, version 2.0, is still one of the primary management tools and is widely used for software administration.
  • The SNA Server is now Host Integration Server.
  • The SQL Server retains its name but with new extensions and vastly expanded functions.
Microsoft Operations Manager
Microsoft provides three options in server products designed to assist administrators: (1) Application Center, (2) System Management Server (SMS), and (3) the new Microsoft Operations Manager (MOM). Here we offer an overview of MOM to underscore the potential importance of this tool set for administration. Stated simply, MOM extends the management tool set of Microsoft operating system servers and .NET Enterprise Server products. Through third-party extensions from vendors like NetIQ, other platforms can also be consistently managed. The following are some major features of MOM:
  • Event management. MOM provides event management for Windows Server, Active Directory, Internet Information Services (IIS), some .NET Enterprise Servers and the old Windows NT Server 4.0. This includes an enterprise event log that collects and reports on problems and information.
  • Proactive monitoring and alert messaging. MOM's distributed capabilities track and monitor information. Based on levels of urgency, the MOM will issue alerts to pagers, through e-mail, or by other external means.
  • Reporting and trend analysis. MOM provides reporting and trend analysis features that examine problems across time and generate detailed reports.
  • Specialized management packs. In order to focus domain-specific operations better, detailed management packs for different Microsoft technologies and products are available. Packs are available for Windows NT Server 4.0, Windows Server, Active Directory, IIS, Terminal Services, Microsoft Distributed Transaction Coordinator (MDTC), Windows Internet Naming Service (WINS), Dynamic Host Configuration Protocol (DHCP), Domain Name Service (DNS), Routing and Remote Access Service, Microsoft Transaction Service (MTS), Microsoft Message Queuing (MSMQ), Exchange Server, Microsoft SQL Server, Proxy Server, Systems Management Server, Commerce Server, and Host Integration Server.
  • Scalable management. MOM provides a sophisticated, load-balancing, multitier architecture designed to manage IT environments with thousands of Windows-based servers and applications.
  • An agile solution to meet the changing needs of business. MOM 2000 provides business flexibility via management rules. It is shipped with default rules that allow you to benefit quickly from the product. The rules can be customized to meet the changing needs.
  • Interoperation with other management systems. MOM 2000 integrates with other enterprise management systems by using Simple Network Management Protocol (SNMP) and Windows Management Instrumentation (WMI), which is based on the Common Information Model (CIM) supported by the Desktop Management Taskforce (DMTF).
Read More