in

SharePoint University

Clean slate. Nothing but SharePoint.
Go, SharePoint!

The server name or address could not be resolved...

Last post 10-22-2007 3:10 PM by GreenLawn. 0 replies.
Page 1 of 1 (1 items)
Sort Posts: Previous Next
  • 10-22-2007 3:10 PM

    The server name or address could not be resolved...

    I am new to SharePoint Administration. 

    This is the error that one of my users is getting: Script execution error: the server name or address could not be resolved.

    I've searched for this issue on the net and the only item I found that match the specific error related to http://support.microsoft.com/kb/830038 HOWEVER, I dont believe I need this regedit procedure to fix my problem and here is why.

    I have a user that is a member to several sites within my sharepoint structure.  He has been given "READER and CONTRIBUTOR" permissions.
    He had been accessing the site with NO issues what so ever for over a year.  He had PC issues and his laptop was ultimately re-imaged.  The laptop was given the same name on the domain and he logs in with the same user credentials as before the re-imaging.

    The regedit is for server side, but because of the way this seems to be working (or not working) indicates to me that it is more permissions based than anything.

    He can successfully get about 2 levels deep in the sites for example....http://xxsps02xxxx/sites/SupplyChain/xxxxsville/default.aspx but any links that are from that point forward he is denied even though I can verify under site settings that he is listed.  I have tried removing and readding him as a user. 

    The server has been rebooted several times during the course of troubleshooting and I've also verified that another user CAN log onto his laptop and get to the required site folders - even though both users are setup identically. 

    Any thoughts would be appreciated at this point - Thx!

     

Page 1 of 1 (1 items)

Need SharePoint Training? Attend a SharePoint Bootcamp!
Forum content (c) original posters. Everything else (c) 2008 SharePoint Experts, Inc.