DavidOverton.com
This site is my way to share my views and general business and IT information with you about Microsoft, IT solutions for ISVs, technologists and businesses, large and small.  
Forums » Microsoft Products » SBS 2008 » SBS Faxing Wizard issues

SBS Faxing Wizard issues

rated by 0 users
Answered (Verified) This post has 2 verified answers | 7 Replies | 2 Followers

Top 10 Contributor
Points 334
Matt Beardon posted on Sun, Dec 13 2009 3:53 PM

Hi All

I've recently migrated a server from 2003 to 2008, after a few issues I managed to get the bulk of the server migrated.

However, the fax services wizard stopped working - I have uninstalled and reinstalled the service and stil get the same message - which gives me an option to report to microsoft which takes a while but no solution as yet

The only error info:

Description:
  Stopped working

Problem signature:
  Problem Event Name: CLR20r3
  Problem Signature 01: faxcw.exe
  Problem Signature 02: 6.0.5601.0
  Problem Signature 03: 48a2260c
  Problem Signature 04: mscorlib
  Problem Signature 05: 2.0.0.0
  Problem Signature 06: 4a7ccd41
  Problem Signature 07: f46
  Problem Signature 08: 7
  Problem Signature 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
  OS Version: 6.0.6001.2.1.0.305.9
  Locale ID: 2057

Any help would be good.  Modem is a u.s. robotics sportster 56k

Matt

  • | Post Points: 21

Answered (Verified) Verified Answer

Top 10 Contributor
Points 334
Reply
Answered (Verified) Matt Beardon replied on Wed, Dec 23 2009 7:17 PM
Verified by David Overton

The Errors I had with this server were:

ConfigureExchangeEAPListTask: The Exchange E-mail address policy cannot be configured.

ConfigureGP: Windows Small Business Server group policies cannot be configured.
MUPhase2Task: One or more updates cannot be installed.
WSUSConfig: Windows Server Update Services cannot be configured.
ReDirOUTask:
ConfigureWSSOutgoingEmailTask: Incoming and outgoing e-mail for Windows SharePoint Services are not configured.
ConfigureWSSIncomingEmailTask: Incoming and outgoing e-mail for Windows SharePoint Services are not configured.

I'm working through recreating the group policies from:

http://blogs.technet.com/sbs/archive/2009/09/03/how-to-manually-create-the-sbs-2008-and-wsus-group-policies-objects.aspx

And I've cross referenced the GUIDs etc

I'll keep posting the results as I get them.

 

  • | Post Points: 5
Top 10 Contributor
Points 334
Reply
Answered (Verified) Matt Beardon replied on Wed, Dec 23 2009 8:43 PM
Verified by Matt Beardon

After importing the GPO's from http://blogs.technet.com/sbs/archive/2009/09/03/how-to-manually-create-the-sbs-2008-and-wsus-group-policies-objects.aspx 

The fax wizard ran successfully.

Thanks

Matt

 

  • | Post Points: 5

All Replies

Top 10 Contributor
Points 84,751
Reply
David Overton replied on Sun, Dec 13 2009 8:18 PM

Can you look in C:\Program Files\Windows Small Business Server\Logs for faxcw.log and e-mail it to me - [email protected].

Thanks


David

  • | Post Points: 21
Top 10 Contributor
Points 334
Reply
Matt Beardon replied on Sun, Dec 20 2009 8:09 PM

Hi

The log file is as follows:

---------------------------------------------------------
[9148] 091220.194941.9977: General: Initializing...C:\Program Files\Windows Small Business Server\Bin\FaxCW.exe
[9148] 091220.194944.7589: WizardChainEngine Next Clicked: Going to page {0}.: FaxConfiguration.SubscriberId
[9148] 091220.194945.5233: WizardChainEngine Next Clicked: Going to page {0}.: FaxConfiguration.OutboundDevice
[9148] 091220.194946.4125: WizardChainEngine Next Clicked: Going to page {0}.: FaxConfiguration.InboundDevice
[9148] 091220.194947.6760: WizardChainEngine Next Clicked: Going to page {0}.: FaxConfiguration.InboundRoutingSame
[9148] 091220.194951.5916: Wizard: WizardChainEngine Next Clicked: Last page, so the wizard isdone, closing wizard frame and returning
[11760] 091220.194951.8412: AdminTME: AdminDataLink Running Task: CommitterSequenceTask
[11760] 091220.194951.8880: AdminTME: Status: TaskId = IWorker.Fax.Common.TaskFaxStartServiceOnly, RootTaskId = IWorker.Fax.FaxConfiguration.TaskFaxConfigurationComposite, Success: True, Warning: False, Continue: True, Message:
[11760] 091220.194951.9036: AdminTME: Status: TaskId = IWorker.Fax.Common.TaskSetCoverPageToCurrentUsersRegistry, RootTaskId = IWorker.Fax.FaxConfiguration.TaskFaxConfigurationComposite, Success: True, Warning: False, Continue: True, Message:
[11760] 091220.194952.4184: AdminTME: Status: TaskId = IWorker.Fax.Common.TaskSetCoverPageToFile, RootTaskId = IWorker.Fax.FaxConfiguration.TaskFaxConfigurationComposite, Success: True, Warning: False, Continue: True, Message:
[9148] 091220.194952.4340: AdminTME: Committer: Completed called
[9148] 091220.194952.4652: Exception:
---------------------------------------
An exception of type 'Type: Microsoft.WindowsServerSolutions.Common.WSSGInvalidRegistryException, WSSG.Support, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has occurred.
Timestamp: 12/20/2009 19:49:52
Message: ClientDeployment registry key not found
Stack:    at Microsoft.WindowsServerSolutions.IWorker.Fax.Common.TaskSetCoverPageToClientsGroupPolicy.Run(ITaskDataLink dataLink)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.LightweightDataLink.Run(TaskId taskId, IAssemblyTask task, CompositeTask parentTask)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.SequentialTask.Run(ITaskDataLink dataLink)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.LightweightDataLink.Run(TaskId taskId, IAssemblyTask task, CompositeTask parentTask)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.SequentialTask.Run(ITaskDataLink dataLink)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.LightweightDataLink.Run(TaskId taskId, IAssemblyTask task, CompositeTask parentTask)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.SequentialTask.Run(ITaskDataLink dataLink)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.AdminDataLink.Run(TaskId taskId, IAssemblyTask task)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.Committer.DoWork(Object sender, DoWorkEventArgs e)
    at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

