I am just re-factoring a Customer Portal (not Communities) on an old org and I come across the following error - just wondering if anyone has seen something like this before. Please have a look at the screenshots below:

enter image description here

If I debug more, it looks like a Salesforce.com script is trying to load a resource that does not exist. This script does not sound familiar at all to me, have a look at he screenshot:

Salesforce.com script

If this is a bug, how do I report it? Does Salesforce.com still support Customer Portal since the product SKU moved to Communities. Looking forward to thoughts and feedback!

  • where is the screenshot?????
    – akash
    Jan 28, 2015 at 11:47
  • Both are in the posts.
    – subodhbahl
    Jan 28, 2015 at 17:34
  • 1
    This happens on every Salesforce page I go to, regardless of user license or type.
    – zachelrath
    Feb 13, 2015 at 18:03

3 Answers 3


The image file logo180.png is obviously deleted or moved (or was never there).

I found that this error also shows in our org as well if you you open developer tools and refresh the page. I did a little digging and it appears the file is related to some marketing survey Salesforce created.

Here's the line in my org:

<script>var SFDCMktUrl='https://login.salesforce.com/17181/logo180.png';</script>

Later on in the page, the variable SFDCMktUrl is referenced in this script:

<script async="" defer="" src="/jslibrary/1421275782000/sfdc/MarketingSurveyResponse.js"></script>

This is clearly a Salesforce bug/defect.

  • The logo180.png is a Salesforce resource which I don't have access to. The script is a salesforce script as you can see attributes like SFDCMktUrl.
    – subodhbahl
    Jan 28, 2015 at 17:35

According to this discussion on Salesforce Success Community, this is actually working as designed. It's somehow part of a malware detection scheme. Perhaps if logo180.png that's a sign an account has been hacked and Salesforce will freeze their account. So, bizarrely, in this case missing 17181/logo180.png is a good thing.

Newer versions of Chrome (like v.47, currently only in Chrome Canary) have the option to block requests for certain URLs in the network window. This option is persistent, so you can just put logo180.png in there one time and it will never bug you about it again.

Accessing the Request Blocking option Adding the file to block (regex) logo180.png blocked in the network panel and no longer showing in the console


I had same bug in using base SF layout ... this script requirement generates 404 response

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .