RE: FAX Routing
- From: v-shshao@xxxxxxxxxxxxxxxxxxxx ("Shawn Shao [MSFT]")
- Date: Mon, 21 Jan 2008 09:12:39 GMT
Hi David,
Thank you for posting here!
From your post, I understand that when trying to route fax to documentlibrary in SharePoint, the following error was received:
"Unable to connect to the SharePoint site. There might be network or
SharePoint problems. Ensure that you have the correct permissions to access
the site, and then try again later. If the problem persists, you might need
to reinstall the windows small business server intranet component."
If there has been any misunderstanding, please feel free to let me know.
Base on my research, this error message is usually caused by the following
factors:
1. Missing or corrupted component (STSwrapper.dll)
2. Incorrect permission configurations.
Let's perform the following steps to fix this issue. We can check this
issue after each step.
Step 1: Register STSwrapper.dll
=============
1. Click Start and then Run.
2. Type in CMD and press Enter.
3. Copy and paste the following command and press Enter. (there will be
successful message)
C:\windows\Microsoft.Net\Framework\v1.1.4322\GACUTIL.exe /f /i "C:\Program
Files\Microsoft Windows Small Business Server\Client
Experience\stswrapper.dll"
IMPORTANT: The version of the framework folder (v.1.1.4322 in the example
above) should match the framework version being used for companyweb. To
check this view the properties of the companyweb site and click the ASP.NET
tab. The ASP.NET tab is present if .NET Framework 2.0 or later is installed.
Step 2: Check the version of STSwrapper.dll
=============
If SBS 2003 SP1 has been installed, verify the version of STSwrapper.dll
under C:\Program files\Microsoft Windows Small Business Server\Client
Experience\
If this file was updated by the service pack, the version will be 5.2.2893.
If this file is version 5.2.2651, copy ststwrapper.dll from an SP1 box,
then run:
C:\windows\Microsoft.Net\Framework\v1.1.4322\GACUTIL.exe /L | find /i "STS"
If the new version of STSWrapper was loaded into the Assembly cache, you
should see STSWrapper returned and we need to unregister it by running:
C:\windows\Microsoft.Net\Framework\v1.1.4322\GACUTIL.exe /u STSWrapper
Then register it with the following command:
C:\windows\Microsoft.Net\Framework\v1.1.4322\GACUTIL.exe /f /i "C:\Program
Files\Microsoft Windows Small Business Server\Client
Experience\stswrapper.dll"
Step 3: Verify the permissions on stswrapper.dll
=============
Locate this file, right click it and then choose Properties. Click the
Security tab.
The permissions should be:
-----------------------
Domain Admins - Full Control
Domain Power Users - Read & Execute, Read
Network Service - Read & Execute, Read
Sharepoint Administrators - Read & Execute, Read
System - Full Control
Step 4: Check DCOM configurations
=============
Check and, if different, change the Default Properties in Component
Services back to:
1. Click Start and then Run. Type in DCOMCNFG and press Enter.
2. Expand "Component Services" > Computers
3. Right click "My Computer" > Properties > Default Properties:
The "Default Distributed COM Communication Properties" should be:
Default Authentication Level : Connect
Default Impersonation Level : Identify
If this issue still occurs, please send me the following logs for further
research
1. All log files under: %ProgramFiles%\Microsoft Integration\Microsoft
Small Business Server 2003\Logs
2. MPS Report
--------------------
a. Please download the MPSRPT_SETUPPerf.EXE from the following link and
then run this tool to gather some information from the problematic computer:
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_SETUPPerf.EXE
b. Double-click on the MPSRPT_SETUPPerf.EXE file. [Note] This process may
take some time; however, it will not have a negative effect on the
performance.
c. A CAB file will be generated in the
%systemroot%\MPSReports\Setup\Reports\Cab directory
called%COMPUTERNAME%_MPSReports.CAB. The CAB file will contain the reports
generated by the MPS Reporting Tool.
You can zip these log files and send them as attachments to my mailbox
v-shshao@xxxxxxxxxxxxx
Hope the above information helps on this issue. If there is any update,
feel free to post back.
Best regards,
Shawn Shao
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
"Notify me of replies" box to receive e-mail notifications when there are
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.
.
- Prev by Date: OMA not working on Small Business Server 2003
- Next by Date: Re: Slightly OT: View Vista event log
- Previous by thread: OMA not working on Small Business Server 2003
- Next by thread: Re: SBS 2003 Crashing at nights
- Index(es):
Relevant Pages
|