[9148] 091220.194952.4652: Exception:
---------------------------------------
An exception of type 'Type: System.Reflection.TargetInvocationException, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 12/20/2009 19:49:52
Message: Exception has been thrown by the target of an invocation.
Stack:    at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
    at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
    at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
    at System.Delegate.DynamicInvokeImpl(Object[] args)
    at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
    at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
    at System.Threading.ExecutionContext.runTryCode(Object userData)
    at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
    at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
    at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
    at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
    at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
    at Microsoft.WindowsServerSolutions.Common.Wizards.Framework.WizardFrameView.Create()
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.Committer.RunSynchronously()
    at Microsoft.WindowsServerSolutions.IWorker.Fax.Wizards.FaxConfiguration.FaxConfigurationWizard.Commit(ICommitterView view)
    at Microsoft.WindowsServerSolutions.IWorker.Fax.Wizards.FaxConfiguration.FaxConfigurationWizard.RunWizard()
    at Microsoft.WindowsServerSolutions.IWorker.Fax.Wizards.FaxConfiguration.Program.Main()
---------------------------------------
An exception of type 'Type: System.Reflection.TargetInvocationException, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 12/20/2009 19:49:52
Message: Exception has been thrown by the target of an invocation.
Stack:    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.Committer.HandleException(RunWorkerCompletedEventArgs e)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.Committer.RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
---------------------------------------
An exception of type 'Type: Microsoft.WindowsServerSolutions.Common.WSSGInvalidRegistryException, WSSG.Support, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has occurred.
Timestamp: 12/20/2009 19:49:52
Message: ClientDeployment registry key not found
Stack:    at Microsoft.WindowsServerSolutions.IWorker.Fax.Common.TaskSetCoverPageToClientsGroupPolicy.Run(ITaskDataLink dataLink)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.LightweightDataLink.Run(TaskId taskId, IAssemblyTask task, CompositeTask parentTask)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.SequentialTask.Run(ITaskDataLink dataLink)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.LightweightDataLink.Run(TaskId taskId, IAssemblyTask task, CompositeTask parentTask)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.SequentialTask.Run(ITaskDataLink dataLink)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.LightweightDataLink.Run(TaskId taskId, IAssemblyTask task, CompositeTask parentTask)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.SequentialTask.Run(ITaskDataLink dataLink)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.AdminDataLink.Run(TaskId taskId, IAssemblyTask task)
    at Microsoft.WindowsServerSolutions.TaskManagement.Admin.Committer.DoWork(Object sender, DoWorkEventArgs e)
    at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

 

I've tried running the wizard without any routing options selected. Or just one & Still get the error.

I've manually created the folders in sharepoint for the faxes and registry from (http://www.tech-archive.net/Archive/Windows/microsoft.public.windows.server.sbs/2009-03/msg01096.html)

I've checked the servers registry against another working sbs 2008 server (which installed the fax services without issues)

The message: " ClientDeployment registry key not found" is odd as it does exist HKLM\Software\Microsoft\SmallBusinessServer\Components\ClientDeployment DWord = 1

I can manually setup via the fax manager all the settings - Is it just a corrupt wizard?

Matt

 

  • | Post Points: 5
Top 10 Contributor
Points 334
Reply
Matt Beardon replied on Tue, Dec 22 2009 9:08 PM

Hi David

I've got a bit further with this issue. (after posting the issue on the microsofts partner forum) they checked the error logs and found:

ConfigureGP: Windows Small Business Server group policies cannot be configured.

