ISCSI Target Issues

I am running MS Server 2012 and am only using this as a iscsi target server. I run VMware vspher 5.5 as the initiator. So every night around 12:30 am, my server restarts many of the services, one of them being the iscsi target service. No
errors are produced, just informational logs about the services stopping and starting again. However, when they stop my vphere client and vm's on the iscsi target lose connection. I just want them to run all the time, these are production systems.
When I come in the next day I just do a refresh on the iscsi target gui and everything reconnects. Then I have to go to the vsphere client and answer the guest question about why they lost contact with the targets and the vm's all restart without
a problem. Does anyone know about this problem and how to resolve it?

No, but I think 2012 has built in virus checker, I'll check that. Nope, but this is the info log published.
At 12:31 I got "The Microsoft iSCSI Software Target service entered the stopped state." Then when I came in this morning and hit refresh at 6:01 I got "The Microsoft iSCSI Software Target
service entered the running state.". Both were the event id below. Sometimes it puts it back in the running state automatically, but sometimes I have to manually do it, either way, when it goes into stopped state my vsphere client makes me
answer the "guest" question to bring it back live in the vmware client side. Checked antivirus, no problems there. Again, these are not errors, they a re calling these basic service operations as shown below. How can shutting down
productions systems be a normal operation, must be some way around that or who would want to use this. The nice thing is how easy it is to set up a target, but this is a problem. People use are systems around the clock sooo...any other thoughts?
Event ID 7036 — Basic Service Operations
73 out of 202 rated this helpful - Rate this topic
Updated: December 11, 2007
Applies To: Windows Server 2008
green
Service Control Manager transmits control requests to running services and driver services. It also maintains status information about those services, and reports configuration changes and state changes.
Event Details
Product: Windows Operating System
ID: 7036
Source: Service Control Manager
Version: 6.0
Symbolic Name: EVENT_SERVICE_STATUS_SUCCESS
Message: The %1 service entered the %2 state.
Resolve
This is a normal condition. No further action is required.
Related Management Information
Basic Service Operations
Core Operating System
So how c

Similar Messages

Reg reboot issue - console message- svc:/network/iscsi/target:default: Method or service exit timed out

Hi,
When I reboot the system I am seeing this message on the console and system is not getting rebooted.
svc.startd[10]: svc:/network/iscsi/target:default: Method or service exit timed out. Killing contract 131.
can someone help me to solve this?

There are still a few issues with Solaris 11.1 and iSCSI LUN and rebooting. I know they are working on fixes.
A possible workaround is to use the reboot command and NOT the init command. At least when you use the reboot the command the system will reboot and not hang.
If this is not your problem then it may be a different problem.
Andrew

ISCSI-Target service start issue

I am trying to configure 11g RAC on RHEL 4.7. I have just done following steps on my storage:
[root@XRBSstorage ~]# rpmbuild rebuild iscsitarget0.4.126.src.rpm
[root@XRBSstorage ~]# rpm ivh /usr/src/redhat/RPMS/i386/iscsitarget*
Preparing... ########################################### [100%]
1:iscsitargetkernel########################################### [ 33%]
2:iscsitarget ########################################### [ 67%]
3:iscsitargetdebuginfo########################################### [100%]
[root@XRBSstorage ~]#vi /etc/ietd.conf
Target iqn.2001-04.:XRBSstorage.sda6
Lun 0 Path=/dev/sda6,Type=fileio
Alias sda6
[root@XRBSstorage ~]# chkconfig --level 35 iscsitarget on
[root@XRBSstorage ~]# service iscsi-target start
Starting iSCSI target service: FATAL: Module iscsi_trgt not found.
netlink fd
: Connection refused
[FAILED]
[root@XRBSstorage ~]#
Kindly guide me how to get rid of the error.
Regards,
Umair

This is the wrong forum for that kind of questions. Please move to Generice Linux forum.
Anyway, check if all kernel module are loaded:
[root@srv01 ~]# lsmod |grep -i iscsi
be2iscsi               50665 0
iscsi_tcp               9524 0
libiscsi_tcp           15026 3 iscsi_tcp,cxgb3i,libcxgbi
libiscsi               39373 7 be2iscsi,ib_iser,iscsi_tcp,bnx2i,cxgb3i,libcxgbi,libiscsi_tcp
scsi_transport_iscsi    35096 8 be2iscsi,ib_iser,iscsi_tcp,bnx2i,libcxgbi,libiscsiRegards,
- wiZ

