Re: SMS_INBOX_MANAGER error OLD CAP

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: Client Install Location (not just SMSMAN)
    ... we did try assigning that "server share" ... is cannot be used as a remote CAP for an SMS 2003 site. ... "all-in-one" package (as in the client.msi for the advanced clients) without ...
    (microsoft.public.sms.misc)
  • Re: SMS Deployment Design
    ... There are several things you need to consider to properly size an SMS ... How many clients will you support. ... Planning and Deployment Guide from ... > know if a centrally located SMS 2003 server is sufficient, ...
    (microsoft.public.sms.admin)
  • Re: sms 03 questions
    ... Legacy Clients and are still valid site roles in SMS 2003, ... security practice is to remove all the CAP roles except one. ... You can add the management point ... role to a server that is currently acting as a CAP and it can perform both ...
    (microsoft.public.sms.admin)
  • Re: SMS_INBOX_MANAGER error OLD CAP
    ... Is this CAP still listed as a site system with a component server role? ... SMS 2003 Scenarios and Procedures Planning and Deployment Guide: ... > The secondary site had some CAP on itself and on other servers. ...
    (microsoft.public.sms.misc)
  • Re: Client Install Location (not just SMSMAN)
    ... That machine just has to be a share on the server machine which is created ... IF you are asking about manually just creating a share and putting the cap ... > what if that "CAP share" is just an "NT box share", its not an SMS server ... > You can then create a script that runs for those clients pointing to a ...
    (microsoft.public.sms.misc)
Loading