Re: SMS_INBOX_MANAGER error OLD CAP

I'm glad it worked out. I was reluctant to give you that solution because
its not really supported. Let me know if you find any "side affects" from
doing that so I can pass that data on.

--
Luke Packard [MSFT]

SMS 2003 Technical FAQ:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
SMS 2003 Scenarios and Procedures Planning and Deployment Guide:
http://www.microsoft.com/downloads/details.aspx?FamilyId=E0644BB4-2336-4254-8A18-9BC180713F7E&displaylang=en.
SMS 2003 Scenarios and Procedures: Security Guide
http://www.microsoft.com/downloads/details.aspx?FamilyID=3d81b520-a203-4376-a72d-fd34a6c4a44c&DisplayLang=en

This posting is provided "AS IS" with no warranties, and confers no rights.

"Fabio" <Fabio@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E0281DDD-C7BE-4522-B47B-7E0E1760347D@xxxxxxxxxxxxxxxx
> Luke,
> thanks for all.
>
> Finally I delete the registry key and all it works good.
> Fabio
>
> "Luke Packard [MSFT]" wrote:
>
>> Try adding this server as a site system and specifying it as a CAP.
>> You'll
>> get errors with site component manager because the sms executive service
>> is
>> already installed but I believe inbox manager will attempt to install
>> inboxes on the server. Of course you'll need to ensure the SMS Svc
>> account
>> has admin rights to the server. If Inbox Mgr successfully creates the
>> CAP
>> share then once it has completed updating it go ahead and remove the CAP
>> role and see if Inbox Mgr successfully clears out the entries from the
>> registry. If this does not work then I suggest contacting product
>> support
>> services.
>>
>> --
>> Luke Packard [MSFT]
>>
>> SMS 2003 Technical FAQ:
>> http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
>> SMS 2003 Scenarios and Procedures Planning and Deployment Guide:
>> http://www.microsoft.com/downloads/details.aspx?FamilyId=E0644BB4-2336-4254-8A18-9BC180713F7E&displaylang=en.
>> SMS 2003 Scenarios and Procedures: Security Guide
>> http://www.microsoft.com/downloads/details.aspx?FamilyID=3d81b520-a203-4376-a72d-fd34a6c4a44c&DisplayLang=en
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Fabio" <Fabio@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:40F8FA58-FB3F-4A7B-A413-601D15C64299@xxxxxxxxxxxxxxxx
>> > Luke,
>> > thanks again for your reply.
>> >
>> > I tried to do it but the problem still persists.
>> >
>> > Fabio
>> >
>> > "Luke Packard [MSFT]" wrote:
>> >
>> >> Try resetting the site.
>> >>
>> >> --
>> >> Luke Packard [MSFT]
>> >>
>> >> SMS 2003 Technical FAQ:
>> >> http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
>> >> SMS 2003 Scenarios and Procedures Planning and Deployment Guide:
>> >> http://www.microsoft.com/downloads/details.aspx?FamilyId=E0644BB4-2336-4254-8A18-9BC180713F7E&displaylang=en.
>> >> SMS 2003 Scenarios and Procedures: Security Guide
>> >> http://www.microsoft.com/downloads/details.aspx?FamilyID=3d81b520-a203-4376-a72d-fd34a6c4a44c&DisplayLang=en
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >> "Fabio" <Fabio@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:4DC906D3-AFFF-484C-88C1-56AFB3A041F1@xxxxxxxxxxxxxxxx
>> >> > Luke,
>> >> > thanks again for your reply.
>> >> >
>> >> > 1) My Site hierarchy is SMS 2.0 SP5
>> >> > 2) No, the CAP is not still listed as a site system with a component
>> >> > server
>> >> > role
>> >> > 3) I don't have a log entry in the sitecomp.log that shows if it was
>> >> > successfully deinstalled as a CAP, because I did it some months ago,
>> >> > and
>> >> > the
>> >> > log (and lo_) was overwrite before
>> >> > 4) I didn't find any reference on the site control file
>> >> > (sitectrl.ct0)
>> >> > for
>> >> > a
>> >> > SYSTEM_RESOURCE_USE section listing my server.
>> >> > 5) I find some references listng my server on the registry:
>> >> >
>> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox
>> >> > Instances\1073
>> >> >
>> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox
>> >> > Instances\1078
>> >> >
>> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox
>> >> > Instances\1083
>> >> >
>> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox
>> >> > Instances\1088
>> >> >
>> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox
>> >> > Instances\1093
>> >> >
>> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox
>> >> > Instances\1098
>> >> >
>> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox
>> >> > Instances\1103
>> >> >
>> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox
>> >> > Instances\1108
>> >> >
>> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox
>> >> > Instances\1113
>> >> >
>> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox
>> >> > Instances\1118
>> >> >
>> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox
>> >> > Instances\1631
>> >> >
>> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Inbox Source\Inbox
>> >> > Instances\1632
>> >> >
>> >> > Could I delete all these registry key?
>> >> > Fabio
>> >> >
>> >> > "Luke Packard [MSFT]" wrote:
>> >> >
>> >> >> Is this CAP still listed as a site system with a component server
>> >> >> role?
>> >> >> Do
>> >> >> you have a log entry in the sitecomp.log that shows it was
>> >> >> successfully
>> >> >> deinstalled as a CAP? Search the site control file for a
>> >> >> SYSTEM_RESOURCE_USE section listing this server. If exist, are any
>> >> >> server
>> >> >> roles specified? If its gone from the site control file then it
>> >> >> appears
>> >> >> there may be some persisted inbox rules in the registry.
>> >> >>
>> >> >> --
>> >> >> Luke Packard [MSFT]
>> >> >>
>> >> >> SMS 2003 Technical FAQ:
>> >> >> http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
>> >> >> SMS 2003 Scenarios and Procedures Planning and Deployment Guide:
>> >> >> http://www.microsoft.com/downloads/details.aspx?FamilyId=E0644BB4-2336-4254-8A18-9BC180713F7E&displaylang=en.
>> >> >> SMS 2003 Scenarios and Procedures: Security Guide
>> >> >> http://www.microsoft.com/downloads/details.aspx?FamilyID=3d81b520-a203-4376-a72d-fd34a6c4a44c&DisplayLang=en
>> >> >>
>> >> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> >> rights.
>> >> >>
>> >> >> "Fabio" <Fabio@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> >> news:C3B58309-6B51-4107-8F2D-60EB8D64CE7E@xxxxxxxxxxxxxxxx
>> >> >> > Luke,
>> >> >> > thanks for your reply.
>> >> >> >
>> >> >> > I have one primary and one secondary site. The primary site have
>> >> >> > only
>> >> >> > one
>> >> >> > CAP, itself.
>> >> >> > The secondary site had some CAP on itself and on other servers.
>> >> >> > I removed the CAP role on all other servers.
>> >> >> >
>> >> >> > The problem is that the secondary site still continue to try to
>> >> >> > contact
>> >> >> > one
>> >> >> > CAP (Simona) that is no longer on the network.
>> >> >> >
>> >> >> > I find the following error on the inbox manager:
>> >> >> >
>> >> >> > Cannot access MSWNET:["SMS_SITE=E01"]\\SIMONA\CAP_E01\
>> >> >> > $$<SMS_INBOX_MANAGER><lun gen 1 0:00:00.000 1601 W. Europe
>> >> >> > Standard
>> >> >> > Time><thread=2800 (0xAF0)>
>> >> >> > Cannot access the destination inbox path
>> >> >> > \\SIMONA\CAP_E01\clidata.box,
>> >> >> > Win32
>> >> >> > Error = 53 $$<SMS_INBOX_MANAGER><lun gen 1 0:00:00.000 1601 W.
>> >> >> > Europe
>> >> >> > Standard Time><thread=2800 (0xAF0)>
>> >> >> >
>> >> >> > I find no error on the site component manager:
>> >> >> >
>> >> >> > Fabio
>> >>
>> >>
>> >>
>>
>>
>>


