Re: SMS_INBOX_MANAGER error OLD CAP

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: SMS_INBOX_MANAGER error OLD CAP
    ... Fabio ... > Try adding this server as a site system and specifying it as a CAP. ... Of course you'll need to ensure the SMS Svc account ... > Luke Packard ...
    (microsoft.public.sms.misc)
  • Re: SMS_INBOX_MANAGER error OLD CAP
    ... Fabio ... > Luke Packard ... > SMS 2003 Scenarios and Procedures Planning and Deployment Guide: ... >>> Try adding this server as a site system and specifying it as a CAP. ...
    (microsoft.public.sms.misc)
  • Re: SMS_INBOX_MANAGER error OLD CAP
    ... My Site hierarchy is SMS 2.0 SP5 ... the CAP is not still listed as a site system with a component server ... SYSTEM_RESOURCE_USE section listing my server. ... > Luke Packard ...
    (microsoft.public.sms.misc)
  • Re: Iron Man = Hitler
    ... Um, sorry, but Iron Man is the good guy here. ... doesn't want to work with Agent Hill who is, as you say, "a bitch". ... asked and helped her round up guys like Luke Cage ... then I'm sure Cap ...
    (rec.arts.comics.marvel.universe)
  • RE: Enterprise Library and Serviced Component (COM+)
    ... Thanks Luke. ... > If you are using Windows 2000, and your COM+ app is a server one, your ... > COM+app properties and set the Application Root Directory property to point ...
    (microsoft.public.dotnet.distributed_apps)