Add Fibre Channel LUN to Server 2012 R2

I'm having difficulty configuring SAN storage attached to a pair of 2012 R2 hosts. I'm building a two node Hyper-V cluster. Bear in mind this is an operation that I'm very familiar with using VMware. I'm simply trying to get the windows
hosts to see the LUN so that I can configure it as shared disk in the Hyper-V cluster. This is IBM System x3850 storage. The host each have Emulex LPe 12000-M8 HBAs. Also, I'm pretty sure that the disk is visible from the HBAs in the OneCommand
utility. <see below>
I've tried to run the mpclaim -e command and it returns "There is no enterprise storage connected on the system"
What am I not doing? MPIO? I've tried adding a device using the 8x16 rule "IBM 5639 "
I can't find any documentation that explains how to do this in server 2012 R2 ANYWHERE!!!! I'm pulling my hair out and I don't have that much to lose!! :)
Please help!
Thank you,
Roger

Again, this is not a Windows issue. I am not familiar with the IBM utility, so I don't know what that is showing. I just know that critical to accessing Fibre Channel LUNs is that you have your SAN network zoned to allow the WWPN from your
HBA to talk to the WWPN of the Fibre Channel controllers, and then on the controller you need to mask the LUN to expose it to the WWN of your server. If that is not done, Windows will not see anything. Once it is done, Windows sees the disk as it if were a
local disk.
I do see that you have two HBAs, and some of the WWN information seems to be duplicated. Most likely you are trying to configure some form of MPIO. I am assuming that is something provided by the IBM software, but it must be working properly
otherwise, once the zone/mask is correct, you will see each LUN two or more times, depending upon your Fibre configuration.
. : | : . : | : . tim

Similar Messages

To add fibre-channel LUNs on the fly

I added a new LUN from my SAN and ran "rescan-scsi-bus.sh" on my OVM Server.
After that,
My "fdisk -l" hangs.
At the GUI, I'm able to see the new LUN and somehow its status is locked.
Even though I tried rebooting the OVM Server, it remains locked.
Did I miss any step or did I go through the right step to add a new Fibre Channel LUN dynamically?
Thanks in advance.
- Young

Hi Snehangshu,
It's still locked even after running those commands.
When I log into the OVM Server, it displays the following warning message as well.
Warning: making manual modifications in the management domain
might cause inconsistencies between Oracle VM Manager and the server.
Even with another reboot, it didn't make a difference.
I guess the most of people use NAS or iSCSI over FCP with OVM 3?
Thanks.
- Young

Unable to add replication feature in sql server 2012 web edition

Hi All,
We are using SQL Server 2012, Web edition and when it was installed replication is not an added feature so I tried to add this feature but getting below error.
Error: There are no SQL Server instances or shared features that can be updated on this computer.
Description: The version of SQL Server instance MSSQLSERVER does not match the version expected by the SQL Server update. The installed SQL Server product version is 11.1.3000.0, and the expected SQL Server version is 11.0.2100.60
And also please let me know how to identify the default file location of the setup file 'setup.exe' for SQL Server 2012 (Webedition, 64bit) Grateful to your time and support.
I'm using "C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Update Cache\KB2777772\QFE\setup.exe" to add replication feature, please correct me if I'm wrong.
Thank You.
Regards,
Kalyan
----Learners Curiosity Never Ends----

It looks like you are trying to add Replication Components, however, you are using the Cumulative update package 5 setup, which is wrong.
Note that you will not find the setup file for SQL Server on your file system, it will be on your installation media.
To install SQL Server Replication Components, locate your installation media and run Setup.exe. Select the add features to an existing instance option, select your instance, and add replication components.
Brandon Williams (blog |
linkedin)

Unable to add network printers from Windows Server 2012 R2 to client running Windows 7 Pro x64

New Windows Server 2012 R2 Standard in the environment. Added print services to it and added five HP printers to it and shared them. Also deployed the printers via group policy.
Clients are running Windows 7 Pro x64. The group policy fails to install the printers (error 0x00000002). We get the same error when trying to manually add the printer from the client side.
From Event Viewer: Group Policy was unable to add per computer connection <<printer share>>. Error code 0x2. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.
Any ideas on troubleshooting this?
Thanks.
-John