Error when trying to install the iSCSI target - Cannot find the Windows PowerShell data file 'ImportExportIscsiTargetConfiguration.psd1'

Hi,
I'm just attempting to setup an iSCSI target on a freshly installed Windows 2012r2 box, but I get the following error when attempting to Create and iSCSI virtual disk via the wizard after a successful
installation of the iSCSI target role.
The full error is:
Cannot find the Windows PowerShell data file 'ImportExportIscsiTargetConfiguration.psd1' in directory 'C:\Windows\System32\WindowsPowerShell\v1.0\Modules\IscsiTarget\en-GB\', or in any parent culture.
I tried to uninstall, then reinstall the role but no go.
The Server Locale and UI was all updated to en-GB but this folder does not appear to exist in this location. Rather, the folder I can see is:
'C:\Windows\System32\WindowsPowerShell\v1.0\Modules\IscsiTarget\en-US\'
I'm going to attempt to copy the 'en-US' folder to 'en-GB' to see what happens, but I would like to know why this has occurred in the first place? Other roles have installed (such as AD DS AD CS and
IIS) on other machines with no issue.
Many thanks
Chris
Chris

Hi Chris,
The error "Cannot find the Windows PowerShell data file 'ImportExportIscsiTargetConfiguration.psd1'" occured, because the file 'ImportExportIscsiTargetConfiguration.psd1' can't be loaded under the folder en-GB with current culture.
I recommend you can copy this .psd1 file under 'C:\Windows\System32\WindowsPowerShell\v1.0\Modules\IscsiTarget'. Essentially if PowerShell can’t find the specified data file for the current culture it will “fallback” to the top-level data
file in this case.
For more detailed information, please refer to this article:
Windows PowerShell 2.0 String Localization
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
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]

Server 2012 R2 iSCSI Target - Multiple targets per iSCSI Virtual Disk with CHAP

Scenario I am trying to achieve is this:
Windows Server 2012 R2 serves as iSCSI Target configured to have 1 iSCSI Virtual Disk
2 Hyper-V servers connecting to this target with iSCSI Inistator and have multiple targets for that iSCSI Virtual Disk using CHAP
**These 2 are nodes in fail over cluster, this iSCSI is added as a CSV.
Issue that I have, is that you can only have 1 target per iSCSI Virtual Disk
Both Hyper-V servers can connect to this LUN without issue when I add both initiator IDs to the target, but once I enable CHAP, you can only put one initiator ID in the "Name" field, so I can only connect from 1 Hyper-V server.
Do you know of a way around this?

From my understanding, "chaptest" is a single target, my goal was to make 2 targets to the same iSCSI virtual disk.
So if you were to right click the iSCSI virtual disk that "chaptest" is assigned to and click "Assign iSCSI Veritual Disk...", then select "New iSCSI Target, and proceed with the wizard it removes the "chaptest" target
and adds the new one just created.
My goal was to have 2 targets to 1 iSCSI VD, but seeing your screenshot, with 2 initiators connected, that goal doesn't seem needed anymore.
I was under the impression that the "User name" = the iscsi initiator IQN name, which had to be unique. That is why I thought I would need 2 targets.
Thanks

OVS servers restart when iSCSI target restarts

Long story short, I've been working on my new lab at home off and on. Tonight I was working on my lab to get to the point where I would have OVMM as a virtual machine as the dedicated host I have for temporary measures only has two gigs of ram vs the recommended 8 gigs of ram.
More to the point: I was working on the storage portion of my setup and I got my iSCSI target discovered (FreeNAS 9.3) and I was able to build my cluster of OVSs. I noticed earlier that my FreeNAS server had some pending updates and I figured it would be a good idea to perform these updates before I started using the iSCSI storage for active virtual machines. Naturally, when the updates are done on my FreeNAS server, it reboots.
What I don't understand is why both of my OVSs restarted at the same time after the FreeNAS server went down for a reboot. Was there a hidden gotcha? Did I overlook something in the documentation?
A side effect of the unexpected reboot is the fact that my OVS(2) did not come back online with OVMM and I could not ping my management interface for that OVS. I did several Google searches and tried some manual up/downs of the interfaces and tried one effort to manually configure bond0 to an IP address to try and get some sort of response. Needless to say, none of those were good ideas and didn't help. Therefore, I'm re-installing OVS on server 2 now.
If anyone has any ideas as to how I could have fixed OVS(2) I'm more than willing to take notes in case this happens again.
Thank you for any and all help,
Brendan
P.S. If this has any influence with my situation, I am running LACP bonds and all IP addresses are configured on the VLAN interfaces. I have not had any issues configuring my switch and with the exception of OVS(2) not wanting to reply after the unexpected restart I had everything working. An added gotcha is that the storage VLAN interface on OVS(2) continued to reply after the restart.

