cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Ben_H
Level 8
Report Inappropriate Content
Message 1 of 6

Repo Pull Failed - Site catalog not found

Jump to solution

I am trying to do a repo pull and I get an error code 5 - access denied message when I try to do my repo pull from my internal UNC location. The credentials test successfully in the setup.

The task details message says "Failed to download file catalog.z from site [UNC path], error code 5 (access is denied)"

The catalog.z file is in the correct location.

Any ideas?

Update 1:

Reviewed the EpoApSvr logs to get additional information. The UNC connection is successful and ePO attempts to open() the catalog.z file then it gets access denied. Then the UNC connection closes.

The service account ePO uses to access the share has full control of the share location so I don't think it is a permissions issue.

Can someone explain what ePO is doing with the file? Is it trying to open it over the network?

2 Solutions

Accepted Solutions
Ben_H
Level 8
Report Inappropriate Content
Message 5 of 6

Re: Repo Pull Failed - Site catalog not found

Jump to solution

The catalog.z file does exist in the UNC location. No proxy is configured.

The solution was using FQDN in the Server Settings, Source Site configuration instead of the \\hostname\share. Even though the ePO OS was configured to append the domain/DNS suffix (in the interface configuration), using the short name in the ePO web UI caused the repo pull error.

Incorrect:

\\hostname\share

Correct:

\\FQDN\share

 

Thanks for the quick responses though, much appreciated!

View solution in original post

cdinet
Employee
Employee
Report Inappropriate Content
Message 6 of 6

Re: Repo Pull Failed - Site catalog not found

Jump to solution

Good to know, thanks for the update!

 

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

View solution in original post

5 Replies
cdinet
Employee
Employee
Report Inappropriate Content
Message 2 of 6

Re: Repo Pull Failed - Site catalog not found

Jump to solution

You might want to look at the security event logs on the unc server.  No, we don't open the files, it is a simple file copy.  

One thing to test is to go to windows explorer, computer, map network drive and use those same credentials.  Then try to copy the file manually and see if you still get access denied.  

 

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Ben_H
Level 8
Report Inappropriate Content
Message 3 of 6

Re: Repo Pull Failed - Site catalog not found

Jump to solution

We don't have any entries for failed logins in the security log on the UNC server. The credentials test successfully in the source site configuration.

Mapping the network drive with the service account and copying the file works with no issues.

Maybe the catalog.z file is not correct? We are retrieving all the contents of update.nai.com/commonupdater and making them available in our UNC share location.

Here is a sanitized excerpt of our logs:

20191218165119 I #04328 INETMGR Starting download session for site [ePO source site name].
20191218165119 I #04328 NAINET UNC Session initialized
20191218165119 I #04328 NAINET Connecting to UNC Server: [hostname]
20191218165119 I #04328 NAINET Domain name=[domain], User name=[service account]
20191218165119 I #04328 NAINET Mapping network share \\[UNC\location] using NetUseAdd
20191218165119 I #04328 NAINET Network Share \\[UNC\location] mapped
20191218165119 I #04328 NAINET Connected to UNC Server: [hostname]
20191218165119 I #04328 INETMGR Started download session 1 for site [ePO source site name].
20191218165119 I #04328 SITEMGR Downloading file catalog.z from [ePO source site name]
20191218165119 I #04328 INETMGR Downloading file catalog.z from session 1, LocalDir=C:\windows\TEMP\naiEC24.tmp\00000000, RemoteDir=.
20191218165119 I #04328 NAINET Downloading file \\[UNC\location]\catalog.z from UNC Server
20191218165119 I #04328 NAINET UNCConnection.cpp(371): CUNCConnection::DownloadFile File \\[UNC\location]\catalog.z Open() failed. Error: Access is denied.
20191218165119 I #04328 INETMGR Download file catalog.z not found on the remote dir in session 1.
20191218165119 I #04328 SITEMGR Mirror.cpp(210): Download file catalog.z from [ePO source site name] failed, hr=-1800
20191218165119 I #04328 NAINET Network share \\[UNC\location] deleted successfully(1)
20191218165119 I #04328 NAINET UNC Session closed
20191218165119 I #04328 INETMGR Session 1 ended, result=1.
20191218165119 I #04328 SITEMGR Mirror thread ended

cdinet
Employee
Employee
Report Inappropriate Content
Message 4 of 6

Re: Repo Pull Failed - Site catalog not found

Jump to solution

Does the catalog.z file actually exist in \\[UNC\location]?  If so and you can copy the file manually, check your browser settings under connection, lan settings.  What is set for proxy?  If anything, even automatically detect is enabled, try disabling that and see if you can still copy the file manually.  If it fails, then set epo to use the proxy settings the browser is using and try again.

The only other thing is to run wireshark while trying to pull the file.  I will be glad to look at it (I will send you my email address in private msg).  

 

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Ben_H
Level 8
Report Inappropriate Content
Message 5 of 6

Re: Repo Pull Failed - Site catalog not found

Jump to solution

The catalog.z file does exist in the UNC location. No proxy is configured.

The solution was using FQDN in the Server Settings, Source Site configuration instead of the \\hostname\share. Even though the ePO OS was configured to append the domain/DNS suffix (in the interface configuration), using the short name in the ePO web UI caused the repo pull error.

Incorrect:

\\hostname\share

Correct:

\\FQDN\share

 

Thanks for the quick responses though, much appreciated!

cdinet
Employee
Employee
Report Inappropriate Content
Message 6 of 6

Re: Repo Pull Failed - Site catalog not found

Jump to solution

Good to know, thanks for the update!

 

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from product experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by employees.
Join the Community
Join the Community