none
iSNS Event Viewer Error

    Question

  • Forgive me if this is the wrong forum, but I can't find one more specific to this error.

    I built a new machine running Windows 7 Ultimate 64-bt.  Each time I boot the machine, there is a warning error in the event viewer System log:

    Source: MSiSCSI

    Message: The firewall exception to allow Internet Storage Name Serve4r (iSNS) client funtionality is not enabled.  iSNS client functionality is not available.

    Where is this message coming from?  Is there any way to disable it?

     

    Thanks

     

    Thursday, February 10, 2011 7:19 PM

Answers

  • Are you using any network attached devices that use the iSCSI protocol?  If not, set the Microsoft iSCSI Initiator Service to manual (or just disable it altogether.)  This should prevent the error message from appearing in the logs.  

    If you are using iSCSI you'll have to go ahead and allow the exception in your firewall.

    Thursday, February 10, 2011 7:31 PM

All replies

  • Are you using any network attached devices that use the iSCSI protocol?  If not, set the Microsoft iSCSI Initiator Service to manual (or just disable it altogether.)  This should prevent the error message from appearing in the logs.  

    If you are using iSCSI you'll have to go ahead and allow the exception in your firewall.

    Thursday, February 10, 2011 7:31 PM
  • Thanks Bob.
    Thursday, February 10, 2011 9:05 PM
  • You're welcome.
    Thursday, February 10, 2011 9:13 PM
  • Yesterday, I set the service to manual and stopped it.  When I booted the machine up today, the service was started and had been set back to automatic.  Any idea what could have caused that?

    Friday, February 11, 2011 7:55 PM
  • Nope.  But you've probably got something installed that's doing it.  Try setting it to "Disabled", reboot and see if anything complains.
    Friday, February 11, 2011 8:28 PM
  • Ok, this is strange.  Disabled the service, now I get these two errors in Administrative Events:

    Log Name:      System
    Source:        Microsoft-Windows-DistributedCOM
    Date:          2/11/2011 7:47:34 PM
    Event ID:      10010
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      CrosshairPhenom
    Description:
    The server {10C73283-9138-4209-BABC-0E58B14E587D} did not register with DCOM within the required timeout.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
        <EventID Qualifiers="49152">10010</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-02-12T00:47:34.000000000Z" />
        <EventRecordID>9123</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>CrosshairPhenom</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">{10C73283-9138-4209-BABC-0E58B14E587D}</Data>
      </EventData>
    </Event>

     

    Log Name:      Application
    Source:        Application
    Date:          2/11/2011 7:48:24 PM
    Event ID:      0
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      CrosshairPhenom
    Description:
    The description for Event ID 0 from source Application cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    DDService error: 122
    Unable to start MS iSCSI service

    the message resource is present but the message is not found in the string/message table

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application" />
        <EventID Qualifiers="0">0</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-02-12T00:48:24.000000000Z" />
        <EventRecordID>4821</EventRecordID>
        <Channel>Application</Channel>
        <Computer>CrosshairPhenom</Computer>
        <Security />
      </System>
      <EventData>
        <Data>DDService error: 122</Data>
        <Data>Unable to start MS iSCSI service</Data>
      </EventData>
    </Event>

     

    Any idea what that DCOM server is that's trying to start the service?

     

    Saturday, February 12, 2011 12:58 AM
  • Well, something did complain after all, but it's not really saying what.  You've got a starting point though: {10C73283-9138-4209-BABC-0E58B14E587D}.  Try doing a Registry search starting on that and see where it leads.

    Are you sure you've got no LAN attached storage - NAS, SAN, tape libraries...?

    Saturday, February 12, 2011 1:15 AM
  • Found that value in "HKEY_CLASSES_ROOT\TivoNotify\CLSID".  Looks like my TiVo Desktop Server needs this, so I guess I need to enable an exception for this in Kaspersky?

    And no, I don't have NAS, SAN, etc.

    Thanks

    Sunday, February 13, 2011 12:49 AM
  • And no, I don't have NAS, SAN, etc.

    Actually, you do...

    Looks like my TiVo Desktop Server needs this, so I guess I need to enable an exception for this in Kaspersky?

    This counts as a NAS (Network Attached Storage) device.  So yeah, you'll need to re-enable the Microsoft iSCSI Initiator service and allow the exception in your firewall.

    Sunday, February 13, 2011 2:14 AM
  • Thanks again Bob.  I guess the old saying is true, you do learn something new every day!
    Sunday, February 13, 2011 5:52 AM
  • Turns out that the version of Kaspersky I'm using doesn't have the firewall feature.  I'm using the Win 7 firewall.  Been looking through the settings, but don't see how to add this exception.  Any idea how to do this?

    Thanks

    Monday, February 14, 2011 12:07 AM
  • Control Panel->Windows Firewall; in the left pane select Advanced settings.  From there you can set up or change your Inbound and Outbound rules.
    Monday, February 14, 2011 1:21 AM
  • I found two predefined entries in each the Inbound Rules and Outbound Rules named iSCSI service.  One is for the Domain profile and any remote address, and the other is for Private/Public profile and local subnet remote address.  I enabled the second one (Private/Public profile & local subnet) in the Inbound and Outbound rules, since the TiVo should be on the local subnet, and set the service back to automatic.  After a reboot, I'm still getting the error "The firewall exception to allow Internet Storage Name Serve4r (iSNS) client funtionality is not enabled.  iSNS client functionality is not available."

    Any idea if these are the actual rules I'm looking for?  I'm concerned about enabling the first rule (Domain profile & any remote address).  Would this open me up to a security vulnerability?

    My other thought was to use the specific program related to the iSCSI Initiator Service.  When I look at the properties of that service, it calls "C:\Windows\system32\svchost.exe -k netsvcs".

    Am I on the right track here?

    Monday, February 14, 2011 4:13 PM
  • I don't know, since my internal firewalls are turned off on my machines (I have a hardware firewall).  But according to the RFC the iSNS service uses port 3205, both TCP and UDP so you could try opening that port on those protocols for both incoming and outgoing.

    Also according to the RFC the iSNS service is optional for iSCSI, so odds are that your TiVo device isn't even actually using it; there may be a way to disable iSNS in the initiator service.  (iSNS provides name lookup services for iSCSI devices, similar to DNS on a normal network.)  I would also guess that the error could be safely ignored if everything seems to be working properly.

    Monday, February 14, 2011 5:02 PM
  • Thanks again for all the help Bob.  I'm just going to set those two rules back to disabled, disable the service, and then run some tests to be sure the TiVo desktop can see the TiVo, and that the TiVo can see the computer.  If those work, I'll just live with the event viewer error.
    Monday, February 14, 2011 8:30 PM
  • You'll want the iSCSI Initiator service running since TiVo apparently needs it.
    Monday, February 14, 2011 10:33 PM
  • I checked the TiVo forums, but didn't see any threads on this topic.  I posted the details of the issue there and will wait for a response.

    Thanks

    Monday, February 14, 2011 11:17 PM
  • THIS IS A GOOD/PERFECT EXAMPLE WHY ALL OF THESE USER FORUMS SHOULD BE ABANDONED AND ALL ISSUES BE FUNNELED THRU "EVENT VIEWER" WHICH DOCUMENTS ALL ISSUES AND SOLUTIONS AND THE RESOURCES OF MS BETTER DIRECTED AT PERFECTING SUCH, RATHER THAN THE MASSES OF USERS POKING AROUND AND DABBLING WITH THEIR PC'S OFTEN WITH BAD CONSEQUENCES.
    Saturday, March 22, 2014 12:41 AM
  • I'M SHAKING MY HEAD??????????????????  THESE FORUMS SHOULD BE ABANDONED IMMEDIATELY, BEFORE SOMEONE HURTS THEMSELVES.

    SEE BELOW

    Saturday, March 22, 2014 12:44 AM