Tag Archives: Microsoft

Workaround: SharePoint 2013 Preview prerequisite installer doesn’t install the Microsoft SQL Server 2008 R2 SP1 Native Client

SharePoint-2013

If you install SharePoint 2013 Preview by running the prerequisite installer (Microsoft SharePoint Products Preparation Tool) and you see this line in the log file:

Error: The tool was unable to install Microsoft SQL Server 2008 R2 SP1 Native Client.

Use these steps to work around the problem:

  • Go to http://go.microsoft.com/fwlink/p/?LinkId=262370 and manually download and install the Microsoft SQL Server 2008 R2 SP1 Native Client (1033\x64\sqlncli.msi).

    Important! Do not download and use 1033\IA64\sqlncli.msi or 1033\x86\sqlncli.msi. These versions are not supported for this preview release.

  • Run the Microsoft SharePoint Products Preparation Tool again.
Advertisements

Determine your SQL Server Version, Service Pack, and Edition

SQL Server

To determine the version of SQL Server, you can use any of the following methods:

Method 1

Connect to the server by using Object Explorer in SQL Server Management Studio. After Object Explorer is connected, it will show the version information in parentheses, together with the user name that is used to connect to the specific instance of SQL Server.

Method 2

Connect to the instance of SQL Server, and then run the following query:

Select @@version

An example of the output of this query is as follows:

Microsoft SQL Server 2008 (SP1) – 10.0.2531.0 (X64)   Mar 29 2009 10:11:52
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

Method 3

Connect to the instance of SQL Server, and then run the following query:

SELECT SERVERPROPERTY(‘productversion’), SERVERPROPERTY (‘productlevel’), SERVERPROPERTY (‘edition’)

Note This query works with any instance of SQL Server 2000 or later

The following results are returned:

  • The product version (for example, 10.0.1600.22)
  • The product level (for example, RTM)
  • The edition (for example, Enterprise)

For example, the results resemble the following:

10.0.1600.22 RTM Enterprise Edition

Note The SERVERPROPERTY function returns individual properties that relate to the version information, although the @@VERSION function combines the output into one string. If your application requires individual property strings, you can use the SERVERPROPERTY function to return them instead of parsing the @@VERSION results.

VERSION INFORMATION

SQL Server 2012 version information

The following table lists the major releases of SQL Server 2012:

Release Product Version
SQL Server 2012 Service Pack 1 11.00.3000.00
SQL Server 2012 RTM 11.00.2100.60

SQL Server 2008 R2 version information

The following table lists the major releases of SQL Server 2008 R2:

Release Product version
SQL Server 2008 R2 Service Pack 2 10.50.4000.0
SQL Server 2008 R2 Service Pack 1 10.50.2500.0
SQL Server 2008 R2 RTM 10.50.1600.1

SQL Server 2008 version information

The following table lists the major releases of SQL Server 2008:

Release Product version
SQL Server 2008 Service Pack 3 10.00.5500.00
SQL Server 2008 Service Pack 2 10.00.4000.00
SQL Server 2008 Service Pack 1 10.00.2531.00
SQL Server 2008 RTM 10.00.1600.22

SQL Server 2005 version information

The following table lists the major releases of SQL Server 2005:

Release Product version
SQL Server 2005 Service Pack 4 9.00.5000.00
SQL Server 2005 Service Pack 3 9.00.4035
SQL Server 2005 Service Pack 2 9.00.3042
SQL Server 2005 Service Pack 1 9.00.2047
SQL Server 2005 RTM 9.00.1399

SQL Server 2000 version information

The following table lists version number of the Sqlservr.exe file:

Release Product version
SQL Server 2000 Service Pack 4 8.00.2039
SQL Server 2000 Service Pack 3 8.00.760
SQL Server 2000 Service Pack 3 8.00.760
SQL Server 2000 Service Pack 2 8.00.534
SQL Server 2000 Service Pack 1 8.00.384
SQL Server 2000 RTM 8.00.194

For more information, please refer to Microsoft KB321185 – How To Identify your SQL Server Service Pack Version and Edition.

Ref : lumension

SharePoint 2013 SP1 support in Windows Server 2012 R2

SharePoint-2013

Before the release of Microsoft SharePoint Server 2013 Service Pack 1 (SP1), Microsoft did not support the installation of SharePoint Server 2013 in a Windows Server 2012 R2-based environment. However, with the release of SharePoint Server 2013 SP1, this configuration is supported in Windows Server 2012 R2. You can now download SharePoint Server 2013 SP1 from the Microsoft Developer Network (MSDN), the Volume Licensing Service Center (VLSC), and the Microsoft Partner Network (MPN).

