SharePoint and FrontPage 2003 Web Parts Error

Hi All,

Windows 2003 Server running IIS 6 and Windows Sharepoint Services. Standard Installation running (thanks to help from EE).

Client PC Trying to connect to the Server using FrontPage 2003. Get the following error :

    soap:Server Server was unable to process request. --> File or assembly name dnh5wq0x.dll, or one of its dependencies, was not found.    

Any suggestions?

Thanks
Sean
LVL 1
SeanNijAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
alimuConnect With a Mentor Commented:
ok, this post:
http://wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=228&Source=http%3A%2F%2Fwss%2Ecollutions%2Ecom%2FLists%2FFAQ%2520Sections%2FSection%2Easpx%3FID%3D3

says it's because your Sharepoint Timer Service needs to run using the same account as your WSS Admin App Pool.
0
 
SeanNijAuthor Commented:
Just another note, the error keeps changing each time I try open the site in FP:

soap:Server Server was unable to process request. --> File or assembly name h64k9rvm.dll, or one of its dependencies, was not found.    

its seems each time the "assembly name _______" keeps changing....
0
 
alimuCommented:
This article says the error will occur when you can't get enough information from the virtual server to load the Web Part/s
http://support.microsoft.com/default.aspx?scid=kb;EN-US;830342
There's a workaround there that may help you.
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
SeanNijAuthor Commented:
"move the assemblies to the global assembly cache"

The assembly cache would be where exactly?

0
 
alimuCommented:
usually in c:\windows\assembly (or wherever your windows directory is located)
0
 
SeanNijAuthor Commented:
Not working. One more thing, failed to mention *blush*, the Server was changed from a being "on a workgroup" to being a domain controller. Could this also effect the sharepoint.
0
 
alimuCommented:
it could but it should just be a matter of checking some configuration... For a start take a look at your event logs to make sure that IIS and sharepoint are healthy on the server.

Few questions (i know - looks like a whole pile of them!):
Have you changed the name of the server at all (this may affect anonymous access rights but IIS 6 should handle the change in most cases).
Can you ping the dns address for the website from the client (eg: ping www.myweb.mydomain) and get a response?
Can you browse web pages in the sharepoint site from the client?
Is the frontpage client connection information you were using still valid for the new server?
Is your web site setup with integrated authentication turned on?  (integrated & anonymous is ok too) - this is just to make sure authors and administrators are able to authenticate.
Are you using a domain user account on the client when you try to use frontpage?

Another thing to check is your IIS log to see if you're getting access denied errors, etc.
0
 
SeanNijAuthor Commented:
EventLog: One Error: Unable to connect to the database WSSConfigDB on SERVERNAME. (Restarted PC - Could this be because the database Engine had not started yet?) Other then that - no errors.


Answers:
Name change: No
Ping: Yes
Browse: Yes
Frontpage: Yes - I can connect and authenticate and see the website - the minute I try to modify anything - error
Integrated: Yes - Integrated and Anonymous
Domain: Yes

IIS Log: LogFile/System32 look fine, what else do i check?
0
 
alimuCommented:
I'm curious - are you getting exactly the same errors after moving the assembly files?
have you tried restarting IIS to make sure the app has unloaded itself before testing?

You might also find this one useful - this is about the creation of basic web parts, installation in GAC and how to make them strongly named http://msdn.microsoft.com/library/en-us/spptsdk/html/CreateABasicWP.asp?frame=true 
0
 
alimuCommented:
this always happens to me... I hit send and I'm too slow :)
0
 
SeanNijAuthor Commented:
Okay, the artical on msdn - wow man way too advanced for me!

Just going back to your moving of the assembly files. If i look in the global whatsamacallit i see a whole lot of Microsoft.Sharepoint.Dsp etc stuff....where exactly am i supposed to be moving from - what bin folder exactly?

Please keep in mind, i aint making any of my own VB stuff or anything - so it "out of the box".
0
 
SeanNijAuthor Commented:
"account as the WSS Admin App Pool account. " 

Previous post - If i look under services i dont see a WSS Admin .... service - how do i know what account the pool is running under?
 
0
 
SeanNijAuthor Commented:
ignore last post...

found it....

hmmm
0
 
alimuCommented:
did you check out the sharepoint timer service and the identity on your wss admin app pool?

if the above is ok and it's out of the box I'm not sure why you'd be getting that error....
If you are developing web parts yourself, hang onto the "advanced" article :) you may need it - particularly the "deploying" section at the bottom.

Have you tried going to the page you want to edit through the client's browser and going "file" "edit in frontpage" ?
0
 
alimuCommented:
oh... and the bin folder's default location is c:\inetpub\wwwroot\bin
but i'd leave that alone if we're not talking custom developed web parts here..
0
 
SeanNijAuthor Commented:
Okay, I changed the Pools all to use Local System - against advice of the pop up box. Now I have four of those WSSConfig Errors but if i open the Default page it doesnt show the web parts missing anymore and i can edit the webpage.

Okay so its working now. Whot do i do about the LocalSystem warnings?
0
 
alimuCommented:
What are the warnings (error source, number and info if possible)?

more tips:
with your identity, next step is to setup a domain account to run the pools and service - using local system gives them all administrative access to the server so this'll tighten up your security a little.  The domain account will need some level of access rights, probably start by adding it to the server's "users" group and work up from there.  

You might need to check out your group policy, IIS is not generally recommended for install on Domain Controllers (it can be done, just not recommended).  
Your server should currently have the default domain policy along with default domain controller policy(very restrictive) applied to it at present.  This will have repercussions on the rights available to users on your server.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.