John,
You might try playing with the HP universal driver, that might help you. Try installing a new shared printer on the server using the universal print driver, then try and connect to it to see if it is any better.
Check these GPO settings to ensure local machines can install the drivers.
1. Configure the following two Group Policy settings:
Computer Configuration\Policies\Administrative Templates\System\Driver Installation\Allow non-administrators to install drivers for these devices setup classesEnabled
2. Device class GUID of printers: {4d36e979-e325-11ce-bfc1-08002be10318}
Computer Configuration/Policies/Administrative Templates/Printers/Point and Print RestrictionsEnabled
Security Prompts: When Installing Drivers for a new connection = Do not show warning or elevation prompt
This article might help you out also:
http://www.eversity.nl/blog/2012/09/windows-cannot-connect-to-the-printer-operation-failed-with-error-0x00000002/
Cheers,
Curt Winter
Certified Microsoft Professional
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied. If you found my post helpful, please mark it as the answer.

What is the maximum number of Fibre Channel LUNS visibile in Solaris 11.2

I have SPARC T4-4's with 4 emulex HBA ports. What is the maximum number of LUNS I can have exported to that server?

Hi Jim,
MOS doc 1018739.1 describes maximum Solaris SCSI and FC targets, LUNs, and device instances.
The FC limit for maximum LUNs is either 65535 or unlimited.
Thanks, Cindy

Downgrade Windows server 2012 64 bit to windows server 2008 R2 32 bit

HI,
what I want to know is when Downgrading Windows server 2012 64 bit to windows server 2008 R2 32 bit, will there be any issues of the license? Can I use the same license of 2012 server for the new 2008 installation.

Hi,
Based on my experience, we cannot use the Windows Server 2012 license key to activate a Windows Server 2008 install.
In addition, which channel the windows server 2012 was purchased through? It seems that the media and product keys to downgrade are not provided although downgrade rights are granted
since Microsoft only supplies bits and product keys to Volume License customers and only for certain versions and editions of the software.
I recommend you to contact the Licensing Activation Centers below for assistance:
http://www.microsoft.com/licensing/existing-customers/activation-centers.aspx
Best regards,
Susie

How to obtain target WWN for a LUN On Windows 2012 R2 Hyper-V with Fibre Channel SAN

I have a large collection of Hyper-V hosts for which I would like to retrieve the target WNN and LUN ID for the LUNs visible on each host. By target WWN I mean the storage array's WWN.
I have tried using the root\wmi namespace to retrieve MS_SMHBA_PORT_LUN instances, but I get 0 instances back.
I get instances of MSFC_FibrePortHBAAttributes back, but those only tell me the local host's HBA WWN, not the target information.
This information must be stored somewhere, because you can't access the LUN without it, I hope there is a way to retrieve it. Is there? Or is it write only during LUN setup?

Hi,
Have you checked these two postings:
http://terrytlslau.tls1.cc/2011/08/how-to-find-world-wide-name-wwn-in.html
http://pkjayan.wordpress.com/2011/08/17/world-wide-name-wwn-for-a-fibre-channel-hba-on-windows-server/
You need the FCINFO tool, which you can get from:
http://www.microsoft.com/en-us/download/details.aspx?id=17530
Cheers
Andrew

Passing LUN through Virtual HBAs on Server 2012 R2

i have two Hyper-V hosts running Server 2012 R2 connected to a Fibre Channel SAN with an EMC back end. I am at the point where I have configured the zoning and can see the LUNs on the Hyper-V nodes using virtual HBA initiators. However, I cannot
find any way to pass the LUNs through to the Virtual Machines running Server 208 R2. If I used the method of a shared SCSI controller I don't see the pint of the Virtual HBAs.
Needless to say, the Virtual OS does not see any LUNs at this point.
PC_Doctor