Hi Brendan,
the situation you encountered is expected for a single-headed iSCSI target. If you present OVM with a LUN - regardless if it's iSCSI or FC, OVM creates an OCFS2 volume on it, when you choose that LUN to be used as a storage repository. This is, since OCFS2 is a cluster-aware file system and thus is the only supported fs to use for a cluster setup. Now, although OVFS2 is really easy to setup - compared to other cluster file systems - it has some mechanics that will cause your nodes to fence (or reboot) in case the node looses "contact" with the OCFS2. Each node writes little keep-alive fragments onto the OCSF2 and if you reboot your iSCSI target, then this will cease and OCFS2 will fence itself, hoping for some minor glitch that may be gone after a reboot.
There are a couple of ways to achieve this with iSCSI, but their resp. setup is not easy, and the hoops to jump through are probably to many for a lab setup. E.g. I am running a two RAC nodes as iSCST targets, which in turn do have high-redundancy disk setup behind them, consiting of 3 seperate storage servers. So, in my setup I am able to survive:
- two storage node failures
- one RAC node failure (which provides the iSCSI target for my OVS)
Regarding your OVS2, as you have already re-installed OVS2, there will be now way, to tell, what went wrong with it, as you'd need access to the console to poke around a bit, while OVS2 is in that situation, where it doesn't respond to pings on it's management interface.
Cheers,
budy

Unable to connect to iSCSI target from PC

We have just installed Storage Server 2012 R2 on a disk array box with 4TB of storage. We installed and configured the iSCSI server software and created a LUN. In Server Manager > File ans Storage Services > iSCSI I see the VM-Store.fhdx file in the
iSCSI VIRTUAL DISKS pane. Below, in the iSCSI TARGETS pane i see the listing for the target.
Both show "Connected" in the Target Status column. From outside the server (on the LAN) I launched the iSCSI Initiator applet in the control panel/administrator tools. I clicked on the "Discovery" tab in the iSCSI Initiator Properties
dialog box and typed in the IP address of the Windows 2012 server. On the Targets tab it's all blank. If I manually enter the IP address in the Quick Connect box at the top and click the Quick Connect button I get a dialog that shows "No targets available
for using Quick Connect" in the status box at the bottom.
CHAP is NOT being used yet so it's not a CHAP issue. What else can I try to make this work? It's holding up a project we desperately need to get online.

Hi,
Do you mean that you get the error "No Targets available for Login using Quick Connect"? I did a test on my pc, and have the same error with you. A workaround for the issue is to enter the server name in the Quick Connect box to connect the iSCSI target.
There is a similar thread, please go through it to help troubleshoot this issue:
How to troubleshoot "No Targets available for Login using Quick Connect."
http://social.technet.microsoft.com/Forums/windowsserver/en-US/9d32b6dd-2957-4305-9818-708d80df5ca1/how-to-troubleshoot-no-targets-available-for-login-using-quick-connect?forum=winserverfiles
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

ISCSI target software for 10.5

I have looked everywhere. Does anyone know of iSCSI target software that will run on a Xserve?