Following keys were missing: (domain.local's have been changed!)

------------------

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\ClientDeployment\GPO

"SBSCSE"="Windows SBS CSE Policy"

"ALLSBSUsers"="Windows SBS User Policy"

"ALLClients"="Windows SBS Client Policy"

"VISTA"="Windows SBS Client - Windows Vista Policy"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\ClientDeployment\GPO\Windows SBS Client - Windows Vista Policy]
"FSPath"="\\\\domain.local\\SysVol\\domain.local\\Policies\\{BF62E77E-8FB7-451D-9725-BD71B1EB8B20}"
"DSPath"="LDAP://CN={BF62E77E-8FB7-451D-9725-BD71B1EB8B20},CN=Policies,CN=System,DC=domain,DC=local"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\ClientDeployment\GPO\Windows SBS Client - Windows XP Policy]
"FSPath"="\\\\domain.local\\SysVol\\domain.local\\Policies\\{EB67760B-9A9D-4696-B18D-F9B5C7E59055}"
"DSPath"="LDAP://CN={EB67760B-9A9D-4696-B18D-F9B5C7E59055},CN=Policies,CN=System,DC=domain,DC=local"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\ClientDeployment\GPO\Windows SBS Client Policy]
"FSPath"="\\\\domain.local\\SysVol\\domain.local\\Policies\\{8AB9D0DF-E783-4BDC-A84F-1F2BD3F84B80}"
"DSPath"="LDAP://CN={8AB9D0DF-E783-4BDC-A84F-1F2BD3F84B80},CN=Policies,CN=System,DC=domain,DC=local"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\ClientDeployment\GPO\Windows SBS CSE Policy]
"FSPath"="\\\\domain.local\\SysVol\\domain.local\\Policies\\{9E9FAA0E-63F8-491E-AEBD-1026BB791D79}"
"DSPath"="LDAP://CN={9E9FAA0E-63F8-491E-AEBD-1026BB791D79},CN=Policies,CN=System,DC=domain,DC=local"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\ClientDeployment\GPO\Windows SBS User Policy]
"FSPath"="\\\\domain.local\\SysVol\\domain.local\\Policies\\{17B7CBAF-929A-4488-BF3B-2A73C4220D31}"
"DSPath"=LDAP://CN={17B7CBAF-929A-4488-BF3B-2A73C4220D31},CN=Policies,CN=System,DC=domain,DC=local

 

 The UID's need to match the policy UID's so this will change on each server.

How to Manually Create the SBS 2008 and WSUS Group Policies Objects

http://blogs.technet.com/sbs/archive/2009/09/03/how-to-manually-create-the-sbs-2008-and-wsus-group-policies-objects.aspx

I'm still getting - unable to save cover page information - but its one step further. 

regards

Matt

  • | Post Points: 21
Top 10 Contributor
Points 84,751
Reply
David Overton replied on Tue, Dec 22 2009 9:25 PM

Matt,

the keys you mention (and more) are created during setup - did you get any errors during the setup of SBS 2008?

Thanks

David

  • | Post Points: 5
Top 10 Contributor
Points 84,751
Reply
David Overton replied on Wed, Dec 23 2009 5:46 PM

Matt,

I understand you are now working with our support team to resolve this.  The belief when I spoke to the team is that there was an error during setup.  While you can simply export the reg keys from another system this will not work by itself as the urls and IMAP references all need to be updated for your system.

Thanks

David

  • | Post Points: 21
Top 10 Contributor
Points 334
Reply
Answered (Verified) Matt Beardon replied on Wed, Dec 23 2009 7:17 PM
Verified by David Overton

The Errors I had with this server were:

ConfigureExchangeEAPListTask: The Exchange E-mail address policy cannot be configured.

ConfigureGP: Windows Small Business Server group policies cannot be configured.
MUPhase2Task: One or more updates cannot be installed.
WSUSConfig: Windows Server Update Services cannot be configured.
ReDirOUTask:
ConfigureWSSOutgoingEmailTask: Incoming and outgoing e-mail for Windows SharePoint Services are not configured.
ConfigureWSSIncomingEmailTask: Incoming and outgoing e-mail for Windows SharePoint Services are not configured.

I'm working through recreating the group policies from:

http://blogs.technet.com/sbs/archive/2009/09/03/how-to-manually-create-the-sbs-2008-and-wsus-group-policies-objects.aspx

And I've cross referenced the GUIDs etc

I'll keep posting the results as I get them.

 

  • | Post Points: 5
Top 10 Contributor
Points 334
Reply
Answered (Verified) Matt Beardon replied on Wed, Dec 23 2009 8:43 PM
Verified by Matt Beardon

After importing the GPO's from http://blogs.technet.com/sbs/archive/2009/09/03/how-to-manually-create-the-sbs-2008-and-wsus-group-policies-objects.aspx 

The fax wizard ran successfully.

Thanks

Matt

 

  • | Post Points: 5
Page 1 of 1 (8 items) | RSS

(c)David Overton 2006-23