Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 347
  • Last Modified:

Web Part error on server only

Hi all,

I'm having the following issue. My developers have made an update to a component we run on our SharePoint farm.  For some unclear reason, they changed the public token of the assemblies in the wsp solution.

After clearing up all the issue I'm left with one problem:

When I want to look at a site in a web application with the wsp installed i have to following issues

On the server accessing the site using http://MyServer/sites/Site1  all web parts, including all of the OOB webparts, generate the following error: "Web Page Error: This page has encountered a critical error. Contact your system administrator if this problem persists." If I retract the solution from this web app, everything returns to normal.

While this happens no messages appear in the ULS although running on verbose


However when viewing the site  on a client pc, the webparts run fine...

and stranger

when using http://localhost/sites/Site1  on the server... the webparts also render correctly

Any ideas? Sites are always viewed in the same 'internet zone'


thx

Bart

0
Bart-Vandyck
Asked:
Bart-Vandyck
  • 3
1 Solution
 
DeathraceCommented:
configure alternate access mappings to your site, if you can render with localhost and not with hostname may be you have to change host file which is located in
C:\Windows\System32\drivers\etc

map the localhost to hostname(Myserver) and try rendering the page now..
0
 
sabby447Commented:
What it looks as is that you are trying to use the url on the same server where you have the site and please share if you are using a different host header name, If yes then you will have to add that host header in backward host header check or disable loopback check  in registry, Follow this article : http://support.microsoft.com/kb/896861 

Try adding the url in trusted zone on server if the above doesnt work
0
 
Bart-VandyckAuthor Commented:
Well I don't believe it to be related to the name I use. The name I use on the server is infact the netbios name of the server, and the sitecollection is setup without a host header name. Further if I retract the solution everything  starts working again on the server....

The loopback has been disabled allready...


(when using the URL http://localhost I actually see a error in the eventlog that no managed path for this is defined, but this seems normal as I did define one and I don't want to)
0
 
Bart-VandyckAuthor Commented:


I found the problem. When installing the new WSP file one of the dll's got not replicated to the second WFE Server. I guess by using 'localhost' it only looks at the current servers...

Still strange behavior but I'm happy it works now!
0
 
Bart-VandyckAuthor Commented:
Own solution found
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now