First, you must be sure that your HBA vendor supports virtual fibre channel - not all vendors do.
Configuring vHBAs for VMs is just like configuring HBAs on the physical hosts - only twice as much work. You have to zone and mask for the individual VMs, just like you zone and mask for the physical hosts. Except the VMs have twice as many WWNs
as the hosts because they need it for live migration to work.
If you search TechNet you will find blogs and design guides that can assist in setting this up.
"I don't see the pint of the Virtual HBAs."
For the most part I agree with you. In a Microsoft environment, there are very few cases where vHBAs make sense (imo). Before Windows Server 2012 with Hyper-V customers asked for vHBAs because VMware had that as a method for sharing volumes between
a pair of nodes to enable failover clustering. Also, early on, there were performance benefits to be realized by going directly to physical storage rather than using virtual disks that resided on physical storage.
2012 changed all that. Yes, it introduced vHBA, but R2 also introduced shared VHDX. 2012 also significantly improved virtual disk performance to the point where the difference between physical and virtual is not noticeable in almost all
cases.
Shared VHDX is much, much easier to implement and manage than is vHBA. It requires a box to be checked to enable sharing. vHBA requires two sets of zones/masks for each VM compared to one set for a physical server.
Shared VHDX allows for complete hardware independence. In other words, because all storage is virtual, the VM can be moved to any other platform. vHBA locks you to a specific hardware configuration. You are tied to the storage array addressed
by the WWNs.
Bottom line for me is that learning to use vHBA is an interesting exercise (which I did perform), but I have yet to run across a situation where I would opt to use vHBA instead of shared VHDX.
. : | : . : | : . tim

HYPER-V 2012 R2 - EVA 4400 - Guest Centos 7 Virtual Fibre Channel

Dear colleagues,
We can't connect EVA4400 LUN's to virtual Guest Machine Centos 7 through virtual Fibre Channel. On the same configuration Guest Machine with Windows 2012 R2 works normally.
[root@lstst log]# lsmod | grep hv_
hv_utils               18357 0
hv_netvsc              31253 0
hv_storvsc             21881 2
hv_vmbus              183547 6 hyperv_keyboard,hv_netvsc,hid_hyperv,hv_utils,hyperv_fb,hv_storvsc
[root@lstst log]# lsscsi -ll
[2:0:0:0]    disk    Msft     Virtual Disk     1.0   /dev/sda
state=running queue_depth=200 scsi_level=5 type=0 device_blocked=0 timeout=180
iocounterbits=32 iodone_cnt=0x1405 ioerr_cnt=0x0 iorequest_cnt=0x1405
queue_type=simple
[3:0:0:0]    disk                                    /dev/sdb
state=running queue_depth=200 scsi_level=0 type=0 device_blocked=0 timeout=180
iocounterbits=32 iodone_cnt=0x2a ioerr_cnt=0x0 iorequest_cnt=0x2a
queue_type=simple
[3:0:0:1]    disk                                    /dev/sdc
state=running queue_depth=200 scsi_level=0 type=0 device_blocked=0 timeout=180
iocounterbits=32 iodone_cnt=0x29 ioerr_cnt=0x0 iorequest_cnt=0x29
queue_type=simple
[4:0:0:0]    disk                                    /dev/sdd
state=running queue_depth=200 scsi_level=0 type=0 device_blocked=0 timeout=180
iocounterbits=32 iodone_cnt=0x28 ioerr_cnt=0x0 iorequest_cnt=0x28
queue_type=simple
[4:0:0:1]    disk                                    /dev/sde
state=running queue_depth=200 scsi_level=0 type=0 device_blocked=0 timeout=180
iocounterbits=32 iodone_cnt=0x28 ioerr_cnt=0x0 iorequest_cnt=0x28
queue_type=simple
[root@lstst log]# cat /proc/scsi/scsi
Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: Msft     Model: Virtual Disk     Rev: 1.0
Type:   Direct-Access                    ANSI SCSI revision: 04
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor:          Model:                  Rev:
Type:   Direct-Access                    ANSI SCSI revision: 00
Host: scsi3 Channel: 00 Id: 00 Lun: 01
Vendor:          Model:                  Rev:
Type:   Direct-Access                    ANSI SCSI revision: 00
Host: scsi4 Channel: 00 Id: 00 Lun: 00
Vendor:          Model:                  Rev:
Type:   Direct-Access                    ANSI SCSI revision: 00
Host: scsi4 Channel: 00 Id: 00 Lun: 01
Vendor:          Model:                  Rev:
Type:   Direct-Access                    ANSI SCSI revision: 00
dmesg
[ 205.580687] hv_storvsc vmbus_0_6: cmd 0x28 scsi status 0x0 srb status 0x22
[ 205.585931] hv_storvsc vmbus_0_6: cmd 0x28 scsi status 0x0 srb status 0x22
[ 205.591237] hv_storvsc vmbus_0_5: cmd 0x28 scsi status 0x0 srb status 0x22
[ 205.591733] hv_storvsc vmbus_0_5: cmd 0x28 scsi status 0x0 srb status 0x22