.

Relevant Pages

  • Re: No site assignment found, Assigned=Yes Client=No
    ... SMS 2003 Scenarios and Procedures Planning and Deployment Guide: ... > SMS 2003 Scenarios and Procedures Planning and Deployment Guide: ...
    (microsoft.public.sms.admin)
  • Re: Overlapped I/O operation
    ... SMS 2003 Scenarios and Procedures Planning and Deployment Guide: ... >> SMS 2003 Scenarios and Procedures Planning and Deployment Guide: ...
    (microsoft.public.sms.misc)
  • Re: Overlapped I/O operation
    ... SMS 2003 Scenarios and Procedures Planning and Deployment Guide: ... >> SMS 2003 Scenarios and Procedures Planning and Deployment Guide: ...
    (microsoft.public.sms.misc)
  • Re: Synchronization of Primary Sites not working
    ... SMS 2003 Scenarios and Procedures Planning and Deployment Guide: ... >> SMS 2003 Scenarios and Procedures Planning and Deployment Guide: ...
    (microsoft.public.sms.admin)
  • Re: Overlapped I/O operation
    ... SMS 2003 Scenarios and Procedures Planning and Deployment Guide: ... >> SMS 2003 Scenarios and Procedures Planning and Deployment Guide: ...
    (microsoft.public.sms.misc)