I just compiled the NetBSD software iSCSI target for Mac OS X
(10.5.6), and it seems to work ok (with the GlobalSAN iSCSI
initiator).
ftp://ftp.netbsd.org/pub/pkgsrc/distfiles/netbsd-iscsi-20080207.tar.gz
You do need to set the environment variable
CFLAGS='-DPOSIX_CSOURCE'
before you do a ./configure;make
otherwise there will be a conflicting definition of uuid_t.
All I tried sharing out was a 128MB file as if it were a disk.
I have not tried sharing raw disk (or other SCSI devices) out,
no idea whether that would work (even for disk, let alone
tape or CD/DVD). The system I did this on is a Mac Mini (Intel),
but I don't see that being particularly relevant.
(and no, I'll neither provide a binary nor a tutorial in how to
set it up; if you go that route, you'll be supporting yourself
anyway, so best to teach yourself right from the start)
The reason I did this was because
http://zfs.macosforge.org/trac/wiki/issues
said that some of the properties wouldn't be supported because
they weren't applicable, and I had my doubts that was wise.
For example, even if there's no "share" command, a Mac can
most certainly share out files (via AFP, CIFS, or NFS). And
given an iSCSI target daemon, it could share out block storage
via iSCSI as well. That was about the simplest test of the latter
premise that I could think of, and at least in the basics, it worked.

ISCSI target performance

Hello!
There're a lot of iSCSI targets with one or two 1Gbps nics on market today but I have serious doubts about their performance: 1Gbps(or 2Gbps) compared to 6 Gbps in raw SAS/SATA make me think their network speed will be the bottleneck in any setup (for example,
two node cluster with an iscsi target). Can anybody please tell me what performance issues may arise, for example, if I place a VM with SQL server on such target?
Thank you in advance,
Michael

"To have fault tolerance you have to have either dual hardware controllers (storage virtualization
creating LU from ultiple physical spindles) or use distributed software controllers (DRBD, HAST, Clustered Storage Spaces etc). " - I don't agree: fault tolerance can be provided by the single RAID 5 controller - of cause it's better to have two controllers
but it's just one more level of fault tolerance. Many (or even all of them) iSCSI targets have RAID controllers that allow them to be fault tolerant and I can't understand why this is not the case with DAS: "If RAID capable, HBAs must be in non-RAID
mode with all RAID functionality disabled".
To make a long story short I'd like to know why I can use RAID with iSCSI and can't with DAS/SAS.
Regards,
Michael
Because Clustered Storage Spaces don't handle LU reservations in software (unlike other Software Defined Storage solutions like VSAN for example) and rely on a hardware mechanism inside single dual pot SAS drive for that. So either you use dumb SAS controllers
providing raw access to SAS spindles or use Clustered RAID controller who handle distributed lock on it's own (LSI Syncro for example) and in this case you *CAN* RAID disks and them pass them to CSS.
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

ISCSI target weirdness

Hello!
If I hadn't experienced the issue I'm going to talk about I would have hardly believed it may ever happen...
I'm starting setting up a test cluster (all hosts = WinServer 2012 R2): Host3 = iSCSI target, Host1 and Host2 - cluster nodes.
1) I create three iSCSI disks on Host3: Disk1-Q (5Gb),
FS (60 Gb), Mail (60 Gb). All of them are "part" of the single target.
2) ... then make an iSCSI connection to Host3 from Host1 and Host2.
3) On Host1 I open Disk Management and create three volumes: Disk1-Q (X),
FS (Y), Mail (Z).
4) I format disk X (Disk1-Q) and give it the name "QUORUM".
4) Now I must open Disk Management on Host2 and make these disks online....but having connected to Host2 I see that all three disks are already online and UNformatted.
Here goes my "funny" "tests:
5) On Host2 I format THE SAME disk X (Disk1-Q) and give it another name "QUORUM2" - the operation succeeds.
6) I create the folder "hhh" on disk X (Disk1-Q) when I connected to Host1 and create the folder "kkk" on
Disk1-Q when connected to Host2. Each node shows only its "own" folder on
Disk1-Q...
7!) a) On Host1: I copied one iso image (3,6 Gb) to disk X (Disk1-Q) and
b) On Host2: I copied other iso image (3.1 Gb) do disk
X (Disk1-Q).
The second copy operation succeeded too!!! Now my 5Gb disk X (iSCSI disk Disk1-Q) contains two iso images that total to 6.7Gb!
...I know that's impossible...is it magic?
...but looking at the pictures above what can you say?
Thank you in advance,
Michael

You cannot do what you're trying to do the way you do :) Making long story short: you connect single NTFS-formatted volume to more then one writer. They both update data and metadata w/o telling each other what they do. That results corrupted volume. You
absolutely need some separate arbiter to take care of ditributed locks. It can be CSV (set of filters on top of NTFS) or it can be some clustered file system (trust me you don't need this as it's expensive). Or layer SMB share on top of your block volume (iSCSI
or generic does not matter) and connect from multiple clients. For more details you can read the link below (ignore StarWind as issues are the same for any SAN). See:
SAN Vs. NAS
http://www.starwindsoftware.com/forums/starwind-f5/trying-clear-this-use-iscsi-instead-smb-t1392.html
Hope this helped a bit ;)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

ISCSI Target Settings - disabling automatically enabled IP addresses

Hey guys,
I could find a way to disabling the "new network addresses will automatically be enabled" function within the iSCSI Target Settings or via powershell.
Can anyone provide a good solution? For several reason I can't avoid to get new IPs regulary (dynamic IPv6 Environment)

Hi,
I’m a little unclear the issue. Do you want to the iSCSI Initiator always use a static IP address to connect the iSCSI Target even the IP address is automatically obtained? I cannot find there is such function.
You could refer to the article below to configure network connections between the initiator and Microsoft iSCSI Software Target.
Microsoft iSCSI Software Target 3.2: Known Issues and Updates
http://technet.microsoft.com/en-us/library/dd904411(v=ws.10).aspx
Best Regards,
Mandy
If you have any feedback on our support, please click
here .
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

ISCSI Target Initiator IDs malfunction?

On Windows Server 2012 R2, I have setup an iSCSI target and have allowed the following list of Initiators to connect:
IPAddress: 192.168.0.102 (iSCSI Initiator)
IPAddress: 192.168.0.109 (iSCSI Target)
No IQN has been listed, only IPAddress.
On the initiator, I make a quick connect to 192.168.0.109 (the target) but while I get a response right away, I get nothing to connect to. The Quick Connect windows says: "No Targets available for Login using Quick Connect."
If I telnet to 192.168.0.109 port 3260, I get through right away so I know the target is reachable.
Then I try to connect from the target (from 192.168.0.109 to 192.168.0.109) itself and I get a connection right away. Everything works.
So, why can't the iSCSI Initiator from 192.168.0.102 get a connection?
I have tried to add the IQN from the initiator to the target and retried the connect and now the initiator can connect. Something is weird here. Why is IPAddress not enough to connect remotely when it is enough to connect locally?
Then I thought perhaps the listed IQN is allowed from the listed IPAddress'es so I connected from a third pc (192.168.0.101) and it connected just fine (assuming the same IQN as 192.168.0.102 used).
What purpose does IPAdress have? It only seems to work locally.
One specific detail. There are 2 netcards in all pc's, one for 192.168.0.x and one for 192.168.34.x. Perhaps this is the issue so I specicied 192.168.0.102 as source IP on the Discover Portal setup for the initiator, but that changed nothing. Either that
source IP isn't passed along correctly or the target throws the source IP away and uses the target IP instead. Bug?
At any rate, specifying IPAddress has no value whatsoever.
It seems the only way to secure the iscsi target is to use the firewall for port 3260.

Hi,
Do you add the client IP address into the iSCSI Target server? When you create an iSCSI target, you need to add the clinet Ip address, then you can use iSCSI initiator in this host to connect.
For more detailed information, you could refer to the thread below:
How to troubleshoot "No Targets available for Login using Quick Connect."
https://social.technet.microsoft.com/Forums/windowsserver/en-US/9d32b6dd-2957-4305-9818-708d80df5ca1/how-to-troubleshoot-no-targets-available-for-login-using-quick-connect?forum=winserverfiles
Best Regards,
Mandy
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 Subscriber Support, contact [email protected]

Iscsi trustee issue

Hello everyone,
I have connected a Netware 6.5 SP 8 running edir 8.8.4 to my existing tree and configured it as a iscsi target and am attempting to use a Xen SLES 10 OES2 SP2 guest as an iscsi initiator. I am running into a slight issue though... In console one I can see my netware server and iscsi target objects, but cannot see my OES2 server object so that I can assign the trustee rights. If I log into imanager I can see the OES2 server object, but no iscsi target object and no Netware 6.5 server object... I cannot properly setup my initiator... If I try to create a connection I get an access denied message on the netware logger screen...
Thanks,

Hi,
datakey wrote:
>
> Hello everyone,
>
> I have connected a Netware 6.5 SP 8 running edir 8.8.4 to my existing
> tree and configured it as a iscsi target and am attempting to use a Xen
> SLES 10 OES2 SP2 guest as an iscsi initiator. I am running into a
> slight issue though... In console one I can see my netware server and
> iscsi target objects, but cannot see my OES2 server object so that I can
> assign the trustee rights.
But that has absolutely no connection to Netware, nor iSCSI. If you
don't see your OES2 server in ConsoleOne, it isn't even in the same
tree. Please ask in the OES2 install groups.
> If I log into imanager I can see the OES2
> server object, but no iscsi target object and no Netware 6.5 server
> object...
Nice. Not. You have obviously two entirely seperate eDir trees here. You
really need to solve this first, assuming you want both servers to be in
the same tree.
CU,
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de

Unable to expand/extend partition after growing SAN-based iSCSI target

Hello, all. I have odd situation regarding how to expand iSCSI-based partitions.
Here is my setup:
I use the GlobalSAN iSCSI initiator on 10.6.x server (Snow Leopard).
The iSCSI LUN is formatted with the GPT partition table.
The filesystem is Journaled HFS+
My iSCSI SAN has the ability to non-destructively grow a LUN (iSCSI target).
With this in mind, I wanted to experiment with growing a LUN/target on the SAN and then expanding the Apple partition within it using disk utility. I have been unable to do so.
Here is my procedure:
1) Eject the disk (iSCSI targets show up as external hard drives)
2) Disconnect the iSCSI target using the control panel applet (provided by GlobalSAN)
3) Grow the LUN/target on the SAN.
4) Reconnect the iSCSI initiator
5) Expand/extend the partition using Disk Utility to consume the (newly created) free space.
It works until the last step. When I reconnect to the iSCSI target after expanding it on the SAN, it shows up Disk Utility as being larger than it was (so far, so expected). When I go to expand the partition, however, it errors out saying that there is not enough space.
Investigating further, I went the command line and performed a
"diskutil resizeVolume <identifier> limits"
to determine what the limit was to the partition. The limits did NOT reflect the newly-created space.
My suspicion is that the original partition map, since it was created as 100% of the volume, does not allow room for growth despite the fact that the disk suddenly (and, to the system, unexpectedly) became larger.
Is this assumption correct? Is there any way around this? I would like to be able to expand my LUNs/targets (since the SAN can grow with the business), but this has no value if I cannot also extend the partition table to use the new space.
If anyone has any insight, I would greatly appreciate it. Thank you!

I have exactly the same problem that you describe above. My iSCSI LUN was near capacity and therefore i extended the iSCSI LUN from 100G to 150G. No problem so far.
Disk Utility shows the iSCSI device as 150G but i cannot extend the volume to the new size. It gives me the same error (in Dutch).
Please someone help us out !

My Windows 2012 ISCSI Target service needs to be restarted every time the server starts.

Every time I restart my Windows 2012 server, the ISCSI Target Service is unavailable to the clients even though it appears to be running.
I have to restart the service, then the clients can connect to it.
I tried to change the startup Type to Delayed, but I get an error 87: parameter is incorrect.
I've tried to delete and recreate the VHD and ISCSI Target.
I've tried to uninstall the Role, and reinstall it.
Anybody have any additional ideas to try and troubleshoot this?
Thank you
James Roper

The service is not starting correctly, even though it does start. If I restart the service, everything works correctly. Here is the event in the ISCSI Target.
Log Name: Microsoft-Windows-iSCSITarget-Service/Admin
Source: Microsoft-Windows-iSCSITarget-Service
Date: 5/8/2013 3:11:10 PM
Event ID: 10
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: SRV-ISCSI1
Description:
The Microsoft iSCSI Software Target service could not bind to network address 10.5.4.31, port 3260. The operation failed with error code 10049. Ensure that no other application is using this port.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-iSCSITarget-Service" Guid="{13953C6E-C594-414E-8BA7-DEB4BA1878E3}" />
<EventID>10</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-05-08T22:11:10.899843800Z" />
<EventRecordID>38</EventRecordID>
<Correlation />
<Execution ProcessID="976" ThreadID="1448" />
<Channel>Microsoft-Windows-iSCSITarget-Service/Admin</Channel>
<Computer>SRV-ISCSI1</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="IpAddress">10.5.4.31</Data>
<Data Name="dwPort">3260</Data>
<Data Name="Error">10049</Data>
</EventData>
</Event>

ISCSI Target Issues

Similar Messages

Maybe you are looking for