[root@lstst ~]# fdisk -l
Disk /dev/sda: 42.9 GB, 42949672960 bytes, 83886080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x0000e8e7
   Device Boot      Start         End      Blocks   Id System
/dev/sda1   *        2048     1026047      512000   83 Linux
/dev/sda2         1026048    83886079    41430016   8e Linux LVM
Disk /dev/sdb: 0 MB, 512 bytes, 1 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sdc: 0 MB, 512 bytes, 1 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sde: 0 MB, 512 bytes, 1 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sdd: 0 MB, 512 bytes, 1 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/centos-swap: 4177 MB, 4177526784 bytes, 8159232 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/centos-root: 38.2 GB, 38243663872 bytes, 74694656 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Unable to add File Server Resource Manager Tools on Windows Server 2012 - Errors on restart and roll back install

Unable to install Windows Server 2012 Feature - [Tools] File Server Resource Manager Tools.
Installs, however when I restart the server error messages appears saying feature unable to install, windows reverting changes.
In the Setup event logs have the following information message "Update FSRM-Infrastructure of package FSRM-All failed to be turned on. Status: 0x800f0922"
Does anyone have any idea's on why this Feature can not be installed ??
Scott

Hi Shaun
Tried both of your suggestions, however neither strategy worked.
Strategy 1
Tried installing via powershell - "install-windowsfeature -name fs-resource-manager -includemanagementtools"
Feature un-installed itself during the restart.
Attempted to use the command "DISM /online /remove-feature /featurename:FSRM-Infrastructure-Services". However
this did work because one the Service was'nt installed or two because there was no command option for "/remove-feature"
PACKAGE SERVICING COMMANDS:
/Add-Package - Adds packages to the image.
/Remove-Package - Removes packages from the image.
/Enable-Feature - Enables a specific feature in the image.
/Disable-Feature - Disables a specific feature in the image.
/Get-Packages - Displays information about all packages in the image.
/Get-PackageInfo - Displays information about a specific package.
/Get-Features - Displays information about all features in a package.
/Get-FeatureInfo - Displays information about a specific feature.
/Cleanup-Image - Performs cleanup and recovery operations on the image.
Strategy 2
Tried installing via powershell, using the following command DISM
/online /enable-feature /featurename:FSRM-Infrastructure-Services, however got the same result, the install backed out during the restart.
All up back to where I started?

Office 2013 over Windows Server 2012 RDP World Add-On Macro/Template Error

I have a new Windows Server 2012 Remote Desktop environment for about ten users (not R2) with the latest Office 2013 Pro installed.
The users all have an add-on word template in Word for Office 2013. That add-on was installed as administrator and ONLY works as administrator.
When any other user (even if they are local administrators, domain admins, etc.) opens Word, they are immediately prompted with the following message:
"Could not load some objects because they are not available on this machine."
If a user "runs as administrator" it runs fine. Obviously, I don't want that. I have been searching and searching and thought maybe there was a group policy or Office setting someone may know that I just can't find.
Any help would be awesome! Thank you.

Hi,
Once you login with the user account which is not getting access, try the below steps and check if it helps fix the issue:
Click on start->control panel->programs and features->right click on the Office 2013 program->click on change->add or remove features-> click on the drop down arrow which is before the Microsoft Office->click on Run all from my computer->Continue.
Once completed restart the computer and then open to check if the issue occurs.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

[SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

Hi there!
I have a problem which makes me very angry already :)
I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
LOGS on the second nodes:
Application Log
"Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
Failover Clustering Diagnostic Log
"[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
CMDLET Error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:06:21
MSC-CO-EXC-02V
Failed
Error:
A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
(MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
This operation returned because the timeout period expired
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
Warning:
Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
Elapsed Time: 00:06:21
UPD:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.
Please, help me if you can.

Hi, Jared! Thank you for the reply.
Of course I did it already :) I have new info:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.

Can't add drivers to Server 2012 R2 boot image in WDS

Hi all.
I want to use my "old" Windows Server 2012 (not R2), WDS to deploy new R2 servers but i can't add driver package to the R2 boot image, it comes out with error code: 0xc0000135 no matter what drivers i use.
Without network drivers i can't boot the image on my physical servers, i've tried on a virtual machine where it works just fine.
I can't use the old boot image to install R2, then it comes with error: "Windows could not apply unattend settings during pass [offlineServicing]." when it tries to install it on both virtual and physical servers.
My initial thought is that the WDS server has to be on a R2 server but i can't find anything that proofs that.
Can someone confirm that non R2 WDS is not supported to R2 or does anyone have an idea to a solution?
Thank you in advance.

Okay maybe not a solution but i installed a new WDS server on R2 and then there was no problem adding driver package to to boot image.
So i was able to confirm my theory that it's not supported to deploy R2 from a non-R2 WDS server. If anyone can make it work please let me know but until then i think this is the only way.
If I understand your description of the issue, the problem is that you are trying to update a WinPE 5.0 WIM with a version of the ADK that services WinPE 4.0 images. Installing the new Windows Server 2012 R2 server caused SCCM to use the version of the
ADK that services WinPE 5.0 images. You should be able to deploy them fine from the other server, but you can only service them from the new one. You will not be able to service the older WinPE 4.0 images from the new server either.

EM12c: Add Target SQL Server 2012 Fails

