Home > Failed To > Failed To Find Accessible Source

Failed To Find Accessible Source

ccmsetup 2/23/2006 10:17:29 AM 4044 (0x0FCC) Next retry in 10 minute(s)... ccmsetup 2/23/2006 10:07:29 AM 4044 (0x0FCC) Source \\servername\SMSClient\I386 is inaccessible (5) ccmsetup 2/23/2006 10:17:29 AM 4044 (0x0FCC) Failed to find accessible source. Log stored proc. The Account that you are using in the Client Installation Agent should be of the Domain Admin elevated persuasion. have a peek here

The below is jsut 1 example for on ofthe sites, this is occuring across a number of our sites all with diffrentprimary servers.From the ccmsetup.log, the error appears over and over At this moment, I can not say.I advise against using Domain\Administrator as your SMS Client Installation account. ccmsetup 2/23/2006 9:57:29 AM 4044 (0x0FCC) Next retry in 10 minute(s)... ccmsetup 2/23/2006 9:57:29 AM 4044 (0x0FCC) Source \\servername\SMSClient\I386 is inaccessible (5) ccmsetup 2/23/2006 10:07:29 AM 4044 (0x0FCC) Failed to find accessible source.

ccmsetup 2/23/2006 10:27:29 AM 4044 (0x0FCC) Next retry in 10 minute(s)... Join your peers on the Internet's largest technical computer professional community.It's easy to join and it's free. Other machines from this AD sitehave been upgraded with no problems. Checking the ccmsetup.log file shows below error message.  Source \\Server\SMSClient is inaccessible (67) ccmsetup 6/8/2012 1:05:13 PM 7980 (0x1F2C) Source \\Server\SMSClient is inaccessible (67) ccmsetup 6/8/2012 1:05:13 PM 7980 (0x1F2C) Failed to find accessible source.

Waiting forretry.]LOG]!>> [Management] >> System Center Suite >> [Configuration Manager] >> SMS 2003 Forum MenuPhoto GalleriesLog inRegistration / Sign up RSS FeedThread Options View Printable PageThread Reading Mode advanced client ccmsetup.log , installation fail with error1603 7.

You can define more then one there in format DOMAIN\USER. ONe thing though can you guys tell me if i could restart the ccmsetup at will. But it has to run as Local Administrator to do the add. I checked the registry on a few clients and didn't see the AutoShareServer and AutoShareWks keys but I know these can be created if necessary.

Any ideas or anything I'm missing? ccmsetup log entires 8. Or, perhaps restrictive NTFS permissions in place? Waiting for retry.

PhilMarcum (MIS) (OP) 27 Apr 06 08:58 From looking in the CCM.log file located on the site server the account I'm using to connect to the client returns the following: ---> Join Now For immediate help use Live now! Spend some time learning about the Con… Concerto Cloud Services Cloud Computing Cisco Advertise Here 656 members asked questions and received personalized solutions in the past 7 days. Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are

The share is accessible from the client machines, I opened the share up to everyone. navigate here Any ideas? They're all Assigned but the client won't install. I think Google is going to start rejecting my searches.. :) The latest thing we tried was to grant "Domain Computers" full access to the Installer location on the SMS server.

Copied the [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM] hive from a known good Go to Solution 2 2 3 Participants Vadim Rapp(2 comments) LVL 40 Installation30 MS Server OS5 riverhosp(2 comments) LVL 1 DecKen LVL 5 To change the password open the SMS Admin Console and expand Site Hierarchy tab then expand Site Settings under your primary server. You could create a little batchfile with the command in "net localgroup Administrators domain\smsmachineaccount /add", stick this on a share, and run a GP startup script to execute the batch from Check This Out ncotton (MIS) 26 Apr 06 12:00 Sounds like you have the client Windows XP Firewall enabled.

Close this window and log in. The setup appears to be running as System user, and accessing the network using a domain admin account for the network access.. RE: No admin$ and SMS clients not installing...~~~~~!

Here is an excerpt from the ccmsetup log file

Waiting for retry.Error(s): Client.msi.loga.Property(S): SmsDetectDowngrade_ErrorMessage = A newer version of the SMS Advanced Client is already installedb.Property(S): SmsDetectColocationDowngrade_ErrorMessage = A newer version of the SMS Management Point is installed. Make sure that the default admin$ share is enabled. This fixed about 60% of my machines that had the problem. this contact form Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by HomeForumsMIS/ITManagement ToolsMicrosoft: SMS (Systems Management Server) Forum No admin$ and

Thank you in advance Don Top CCMSETUP log error by jeffl » Wed, 07 Jan 2004 07:09:38 Is the SMS\Client folder actually shared out as 'SMSClient'? -- Jeff a number are nowfailing with "failed to find accessbile source" errors.I am able to ping the machines by hostname, connect via the admin$ sharealso by the c$ share all with no Greg Davies SMS/Citrix Engineer MCSE, MCSA #6 Online Bookmarks Sharing: Jump to: Jump to - - - - - - - - - - [General Tech Discussion] - - - Waiting for retry.

Thank you for the checklist though, I appreciate the feedback. Thank you in advance, Don Top CCMSETUP log error by RG9uIF » Wed, 07 Jan 2004 23:51:25 Yes, the folder is shared as SMSClient. Reran CCMSETUP.EXE and all went well. ******************************************************** To perform a more thorough manual rebuild, run the following series of commands: net stop ccmsetup %windir%\system32\wbem\winmgmt /clearadap %windir%\system32\wbem\winmgmt /kill %windir%\system32\wbem\winmgmt /unregserver %windir%\system32\wbem\winmgmt /reserver I've tried uninstalling and re-installing the MP.

No registry lookup for command line parameters is required.]