Note You should avoid creating your own slipstream versions because of a change in the package layout that was introduced with the March 2013 product update.

This Article Applies to
  • Microsoft SharePoint Foundation 2013
  • Windows Server 2012 R2 Datacenter
  • Windows Server 2012 R2 Essentials
  • Windows Server 2012 R2 Foundation
  • Windows Server 2012 R2 Preview
  • Windows Server 2012 R2 Standard

Keywords:
KB2891274

Ref : Support Microsoft

WINDOWS SERVER 2012 AND R2 (FEATURES)

Features includes

Installation options
Unlike its predecessor, Windows Server 2012 can switch between “Server Core” and “Server with a GUI” installation options without a full reinstallation. Server Core – an option with a command-line interface only – is now the recommended configuration. There is also a third installation option that allows some GUI elements such as MMC and Server Manager to run, but without the normal desktop, shell or default programs like File Explorer.

User interface
Server Manager has been redesigned with an emphasis on easing management of multiple servers. The operating system, like Windows 8, uses the Metro-based user interface unless installed in Server Core mode. Windows Store is available in this version of Windows but is not installed by default. Windows PowerShell in this version has over 2300 commandlets, compared to around 200 in Windows Server 2008 R2.

Task Manager
Windows Server 2012 includes a new version of Windows Task Manager together with the old version.In the new version the tabs are hidden by default showing applications only. In the new Processes tab, the processes are displayed in varying shades of yellow, with darker shades representing heavier resource use. It lists application names and status, as well as CPU, memory, hard disk and network utilization. The process information found in the older versions are now moved to the new Details tab. The Performance tab shows “CPU”, “Memory”, “Disk”, “Wi-Fi” and “Ethernet” graphs. The CPU tab no longer displays individual graphs for every logical processor on the system by default; instead, it can display data for each NUMA node. When displaying data for each logical processor for machines with more than 64 logical processors, the CPU tab now displays simple utilization percentages on heat-mapping tiles. The color used for these heat maps is blue, with darker shades again indicating heavier utilization. Hovering the cursor over any logical processor’s data now shows the NUMA node of that processor and its ID, if applicable. Additionally, a new Startup tab has been added that lists startup applications, however this tab does not exist in Windows Server 2012. The new task manager recognizes when a Windows Store app has the “Suspended” status.

IP address management (IPAM)
Windows Server 2012 has an IP address management role for discovering, monitoring, auditing, and managing the IP address space used on a corporate network. The IPAM is used for the management and monitoring of Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) servers. Both IPv4 and IPv6 are fully supported.

Active Directory
Windows Server 2012 has a number of changes to Active Directory from the version shipped with Windows Server 2008 R2. The Active Directory Domain Services installation wizard has been replaced by a new section in Server Manager, and a GUI has been added to the Active Directory Recycle Bin. Multiple password policies can be set in the same domain. Active Directory in Windows Server 2012 is now aware of any changes resulting from virtualization, and virtualized domain controllers can be safely cloned. Upgrades of the domain functional level to Windows Server 2012 are simplified; it can be performed entirely in Server Manager. Active Directory Federation Services is no longer required to be downloaded when installed as a role, and claims which can be used by the Active Directory Federation Services have been introduced into the Kerberos token. Windows Powershell commands used by Active Directory Administrative Center can be viewed in a “Powershell History Viewer”.

Hyper-V
Windows Server 2012, along with Windows 8, includes a new version of Hyper-V, as presented at the Microsoft BUILD event. Many new features have been added to Hyper-V, including network virtualization, multi-tenancy, storage resource pools, cross-premise connectivity, and cloud backup. Additionally, many of the former restrictions on resource consumption have been greatly lifted. Each virtual machine in this version of Hyper-V can access up to 64 virtual processors, up to 1 terabyte of memory, and up to 64 terabytes of virtual disk space per virtual hard disk (using a new .vhdx format). Up to 1024 virtual machines can be active per host, and up to 8000 can be active per failover cluster. SLAT is a required processor feature for Hyper-V on Windows 8, while for Windows Server 2012 it is only required for the supplementary RemoteFX role.

ReFS
Resilient File System (ReFS), codenamed “Protogon”, is a new file system in Windows Server 2012 initially intended for file servers that improves on NTFS in some respects. Major new features of ReFS include:

