Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4087
  • Last Modified:

microsoft iscsi initiator error

When Trying to re-add ISCSI Drive after running Windows 2003 R2 repair.  When I went back into the Initiator I could not add in the Targets and receive error Initiator instance does not exist?


Please help!!
0
nachs06
Asked:
nachs06
  • 2
  • 2
1 Solution
 
bluemelnCommented:
At what point exactly are you getting this error? Can you get into the iSCSI Initiator at all?
If so, are you getting this error on the Target Portals tab trying to Add a Portal?
If so, add targets first on the available targets tab.
0
 
nachs06Author Commented:
I can get into the initiator and can add in the target portals.  Non of the targets are seen. When I re-add the portal target IP's it gives me that error.  I have done no other config changes except for a server repair.
0
 
bluemelnCommented:
There are a couple of things you can look at, but it depends on the type of system you are using. If you use EMC, I can help you with details.
First off, are there any entries on the Available Targets tab?
Are there any entries on the Target Portals tab?
Have you rebooted the server since the repair?

On my SAN, for example, I have to run a SAN server utility to rediscover the connection between the server and the SAN. It's called EMC Navisphere. Another thing I sometimes have to do is to log on to the SAN management console and enter the connection to the server.

Here is the sequence that usually needs to be followed when setting up the connection to the SAN:
1. Under Target Portals click Add, but don't just enter the IP and port, also click on Advanced. The local adapter is the iSCSI Initiator, the Source IP is the IP address you entered on the SAN appliance as the authorized connecting server. The CHAP information (user name and shared secret) has to match that on the SAN appliance.
2. Under Targets, select Logon. If appropriate, choose multi-path and automatic reconnect.
3. Run the SAN utility on the server to rediscover the SAN. Reboot the server if necessary.
0
 
nachs06Author Commented:
Bluemeln,

Actually found a fix, Had to download and install the newest Initiator from MS.  The old version needed to be ran with an add on to interact with our iSCSI SAN.  The newest initiator has it built in.  


Thanks for taking the time to assist!!!
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now