General help with errors?

[MarcBey]

Hey all,

I got a lot of Sharepoint error messages on the live server, although the webparts are working properly without any problems on the local machine. The error messages never indicated the right issue...

Therefore, I wonder, if there are any possibilities to get a deeper look into the Sharepoint processes, beyond debugging of the proprietary webparts with the sdk?

Are there any tools or possibilities to set breakpoints into the SP code, before the webparts will be executed?

Thanks a lot for any help!

Marc

 

[ChaserNL]

http://msdn.microsoft.com/library/en-us/spptsdk/html/DebuggingWebParts_SV01022252.asp?frame=true

Is this what you are looking for?

 

[ChaserNL]

And i forgot to ask if you have put try{ } catch(exception exp){} Around all your code? So you can pinpoint it that way?

 

[MarcBey]

Hey Chaser,


thanks for your help again, although I got still this problem with "properties...incorrect format ...cannot deserialize...".

The problem is that the webpart is working perfect locally but not on the server. Therefore I suppose the error happens before my webpart code is applied.

So I'm looking for a possiblity to debug the SP code which runs before the webpart code, so that i m able to get more information about the error statement.

Do you have any ideas ...is there a tool or a possibility to look behind the webpart?

Marc

 

[ChaserNL]

no i really dont have any more ideas, i am asumming its a webpart you developed yourself?

by SP code you mean the code of the aspx page its self? if so just run the page without the webpart on it and see if its going ok.

Mabye you could post the code here, and explain a bit whats its supposed to do, then i'll can take a look at the part and see if i can see the problem.

Something else you could try tho is taking the code and pasting it in a diferent webpart with a different name and key, then you can see if there is something srewy in the database that might refer to your specific part. Or that the problem still exists.

 

[ChaserNL]

I did some aditional searching and found this:

These errors can be caused when permissions that Windows SharePoint Services
configured on the Windows Temp directory were unintentionally reset (perhaps
during an upgrade to the operating system). To resolve this issue, make sure
that the following permissions are configured correctly.

Windows directory Required permissions
%WinDir%\Temp
Administrators - Full control

SYSTEM - Full control

STS_WPG - Read, Write

Network Service (for a domain controller only) - Read, Write

%WinDir%\System32\Logfiles
STS Administrators - Full Control

SYSTEM - Full control

STS_WPG - Read, Write

Network Service (for a domain controller only) - Read, Write


Note If your usage analysis log files are stored in a different location,
you must also be sure that the permissions for those log files match the
permissions for the Logfiles directory above.

For more information about the permissions needed for Windows SharePoint
Services to perform as expected, see Files and Permissions. This issue is
also covered by article 826786 in the Microsoft Knowledge Base.


Another thing i found was when adding webparts, you should first make a local copy of the dwp file your importing. I didnt realy see if they ment local for the user or local as on the server, but you could try it

 

[ChaserNL]

Yet another possible solution!

Is IIS set to use a static IP? If so, that's the problem. If you change the IP to All Unassigned, that should fix the problem.