Improved reliability for on-disk structures
ReFS uses B+ trees for all on-disk structures including metadata and file data. Metadata and file data are organized into tables similar to a relational database. The file size, number of files in a folder, total volume size and number of folders in a volume are limited by 64-bit numbers; as a result ReFS supports a maximum file size of 16 Exabytes, a maximum of 18.4 × 1018 folders and a maximum volume size of 1 Yottabyte (with 64 KB clusters) which allows large scalability with no practical limits on file and folder size (hardware restrictions still apply). Free space is counted by a hierarchical allocator which includes three separate tables for large, medium, and small chunks. File names and file paths are each limited to a 32 KB Unicode text string.

Built-in resilience
ReFS employs an allocation-on-write update strategy for metadata, which allocates new chunks for every update transaction and uses large IO batches. All ReFS metadata has built-in 64-bit checksums which are stored independently. The file data can have an optional checksum in a separate “integrity stream”, in which case the file update strategy also implements allocation-on-write; this is controlled by a new “integrity” attribute applicable to both files and directories. If nevertheless file data or metadata becomes corrupt, the file can be deleted without taking down the whole volume offline for maintenance, then restored from the backup. As a result of built-in resiliency, administrators do not need to periodically run error-checking tools such as CHKDSK when using ReFS.

Compatibility with existing APIs and technologies
ReFS does not require new system APIs and most file system filters continue to work with ReFS volumes. ReFS supports many existing Windows and NTFS features such as BitLocker encryption, Access Control Lists, USN Journal, change notifications, symbolic links, junction points, mount points, reparse points, volume snapshots, file IDs, and oplock. ReFS seamlessly integrates with Storage Spaces, a storage virtualization layer that allows data mirroring and striping, as well as sharing storage pools between machines. ReFS resiliency features enhance the mirroring feature provided by Storage Spaces and can detect whether any mirrored copies of files become corrupt using background data scrubbing process, which periodically reads all mirror copies and verifies their checksums then replaces bad copies with good ones.
Some NTFS features are not supported in ReFS, including named streams, object IDs, short names, file compression, file level encryption (EFS), user data transactions, hard links, extended attributes, and disk quotas. Sparse files was not supported by Preview, but it is supported by RTM. ReFS does not itself offer data deduplication. Dynamic disks with mirrored or striped volumes are replaced with mirrored or striped storage pools provided by Storage Spaces. However, in Windows Server 2012, automated error-correction is only supported on mirrored spaces, and booting from ReFS is not supported either.

IIS 8.0
Windows Server 2012 includes version 8.0 of Internet Information Services (IIS). The new version contains new features such as SNI, CPU usage caps for particular websites, centralized management of SSL certificates, WebSocket support and improved support for NUMA, but few other substantial changes were made.

Also View :

Windows Server 2012 and R2 (History)

Some History for Windows Server 2012, codenamed “Windows Server 8”, is the sixth release of Windows Server family of operating systems developed concurrently with Windows 8. It was not until April 17, 2012 that the company announced that the final product name would be “Windows Server 2012”.

Microsoft introduced Windows Server 2012 and its developer preview in the BUILD 2011 conference on September 9, 2011. However, unlike Windows 8, the developer preview of Windows Server 2012 was only made available to MSDN subscribers. It included a graphical user interface (GUI) based on Metro design language and a new Server Manager, a graphical application used for server management. On February 16, 2012, Microsoft released an update for developer preview build that extended its expiry date from April 8, 2012 to January 15, 2013.

Before Windows Server 2012 was finalized, two test builds were made public. A public beta version of Windows Server 2012 was released along with the Windows 8 Consumer Preview on February 29, 2012. The release candidate of Windows Server 2012 was released on May 31, 2012, along with the Windows 8 Release Preview.

The product was released to manufacturing on August 1, 2012 and became generally available on September 4, 2012. However, not all editions of Windows Server 2012 were released at the same time. Windows Server 2012 Essentials was released to manufacturing on October 9, 2012 and was made generally available on November 1, 2012. As of September 23, 2012, all students subscribed to DreamSpark program can download Windows Server 2012 Standard or Datacenter free of charge.

Also View :

Cannot view list in Datasheet View

I recently had to install Office 2010 64bit on my computer to work with some extremely large Excel spreadsheets. I noticed today that when I tried to open one of the SharePoint list in datasheet view, it came up with the following error:

The list cannot be displayed in Datasheet view for one or more of the following reasons: A datasheet component compatible with Windows SharePoint Services is not installed, your browser does not support ActiveX controls, or support for ActiveX controls is disabled

This is a known compatibility issue between Office 2010 64bit and SharePoint. Microsoft has a workaround for this issue.

Install KB2266203 from Microsoft.

http://support.microsoft.com/kb/2266203

After installing the fix, the problem was resolved immediately.