Hello Customer,
Thank you for posting here.
According to your description, I understand that you get error "Server
error in / application" when you access companyweb. If I have misunderstood
the problem, please don't hesitate to let me know.
The companyweb uses Windows Integrated authentication. Therefore, please
ensure the windows 2000 clients had joined SBS domain.
Then, please verify the settings in IIS server as follows to check if it
helps:
a. Open IIS snap-in.
b. Go to companyweb, right click it to click Properties.
c. Click ASP.NET tab, please change the ASP.NET version to 1.1.4322.
d. Run IISReset command to take effect the change. Then please test the
issue to see if it resolved.
Based on my research, there are 3 scenarios for your error, so I suggest we
try the following steps to see if we can resolve this issue:
Scenario 1:
There must be a web.config file in folder Inetpub\companyweb. I try to
delete the file from the folder on my test machine, then try to access the
companyweb, I get the same error with you. Find a fine SBS server and copy
the file web.config to this problematic SBS server, then test this issue.
Scenario 2:
The Network Service group does not have sufficient permissions to the
Temporary ASP.NET Files folder on the domain controller.
To resolve this issue, follow these steps, as appropriate for the version
of ASP.NET that you are running.
1. Click Start, click Run, type cmd in the Open box, and then click OK.
2. Switch to the Drive :\Windows\Microsoft.Net\Framework\v1.1.4322 folder.
In this folder, Drive is the drive where Windows is installed. To do this,
type the following line at the command prompt, and then press ENTER:
cd Drive :\windows\microsoft.net\framework\v1.1.4322
3. Add the appropriate permissions to the Network Service group for the
Temporary ASP.NET Files folder. To do this, type the following line, and
then press ENTER:
aspnet_regiis -ir
Note: For more information about the difference between the -ir
command-line option and the -i command-line option, visit the following
Microsoft Web site:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/htm
l/cpgrfaspnetiisregistrationtoolaspnet_regiisexe.asp
4. Type exit , and then press ENTER to quit the command prompt.
Scenario 3:
Please ensure the SQL server (sharepoint) service on your SBS is correct
started.
1. Please run services.msc command on SBS to open the Services snap-in,
2. Open SQL Server (sharepoint) properties, click Log On tap, please select
Local System Account,
3. Click General tap, click start button, click OK.
4. Then test this issue.
If the issue persists, we have to reinstall the companyweb component
through the following KB:
How to remove and how to install the Windows Small Business Server 2003
SharePoint Services companyweb Web site
http://support.microsoft.com/?id=829114
If we cannot resolve the issue after we perform the above steps, please
kindly help me collect some information for further investigation:
1. Please capture screenshots on the error messages and send the pictures
to me at v-terliu@microsoft.com
2. Save the application event log and system event log as evt files on the
problematic machines and send to my mailbox: v-terliu@microsoft.com
3. Collect the IIS metabase on SBS and send to me: v-terliu@microsoft.com
for further analysis:
1). On Exchange Server, install .NET Framework Version 1.1:
http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-
8157-034d1e7cf3a3&DisplayLang=en.
2). Install MBExplorer by installing IIS 6 Resource Kit Tools:
http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
B628-ADE629C89499&displaylang=en.
3). Once it is installed, access it from Start, Programs, IIS Resources,
Metabase Explorer.
4). In the left pane, right click ''LM'' (under your server computer name)
to choose ''Export to file'', and then save it as IIS.mbk.
5). Compress this mbk file and send it to me for analysis. Please let me
know the password if you set on this iis mbk file.
4. Please collect the IIS log on SBS so that I can perform further research:
1). On Exchange Serves, open IIS MMC, right click Default Web Site and then
click Properties.
2). Click Website tab and then check Enable logging.
3). Stop the Default Website and RENAME the existing IIS log files under
C:\WINDOWS\system32\LogFiles\W3SVC1.
4). Restart the Default Website and reproduce the problem, which will
generate new IIS log file with the exact error.
5). Wait for a while so that IIS Log can be synced. And then go to the
following folder on Exchange Server: C:\WINDOWS\system32\LogFiles\W3SVC1.
6). Send me the log files to my working email address
v-terliu@microsoft.com. And please let me know the alias of the user who
encountered the issue.
5. Run command "ipconfig /all > c:\ipconfig_XP.txt" and "route print >
c:\route_XP.txt" on one XP client, send the files c:\ipconfig_XP.txt and
c:\route_XP.txt to me at v-terliu@microsoft.com
6. Run command "ipconfig /all > c:\ipconfig_2000.txt" and "route print >
c:\route_2000.txt" on problematic windows 2000 client, send the files
c:\ipconfig_2000.txt and c:\route_2000.txt to me at v-terliu@microsoft.com
Hope these steps will give you some help.
Thanks and have a nice day!
Best regards,
Terence Liu(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
19:59:13 GMT)
rv:1.8.1.11)
msrn-in!newshub.sdsu.edu!postnews.google.com!l1g2000hsa.googlegroups.com!not
-for-mail
http://companyweb