Hi,

I am gettings lots of Javascript errors on my SharePoint site. It is causing a lot of issues when you log into the SharePoint site internally and externally, it also doesnt matter what browser I use, the menu toolbar at the top will not load when you move between 'page' and 'browse' and just displays 'loading' and nothing happens. Also when you click 'add document' or 'upload a document' nothing happens. It did work fine but stopped when I published my site through my Forefront-TMG with alternate access mappings. Setup is:

User enters https://share.domain.com into IE from an external location . Traffic gets to Forefront-TMG and performs a reverse proxy and bridge to http://share.domain.com.

AAM's for my site are:

1. Internal URL = http://servername, zone = default, Public URL = http://servername
2. Internal URL = http://share.domain.com, zone = Internet, Public URL = http://share.domain.com

I have also setup bindings in IIS7 as follows:

Site Name = SharePoint - 80

1. Binding 1 - Type = http, Host Name = (Blank), Port = 80, IP Address = *, Binding = (Blank)
2. Binding 2 - Type = http, Host Name = share.domain.com, Port = 80, IP Address = *, Binding = (Blank)

The Javascript errors I get when I log into the page are:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; InfoPath.2; AskTbARS/5.11.4.15711)
Timestamp: Fri, 2 Sep 2011 12:29:04 UTC


Message: Syntax error
Line: 2
Char: 1
Code: 0
URI: http://servername/ScriptResource.axd?d=uovouhrEgyCS_75JM20ps7W4av5wPBtMACiBMCNWKYze9VbGAXUhpYioG729MoBB1yiKFvL_atFrJecECp-YVBFZMBMmp0xjPQS7HK5D-BltyIa_sNbx3vZRd4NA6IRQyTyBL4G3ABuKECn9_H3gU25-sys1&t=fffffffff9d85fa6


Message: Syntax error
Line: 2
Char: 1
Code: 0
URI: http://servername/ScriptResource.axd?d=DvDLt9okEx5girF-loZUj711cVab5vOi_4nsmcHny1XEwwLujl2GpsT1hehQoJSdv-VHoSVJ7DKJ5QgGASukuI7D_ncRMdHC19nCNpbEf86i_AhVOxV-FI0jzsJ8aXdak3PgJYUKaZsulXqI_ascXNnCtG6M2kfs2pg-5YmplMzGcX9O0&t=fffffffff9d85fa6


Message: Syntax error
Line: 2
Char: 1
Code: 0
URI: http://servername/WebResource.axd?d=U0-zo256wubzZcxVGT8ntSfdhL3CPzC-2U91HeBIMvZ5TCe8N87IlRuws30qw6XMAjJXvH2LnHskMaWCF8ZdwSI4TdI1&t=634245190248165742


Message: Syntax error
Line: 2
Char: 1
Code: 0
URI: http://servername/ScriptResource.axd?d=ZoMdDxOcMg83U1ARLHwJTmFIfDEmTq6z_x9D8WueYvA6vIIr_fj8c1SrXRqaRDSphqz2YSKP9IkvS_1qlTxyiMLqn4_PCTnRiVr6haAM9kZTX2bZz72zmiJKmp1GJhOker_IKQ2&t=ffffffff841270f7


Message: 'Sys' is undefined
Line: 228
Char: 1
Code: 0
URI: http://servername/sites/intranet/default.aspx


Message: 'WebForm_SaveScrollPositionSubmit' is undefined
Line: 1053
Char: 1
Code: 0
URI: http://servername/sites/intranet/default.aspx


Message: 'Type' is undefined
Line: 3
Char: 1
Code: 0
URI: http://servername/_layouts/navresizer.js?rev=eIyf%2BsxKEYfuJuIYj384zw%3D%3D


Message: 'Type' is undefined
Line: 2
Char: 1
Code: 0
URI: http://servername/_layouts/sp.core.js?rev=7ByNlH%2BvcgRJg%2BRCctdC0w%3D%3D


Message: Object doesn't support property or method 'registerInterface'
Line: 2
Char: 132
Code: 0
URI: http://servername/_layouts/cui.js?rev=wvoVpqlQb30nGo4DjDk8Kg%3D%3D

I have no idea what I have done to cause this as my SharePoint is now unusable, tried to remove AAM's etc to put it back to how it was but it made no difference.

Does anyone have any idea how I can rectify this and get my SharePoint working again internally and externally?

 

Thanks,

 

CraigNoz

 

 

One possibility is that the js files were not downloaded fully and are cached either at the client level or in some proxy server. Another possibility is they are blocked completely by some policy or other settings (you can easily test this using another site - local or public).
Suggestion is to use Fiddler to examine traffic and see if js files are being received by the client.
AK

I have installed Fiddler and opened the SharePoint site, when you try and click the buttons no traffic is logged in Fiddler, the only time anything is logged is when you move between pages, eg from documents to a callendar.

Some time ago I noticed that for a site that was published through an ISA Server AAM was not enough, I got a lot o js errors. I had to extend my web application and everything started working fine.

Cheers
Riccardo

Right,

So I can now use my SharePoint internally without issue, I have extened the Web Application and when I log in all is fine.

The Javascript errors still however exist externally when going through my Forefront-TMG. Im guessing I'm probably close to the bottom of the issue if its now ok internally.

Has anyone experienced the Javascript errors through Forefront?

 

CraigNoz

Go to (in Fiddler) Tools and clear WinInet cache. Then open the site and examine the scripts - you can also compare with working copies. The js files are cached as .js after being downloaded.
AK

Riccardo's answer was correct, after extending web application and a little bit of tweaking we now have internal and external fully functional SharePoint.

Thanks

 

CraigNoz

Thanks for pointing out. It is best practice to always extend your webapp when adding AAM. But I normally neglect this to avoid too many resources (IIS websites). It solves it but we need too get a litte deeper to explain it. Why TMG filters these out when just AAM without extending?

Chrome doesn't show these errors so I thought it was caused by IE. Knowing this now I checked Chrome, Tools, Javascript console, and guess what: they are there too:    

  

Can you elaborate more on what you did in TMG/Forefront I'm have the same issue and I feel like I have tried every configuration combination it.

Hi Craignoz i am having the same issue. The claims based site was already extended in internet zone and is working fine but all of sudden i am getting this issue. How did you fix this issue ?. Kindly explain.