EM12c: Add Target SQL Server 2012 Fails
Configuration:
EM12c platform:
Oracle Enterprise Linux 6.2(x86_64)
Oracle Enterprise Database 11.2.0.3 (x86_64)
Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) (x86_64)
Microsoft SQL Server Plug-In 12.1.0.2.0 deployed in the Management Server
Target:
Windows Server 2008 R2 Enterprise Edition SP1 (64-bit)
SQL Server 2012 (Enterprise Edition) (64-bit)
Microsoft SQL Server Plug-In 12.1.0.2.0 deployed in the Management Agent
Problem: EM12c fails to add a SQL Server 2012 instance.
Target Name: mssql_mcsdbsqlsrv2.esri.com
Target Type: Microsoft SQL Server
Agent: https://mcsdbsqlsrv2.esri.com:3872/emd/main/
* JDBC URL (Example : jdbc:sqlserver://<host>:<port>): jdbc:sqlserver://mcsdbsqlsrv2.esri.com:1433
JDBC Driver (Optional): com.microsoft.sqlserver.jdbc.SQLServerDriver
Database Username (Required for SQL Authentication): sa
Password of Database User (Required for SQL Authentication): ****
System Username (Needed when SQLServer is at remote location):
System Password (Needed when SQLServer is at remote location):
Connect Using Windows Integrated Authentication (Yes/No): No
Role (Optional):
Error:
MSSQLDetermineName_DynamicProperty;em_error=Could not connect. Error code = 0x8004100e
em_error=Failed while connecting to WMI.
Response;Can't resolve a non-optional query descriptor property [provided_sql_server_name] (ms_sqlserver_servername)
The sa login is enabled and I can connect from a remote machine to the MSSQL 2012 server using SQL Server Management Studio.
I have also added several default MSSQL 2008 instances to EM12c successfull.
I've installed the latest "Microsoft SQL Server Plug-In 12.1.0.2.0" in EM12c and deployed it to the target agent in the MSSQL 2012 machine
Does EM12c (12.1.0.1) support MSSQL 2012?
Thanks,
Marcelo Marques
Technical Manager, Esri
Edited by: Marcelo Marques - ESRI on Sep 26, 2012 9:12 AM
Edited by: Marcelo Marques - ESRI on Sep 26, 2012 9:13 AM

Hello All,
What is the latest information on MSSQL 2012 support on EM12c as a supported Target Deployment?
Thanks
Jan S.

Cannot Add File Share to (any) File Server Role of a Cluster in Windows Server 2012

Cannot Add File Share to (any) File Server Role of a Cluster in Windows Server 2012...
Get this message in the Operational Log in "FileServices-ServerManager-EventProvider" section of MS-Windows Eventlogs:
Exception: Caught exception Microsoft.Management.Infrastructure.CimException: The xsi:type attribute (MSCluster_Property_Resource_Network_Name) does not identify an existing class.
   at Microsoft.Management.Infrastructure.Internal.Operations.CimSyncEnumeratorBase`1.MoveNext(Boolean discardResultsAndErrors)
   at Microsoft.Management.Infrastructure.Internal.Operations.CimSyncEnumeratorBase`1.MoveNext()
   at Microsoft.FileServer.Management.Plugin.Services.FSCimSession.PerformQuery(String cimNamespace, String queryString)
   at Microsoft.FileServer.Management.Plugin.Services.ClusterEnumerator.BuildNodes(ICimSession session, ClusterRole scopeType, String query, IDictionary`2 groupNameToTypeMap)
   at Microsoft.FileServer.Management.Plugin.Services.ClusterEnumerator.GetClusterClientAccessPointNames(ICimSession session, IDictionary`2 groupNameToTypeMap)
   at Microsoft.FileServer.Management.Plugin.Services.ClusterEnumerator.RetrieveClusterConnections(ComputerName serverName, ClusterMemberTypes memberTypeToQuery)
Thanks for help...(everything else works fine in other type of cluster roles).
Thomas.

This issue also happens in fresh Windows 2012R2 installations, not just upgrades from 2008R2!
I have the issue where I cannot modify any settings on SMB shares. Here is the stacktrace. It appears to be WMI related.
Error: ERROR: Task 'TEST.xxxxxxx.COM-ClusterStorage$-SmbShareUpdate-46bcabf6-1dd4-4a48-a525-5e5d374596c7' has failed: Microsoft.FileServer.Management.Plugin.FSACException: Error occurred while updating an SMB share: The requested operation is not supported.
---> Microsoft.Management.Infrastructure.CimException: The requested operation is not supported.
   at Microsoft.Management.Infrastructure.Internal.Operations.CimSyncEnumeratorBase`1.MoveNext()
   at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)
   at Microsoft.Management.Infrastructure.CimSession.ModifyInstance(String namespaceName, CimInstance instance, CimOperationOptions options)
   at Microsoft.FileServer.Management.Plugin.Services.FSCimSession.ModifyInstance(ICimInstance instance)
   at Microsoft.FileServer.Management.Plugin.Services.FSCimSession.ModifyInstance(ICimInstance instance, IEnumerable`1 propertiesWithKeys)
   at Microsoft.FileServer.Management.Plugin.Providers.WmiUpdateTaskBase.DoUpdateInstance(ICimSession session, ICimInstance instance)
   at Microsoft.FileServer.Management.Plugin.Providers.WmiUpdateTaskBase.DoWork(Object sender, DoWorkEventArgs e)
   --- End of inner exception stack trace ---
   at Microsoft.FileServer.Management.Plugin.Providers.WmiUpdateTaskBase.DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

Add Fibre Channel LUN to Server 2012 R2

Similar Messages

Maybe you are looking for