Jump to content


Elioti

problems with rolling out systems

Recommended Posts

Hi everyone,

 

hope anyone can support me cause I don't find my problem explained on google etc...

these are the warnings I can see in config mgr status message viewer;

 

SMS MP CONTROL MANAGER

The AMT Proxy Manager failed to replicate file

C:\Program Files\Microsoft Configuration Manager\inboxes\amtproxymgr.box\disc.box\{849BD1E2-1651-4251-8FC0-598737ABB3

RDC to out of band service point for the 0 time. The file will be re-send again later.

 

SMS_AMT_PROXY COMPONENT

The AMT Proxy Manager failed to replicate file C:\Program Files\Microsoft Configuration Manager\inboxes\amtproxymgr.box\disc.box

\{849BD1E2-1651-4251-8FC0-598737ABB3

RDC to out of band service point for the 9 time.

The file will be re-send again later.

 

SCCM is installed,with everything what is needed by the prerequisite checker etc..

 

AD extended.

some more info=

 

I can't find the problem:

it 's in a working area not virtual,not lab or something!

Share this post


Link to post
Share on other sites

I have instald server 2008

SCCM => system center configuration manager 2007 with service pack 1 x86

all the components as described in the guides on this forum :)

 

so now when i start my cmgr on my client in the domain,it gives some errors

by site status;

under component status

and site system status

it gives criticals errors.

 

maybe it is more usefull to post some screenshots.

Share this post


Link to post
Share on other sites

could you post mp log files which are present in SCCM installation folder\Logs.Also check if your WDS services are running for PXE service point error.

Have you tried restaring the server to see if that could help.Sometimes it helps if all the prereq are running fine.

 

 

Share this post


Link to post
Share on other sites

logssccm.jpg

 

mpcontrol.log=>

full of errors ofcourse I paste :

 

RetryDNSPublishingIfNecessary: No need to retry. Returning.~ $$<SMS_MP_CONTROL_MANAGER><vr apr 16 12:52:34.846 2010 Romance Daylight Time><thread=8032 (0x1F60)>

Completed periodic tasks. $$<SMS_MP_CONTROL_MANAGER><vr apr 16 12:52:34.846 2010 Romance Daylight Time><thread=8032 (0x1F60)>

Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error $$<SMS_MP_CONTROL_MANAGER><vr apr 16 12:57:34.527 2010 Romance Daylight Time><thread=8032 (0x1F60)>

Http test request failed, status code is 500, 'Internal Server Error'.~ $$<SMS_MP_CONTROL_MANAGER><vr apr 16 12:57:34.529 2010 Romance Daylight Time><thread=8032 (0x1F60)>

Successfully performed Management Point availability check against local computer.~ $$<SMS_MP_CONTROL_MANAGER><vr apr 16 12:57:34.530 2010 Romance Daylight Time><thread=8032 (0x1F60)>

Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error $$<SMS_MP_CONTROL_MANAGER><vr apr 16 12:57:34.534 2010 Romance Daylight Time><thread=8032 (0x1F60)>

Http test request failed, status code is 500, 'Internal Server Error'.~ $$<SMS_MP_CONTROL_MANAGER><vr apr 16 12:57:34.536 2010 Romance Daylight Time><thread=8032 (0x1F60)>

Successfully performed Device Management Point availability check against local computer.~ $$<SMS_MP_CONTROL_MANAGER><vr apr 16 12:57:34.537 2010 Romance Daylight Time><thread=8032 (0x1F60)>

 

the reboot doesnt fixxed any thing

there was also an application instald called teamfoundation from microsoft

this changed some settings with the iss changed the default web site settings from iis default page to something about sharepoint but

this is removed but i keep stucked with the errors/warnings etc above

Share this post


Link to post
Share on other sites

schema extended yes(after installation)

 

 

I restarted the WDS service

en 1 error is gone,

the http error stil remains

 

SO untill now I didn't remove the MP yet...hope it can be done without deleting it! if not I will try it offcourse.

 

i have checked twice thesite status = management point

properties , unchecked the option 'allow devices to use this management point'

 

 

 

marked and save

so then I refreshed my errors in site status -component status ALL MARKED GREEN

but the

site system status gives still the critical error RED :s configmgr managememnt point

if I check the details

 

critical%20error.jpg

 

 

I guess I was to enthousiast

cause after a while the error that went green (mp) has come back with a warning

 

errorback.jpg

Share this post


Link to post
Share on other sites

searching further for possibles causes :s

 

I was reading this error warning:

MP Control Manager detected DMP is not responding to HTTP requests. The http status code and text is 500, Internal Server Error.

 

Possible cause: DMP encountered an error when connecting to SQL Server.

Solution: Verify that the SQL server is properly configured to allow Device Management Point access.

If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security;

or configure the Device Management Point to use an NT integrated security account, with appropriate access.

If using integrated security, verify the account used by the DMP to connect to the SQL server is a member

of the SMS_SiteSystemToSQLConnection_<sitecode> group on the SQL server, that the account is not locked out,

and that the account password is not expired. (In standard security, the default account is SMS_SQL_RX_<sitecode>.)

 

Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory

Solution: Ensure SQL server SPNs are correctly registered. Review Q829868.

 

Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate.

Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use.

 

Possible cause: The designated Web Site is disabled in IIS.

Solution: Verify that the designated Web Site is enabled, and functioning properly.

 

Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges.

Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy.

 

For more information, refer to Microsoft Knowledge Base article 838891.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.