Quantcast
Channel: Small Business Server forum
Viewing all 8539 articles
Browse latest View live

Remote Desktop Services (Terminal Services) Licenses on SBS 2011

0
0

I'm having a problem on Small Business Server 2011

It's supposed to come with 5 Terminal Services licenses, but when I try to log in with the 3rd concurrent user, I need to choose one of the two first users to disconnect. It also give a warning that the terminal licenses will expire.

So what I did was add an additional 5 licenses and now in Remote Desktop Session Host Configuration I have "Number of licenses available for clients" at 5, it was at 0 before.

Other settings are:

Delete temporary files on exit: Yes
Use temporary folders per session: Yes
Restrict each user to a single session: Yes
User logon mode: Allow all connections
Remote Desktop licensing mode: Per User
Remote Desktop license Server: Specified
Member of farm in RD Connection Broker: No
IP Virtualization: Not Enabled

But even after this only 2 concurrent users is allowed.

No idea what next, is it possible to return it to "factory" state without reinstalling Windows?


Check Your System Partitions for Bare Metal Backup & Restore

0
0

This is something that I didn't know and it took a while to figure out how to fix without bricking a server.

I bought a Dell T310 server without the OS and installed SBS 2011 on it. I didn't think to erase the partitions that Dell put on it because they looked correct. What I didn't know (because it doesn't show or warn you) the OS partition that Dell created was formatted as FAT32. SBS installed without any problems (I blame Microsoft for this part). I was able to backup the system thinking I had good backups for a bare metal restore. When I went to test a bare metal restore the image was not found. This started a long process to troubleshoot and a few threads and help from others.

I solved the problem by adding a drive letter (B:) to the OS system partition.

Used an elevated DOS prompt and went to B:

Ran Convert B: /FS:NTFS

It converted to NTFS without destroying the boot information.

Removed drive letter B: from system partition.

Rebooted (I had to reboot to configure backup again).

Configured server backup and the system partition is now part of the bare metal backup (it did not show prior to this).

Bare Metal Restore now works!

My advice: Check your system partitions that's labeled OS or system reserved and see if it's formatted as FAT32. You will not be able to do a bare metal restore (BMR) if it is.




Remote Desktop access

0
0
i know you can have two concurrent Remote Desktop sessions going on at the same time within small business server but my question is is a user logs in from the web based remote desktop client will effect a user who is already connected to the same server or is that allowed since its only two users at the moment...if someone is physically using the server or a program on the server will a user logging into the server from the web still be able to gain access with no interuptions...

SBS 2012 Accepted Domain

0
0

I need some
help in correcting a Small Business 2012 issue<o:p></o:p>

I mistyped the email domain, and I need to correct it. In the accepted Domains tab there
are two one called Land.local and the other called Premierlandsurvey.com however
it should be Premierlandsurveying, with the ing at the end. <o:p></o:p>

I went into AD and deleted the gateway Proxy in the CN=Windows SBS Email address policy,
Premierlandsurveying, properties so I could do a new email address policy. The
users were coming up with the wrong email address and their mail would not work
in their small business install. I did not discover that I did this incorrectly
until we were ready to move email off their ISP. I went back into EMC and tried
to remove the Windows SBS External Domain and I get the error the email address
policy object doesn’t have a primary SMTP Email address specified in the
template.<o:p></o:p>

I really
would appreciate some help with this I going to be working in this over the weekend

Thanks very
much in advance <o:p></o:p>

Rick<o:p></o:p>



Rick Arnold Arnoldconsult, MCP

Why The Cloud Push Will Fail!

SBS 2011 OWA Not working, ASP 2 errors, no access to Exchange console or powershell

0
0

OK, I have a problem that I'm pretty sure is related to IIS but is causing me a whole heap of issues.

 

Server was rebooted to install a new tape drive.  Following reboot OWA stopped working as well as ActiveSync.  Believed it to be a faulty install of Exchange 2010 rollup 4v2 so followed advice and installed it with elevated administrative priveledges.

 

This didn't fix the issue but now means I can't get into Exchange management AT ALL.  Exchange itself is working. Event Viewer is littered with ASP errors  Error messages at bottom – I’ll detail what I’ve tried to fix it first (as I’ve tried a LOT)

1)      Tried uninstalling the rollup

2)      Registered ASP 2.0, allowed .NET Framework 1.1 in IIS. Confirmed all AppPools are started

3)      Tried everything in http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx including running EMTShooter which gave me a supremely unhelpful output

4)      Renamed security.config

5)      Installed WinRM for IIS and also confirmed WinRM is correctly configured

6)      Checked that Kerbauth is native and just in powershell (not also def website)

7)      Checked WSMan module is in ApplicationHost.config

8)      Confirmed port 80 is bound to the default website

9)      Confirmed the location of Exchange install and powershell is correct

10)   Ran ExBPA.exe directly from its location – no issues

So I’m basically at my wits end and any help would be appreciated J

ASP Errors in Event Viewer:

Event 1334 ASP>NET 2…

 

Failed to initialize the AppDomain:/LM/W3SVC/1/ROOT/Microsoft-Server-ActiveSync

 

Exception: System.SystemException

 

Message: Failed to create AppDomain.

Plus

IIS-W3SVC-SP 2299

An application has reported as being unhealthy. The worker process will now request a recycle. Reason given: ASP.NET application initialization failed.. The data is the error.

When I try to connect to Exchange Console I get:

Attempt to connect using Kerberos failed. ..WinRM client received an HTTP server status (500)

Connecting to powershell gives:

 VERBOSE: Connecting to SBS2011.Blah.local

[sbs2011.blah.local] Connecting to remote server failed with the following error message : The WinRM client rece

ived an HTTP server error status (500), but the remote service did not include any other information about the cause of

 the failure. For more information, see the about_Remote_Troubleshooting Help topic.

    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc

   eption

    + FullyQualifiedErrorId : PSSessionOpenFailed

VERBOSE: Connecting to SBS2011.blah.local

[sbs2011.blah.local] Connecting to remote server failed with the following error message : The WinRM client rece

ived an HTTP server error status (500), but the remote service did not include any other information about the cause of

 the failure. For more information, see the about_Remote_Troubleshooting Help topic.

    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc

   eption

    + FullyQualifiedErrorId : PSSessionOpenFailed

VERBOSE: Connecting to SBS2011.Blah.local

[sbs2011.blah.local] Connecting to remote server failed with the following error message : The WinRM client cann

ot process the request. It cannot determine the content type of the HTTP response from the destination computer. The co

ntent type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.

    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc

   eption

    + FullyQualifiedErrorId : PSSessionOpenFailed

Exchange 2010 is suddenly unmanageable

0
0

Hi --

On a SBS 2011 box running Exchange 2010 SP2, Exchange has suddenly become unmanageable. I have no idea what happened overnight to cause this. But I've been trying to get this fixed for two hours already, with no luck.

Nobody can open OWA. From anywhere. Including from the server itself. IE network diagnostics reveal that "The device or resource (whatever) is not set up to accept connections on port "https".

The Exchange Management Console won't open. I get the error "The attempt to connect to http://server/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: The WinRM client cannot process the request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service configuration or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic."

Opening an Exchange Management Shell results in the error:

>>>>>>>>>>>>>>>>>>>>>>>>

VERBOSE: Connecting to server.domain.local
[server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
ooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to server.domain.local
[server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
ooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to server.domain.local
[server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
ooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:

<<<<<<<<<<<<<<<<<<<<<<<<

I have checked and double-checked bindings, Kerberos settings, and a slew of other things. I have reset IIS and rebooted the server multiple times. I can't get past this. Everything referenced in the following articles was checked and verified to be as the articles said they should be:

http://blogs.technet.com/b/bshukla/archive/2012/05/04/exchange-management-shell-error-500-internal-server-error.aspx

http://technet.microsoft.com/en-us/library/ff607221%28v=EXCHG.80%29.aspx

http://support.microsoft.com/kb/2028305

I installed and ran the EMTshooter script referenced in http://blogs.technet.com/b/exchange/archive/2010/12/07/resolving-winrm-errors-and-exchange-2010-management-tools-startup-failures.aspx. This it what it reported:

>>>>>>>>>>>>>>>>>>>>>>>>

Welcome to the Exchange Management Troubleshooter!

We recommend that you run the troubleshooter after making changes to
IIS to ensure that connectivity to Exchange Powershell is unaffected.

Checking IIS Service...

Checking the Exchange Install Path variable...

Checking the Powershell Virtual Directory...

Checking the Powershell vdir SSL setting...

Checking the Powershell vdir path setting...

Checking HTTP Port 80...

Checking HTTP Port 80 Host Name...

Testing for errors...

VERBOSE: Connecting to server.domain.local


[server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a r
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExcep
    + FullyQualifiedErrorId : PSSessionOpenFailed
The Exchange Management Troubleshooter successfully completed connecting to:

server.domain.local

Failed to connect to any Exchange Server in the current site.

Problem found:

Looking for error...

These are the possible causes for this error:

1. The default http binding has been removed from the Default Web Site. Exchange Powershell needs http to be configured
so that the IP Address is "All Unassigned", the Port is "80", and the Host Name is "".  A common scenario for changing t
his is if you are running multiple web sites, and attempting to set up a redirect to https://mail.company.com/owa by req
uiring SSL on the Default Web Site, and creating another web site to do the redirect back to the SSL-enabled website. Re
mote PowerShell requires port 80 to be available on the Default Web Site for all Internet Addresses. If you want to set
up an automatic redirect to /owa and redirect http requests to https, you should follow the instructions located at:

http://technet.microsoft.com/en-us/library/aa998359(EXCHG.80).aspx

and follow the directions under the section:
"For a Configuration in Which SSL is required on the Default Web Site or on the OWA Virtual Directory in IIS 7.0."

2. The http binding on the Default Web Site has been modified, and the Hostname field configured. To correct this issue,
 you need to clear out the Hostname field under the port 80 bindings on the Default Web Site.

After each error is resolved, close this window and re-run the tool to check for additional problems.

<<<<<<<<<<<<<<<<<<<<<<<<

However, the bindings on the Default Web site are correct (I've checked them multiple times).

And the server's System, Security and Application logs are devoid of anything that could even begin to explain what is going on.

And this was all working yesterday ...

I have automatic replies to modify/remove and have no way to get to them. Outlook on the PCs won't pull up Automatic Replies, claiming that the server is unavailable. On the other hand, email is coming and going fine ...

I need to get this fixed _now_. Does anybody know how to get to the bottom of this -- and what could have possibly happened to cause this in the first place?

Thanks
CL

SBS2011 premium and Remote Desktop Services in Hyper-V

0
0

Hello, Is it possbile to run SBS2011 premium and Windows 2008 RDP (terminal server) in Hyper-V? I think it does.
it is for a small company, 14 users wich 4 only work RDP.
config of server is 1 xeon proc. with 32GB memory, 2 sets of RAID1, 1 for SBS and 1 for RDP server.
Any tips are appreciate.
regards, Marc


MarcH


migrate windows server 2003 to sbs 2011

0
0

hi,

i want migrate a domain windows 2003 (only one server 2003 sp2) to small business server 2011.

I've installed and used sbs migration prepartion tools but after the update schema i've an error on the log file and i cannot continue the script.

The server sbs 2011 cannot connect to server 2003 because doesn't meet the requirements of server.

09/10/2012 18:23:17              Adprep returned: Success(0)
09/10/2012 18:23:17              adprep.exe Exists: False
09/10/2012 18:23:17              adprep\adprep.exe Exists: True
09/10/2012 18:23:17              Running C:\Programmi\Windows Small Business Server 2011 Standard Migration Preparation Tool\adprep\adprep32.exe /domainPrep /gpprep /wssg /silent
09/10/2012 18:23:19              
09/10/2012 18:23:20              
09/10/2012 18:23:20              Adprep returned: Success(0)
09/10/2012 18:23:20              Adprep has succeeded.
09/10/2012 18:23:20          Task finished successfully
09/10/2012 18:23:28          Starting health scan using MBCA engine..
09/10/2012 18:23:35  !Error! BPAEngine: Microsoft.WindowsServerSolutions.SmallBusinessServer.Tools.MigrationPrep.Wizard.BPAException: Unexpected PSRuntime exception. ---> System.Management.Automation.CmdletInvocationException: Errori durante il caricamento del file di dati di formato: 
Microsoft.PowerShell, ,X:\Programmi\Microsoft Baseline Configuration Analyzer 2\Modules\baselineconfigurationanalyzer\Microsoft.BaselineConfigurationAnalyzer.Cmdlets.Formats.ps1xml : file ignorato a causa della seguente eccezione di convalida: Controllo AuthorizationManager non riuscito..
 ---> System.Management.Automation.RuntimeException: Errori durante il caricamento del file di dati di formato: 
Microsoft.PowerShell, ,X:\Programmi\Microsoft Baseline Configuration Analyzer 2\Modules\baselineconfigurationanalyzer\Microsoft.BaselineConfigurationAnalyzer.Cmdlets.Formats.ps1xml : file ignorato a causa della seguente eccezione di convalida: Controllo AuthorizationManager non riuscito..

   in System.Management.Automation.Runspaces.FormatAndTypeDataHelper.ThrowExceptionOnError(String errorId, Collection`1 independentErrors, Collection`1 PSSnapinFilesCollection, RunspaceConfigurationCategory category)
   in System.Management.Automation.Runspaces.RunspaceConfiguration.UpdateFormats()
   in System.Management.Automation.Runspaces.RunspaceConfigurationEntryCollection`1.Update(Boolean force)
   in Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(ExternalScriptInfo scriptInfo, ManifestProcessingFlags manifestProcessingFlags, Version version)
   --- Fine dell'analisi dello stack dell'eccezione interna ---
   in System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   in System.Management.Automation.Internal.PipelineProcessor.SynchronousExecute(Array input, Hashtable errorResults)
   in System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
   in System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
   --- Fine dell'analisi dello stack dell'eccezione interna ---
   in Microsoft.WindowsServerSolutions.SmallBusinessServer.Tools.MigrationPrep.Wizard.MBCAEngine.Run()
   in Microsoft.WindowsServerSolutions.SmallBusinessServer.Tools.MigrationPrep.Wizard.BPALauncher.Run()
09/10/2012 18:23:35          Unexpected errors occurred during BPA scan.
09/10/2012 18:24:22          Starting health scan using MBCA engine..
09/10/2012 18:24:22  !Error! BPAEngine: Microsoft.WindowsServerSolutions.SmallBusinessServer.Tools.MigrationPrep.Wizard.BPAException: Unexpected PSRuntime exception. ---> System.Management.Automation.CmdletInvocationException: error load file format
Microsoft.PowerShell, ,X:\Programmi\Microsoft Baseline Configuration Analyzer 2\Modules\baselineconfigurationanalyzer\Microsoft.BaselineConfigurationAnalyzer.Cmdlets.Formats.ps1xml : file ignorato a causa della seguente eccezione di convalida: Controllo AuthorizationManager non riuscito..
 ---> System.Management.Automation.RuntimeException: Errori durante il caricamento del file di dati di formato: 
Microsoft.PowerShell, ,X:\Programmi\Microsoft Baseline Configuration Analyzer 2\Modules\baselineconfigurationanalyzer\Microsoft.BaselineConfigurationAnalyzer.Cmdlets.Formats.ps1xml : file ignorato a causa della seguente eccezione di convalida: Controllo AuthorizationManager non riuscito..

   in System.Management.Automation.Runspaces.FormatAndTypeDataHelper.ThrowExceptionOnError(String errorId, Collection`1 independentErrors, Collection`1 PSSnapinFilesCollection, RunspaceConfigurationCategory category)
   in System.Management.Automation.Runspaces.RunspaceConfiguration.UpdateFormats()
   in System.Management.Automation.Runspaces.RunspaceConfigurationEntryCollection`1.Update(Boolean force)
   in Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(ExternalScriptInfo scriptInfo, ManifestProcessingFlags manifestProcessingFlags, Version version)
   --- Fine dell'analisi dello stack dell'eccezione interna ---
   in System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   in System.Management.Automation.Internal.PipelineProcessor.SynchronousExecute(Array input, Hashtable errorResults)
   in System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
   in System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
   --- Fine dell'analisi dello stack dell'eccezione interna ---
   in Microsoft.WindowsServerSolutions.SmallBusinessServer.Tools.MigrationPrep.Wizard.MBCAEngine.Run()
   in Microsoft.WindowsServerSolutions.SmallBusinessServer.Tools.MigrationPrep.Wizard.BPALauncher.Run()
09/10/2012 18:24:22          Unexpected errors occurred during BPA scan.
09/10/2012 18:24:29          Writing migration ready flag to False
09/10/2012 18:24:29          Writing time stamp to registry
09/10/2012 18:24:29          Writing Errors and warnings count to registry

Thank you very much for help

windows sbs 2003 BPA is only for small business so i cannot do on windows 2003 and i cannot finish the prepare tool for migrating.

i'e already read this post 

Windows Server 2003 to SBS 2011 Std Migration

http://social.technet.microsoft.com/Forums/da/smallbusinessserver/thread/099e06ad-194f-47da-ad88-a2e175263ef8

but i cannot use BPA

 

SBS 2008 data move wizard crashing. Moving Redirected Documents. SUBST drive?

0
0

We're trying to move Users' Redirected Documents data using the wizard in the SBS console. It keeps crashing though as soon you hit next for the fist time in the wizard.

The main error appears to be "WMI error occurred while accessing drive ---> System.Management.ManagementException: Not found "

I've looked at a number of things and the closest crash I can find on the internet is related to dynamic disks. This machine doesn't have a dynamic disk but it does have a drive mapped with SUBST and I was wondering if this could cause the following:

Problem details:

Description:
  Stopped working

Problem signature:
  Problem Event Name: CLR20r3
  Problem Signature 01: movedata.exe
  Problem Signature 02: 6.0.5601.0
  Problem Signature 03: 48a22618
  Problem Signature 04: mscorlib
  Problem Signature 05: 2.0.0.0
  Problem Signature 06: 4ef6c2e7
  Problem Signature 07: 20c8
  Problem Signature 08: 143
  Problem Signature 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
  OS Version: 6.0.6002.2.2.0.305.9
  Locale ID: 2057

Logfile:

[15956] 120907.170307.9253: Storage: Initializing...C:\Program Files\Windows Small Business Server\Bin\MoveData.exe
[15956] 120907.170308.0581: Storage: Data Store to be moved: UserDocuments
[15956] 120907.170308.0981: Storage: Exception Microsoft.WindowsServerSolutions.Common.WindowsTaskSchedulerException:

[15956] 120907.170308.1071: Exception: 
---------------------------------------
An exception of type 'Type: Microsoft.WindowsServerSolutions.Common.WindowsTaskSchedulerException, Common, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has occurred.
Timestamp: 09/07/2012 17:03:08
Message: Task not found.
Stack:    at Microsoft.WindowsServerSolutions.Common.WindowsTaskScheduler..ctor(String taskPath, String taskName)
  at Microsoft.WindowsServerSolutions.Storage.Common.ServerBackupUtility.GetServerBackupTaskStatus()

[15956] 120907.170308.1101: Storage: Error Retrieving Server Backup Task Status: ErrorCode:0
BaseException: Microsoft.WindowsServerSolutions.Storage.Common.StorageException: GetServerBackupTaskStatus: fail to find the task ---> ErrorCode:0
BaseException: Microsoft.WindowsServerSolutions.Common.WindowsTaskSchedulerException: Task not found.
   at Microsoft.WindowsServerSolutions.Common.WindowsTaskScheduler..ctor(String taskPath, String taskName)
   at Microsoft.WindowsServerSolutions.Storage.Common.ServerBackupUtility.GetServerBackupTaskStatus()
   --- End of inner exception stack trace ---
   at Microsoft.WindowsServerSolutions.Storage.Common.ServerBackupUtility.GetServerBackupTaskStatus()
   at Microsoft.WindowsServerSolutions.Storage.MoveData.Helper.get_ServerBackupTaskState()
[15956] 120907.170308.5087: Storage: Backup Task State: Unknown
[15956] 120907.170308.6326: Storage: Launching the Move Data Wizard!
[15956] 120907.170308.6376: Wizard: Admin:QueryNextPage(null) = Storage.MoveDataWizard.GettingStartedPage
[15956] 120907.170308.6396: Wizard: TOC Storage.MoveDataWizard.GettingStartedPage is on ExpectedPath
[15956] 120907.170308.6546: Wizard: Storage.MoveDataWizard.GettingStartedPage entered
[15956] 120907.170308.6626: Wizard: Admin:QueryNextPage(Storage.MoveDataWizard.GettingStartedPage) = Storage.MoveDataWizard.DiagnoseDataStorePage
[15956] 120907.170308.6626: Wizard: TOC Storage.MoveDataWizard.DiagnoseDataStorePage is on ExpectedPath
[15956] 120907.170308.6626: Wizard: Admin:QueryNextPage(Storage.MoveDataWizard.DiagnoseDataStorePage) = Storage.MoveDataWizard.NewDataStoreLocationPage
[15956] 120907.170308.6626: Wizard: TOC Storage.MoveDataWizard.NewDataStoreLocationPage is on ExpectedPath
[15956] 120907.170308.6626: Wizard: Admin:QueryNextPage(Storage.MoveDataWizard.NewDataStoreLocationPage) = null
[15956] 120907.170308.6666: Wizard: ----------------------------------
[15956] 120907.170308.6666: Wizard: The pages visted:
[15956] 120907.170308.6666: Wizard: Current Page := [TOC Storage.MoveDataWizard.GettingStartedPage]
[15956] 120907.170308.6666: Wizard: [TOC]        : TOC Storage.MoveDataWizard.DiagnoseDataStorePage
[15956] 120907.170308.6666: Wizard: [TOC]        : TOC Storage.MoveDataWizard.NewDataStoreLocationPage
[15956] 120907.170308.6666: Wizard: Step 1 of 3
[15956] 120907.170310.4021: Wizard: Admin:QueryNextPage(Storage.MoveDataWizard.GettingStartedPage) = Storage.MoveDataWizard.DiagnoseDataStorePage
[15956] 120907.170310.4031: Wizard: Storage.MoveDataWizard.GettingStartedPage exited with the button: Next
[15956] 120907.170310.4031: WizardChainEngine Next Clicked: Going to page {0}.: Storage.MoveDataWizard.DiagnoseDataStorePage
[15956] 120907.170310.4101: Wizard: Storage.MoveDataWizard.DiagnoseDataStorePage entered
[15956] 120907.170310.4151: Wizard: Admin:QueryNextPage(Storage.MoveDataWizard.DiagnoseDataStorePage) = Storage.MoveDataWizard.NewDataStoreLocationPage
[15956] 120907.170310.4151: Wizard: Admin:QueryNextPage(Storage.MoveDataWizard.NewDataStoreLocationPage) = null
[15956] 120907.170310.4151: Wizard: ----------------------------------
[15956] 120907.170310.4151: Wizard: The pages visted:
[15956] 120907.170310.4151: Wizard: [TOC] visited: TOC Storage.MoveDataWizard.GettingStartedPage
[15956] 120907.170310.4151: Wizard: Current Page := [TOC Storage.MoveDataWizard.DiagnoseDataStorePage]
[15956] 120907.170310.4151: Wizard: [TOC]        : TOC Storage.MoveDataWizard.NewDataStoreLocationPage
[15956] 120907.170310.4151: Wizard: Step 2 of 3
[5416] 120907.170310.4191: Storage: Starting System Diagnosis
[5416] 120907.170310.4191: Storage: Getting Data Store Information
[5416] 120907.170310.4541: Storage: Get folder size
[5416] 120907.170311.0736: Storage: Success get Redirection folder size: 8424198899 bytes
[5416] 120907.170311.0786: Storage: Data Store Drive/s Details:Name=C:\,Size=8424198899 
[5416] 120907.170311.0786: Storage: Data Store Size Details: Current Total Size=8424198899  Required Size=8424198899
[5416] 120907.170311.0786: Storage: MoveData Task can move the Data Store=True
[5416] 120907.170311.1715: Storage: An error was encountered when performing system diagnosis : ErrorCode:0
BaseException: Microsoft.WindowsServerSolutions.Storage.Common.StorageException: WMI error occurred while accessing drive ---> System.Management.ManagementException: Not found 
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
   at Microsoft.WindowsServerSolutions.Storage.Common.DriveUtil.IsDriveRemovable(String drive)
   --- End of inner exception stack trace ---
   at Microsoft.WindowsServerSolutions.Storage.Common.DriveUtil.IsDriveRemovable(String drive)
   at Microsoft.WindowsServerSolutions.Storage.Common.DataStoreInfo.LoadAvailableDrives()
   at Microsoft.WindowsServerSolutions.Storage.Common.MoveDataUtil.CanMoveData(DataStoreInfo storeInfo, MoveDataError& error)
   at Microsoft.WindowsServerSolutions.Storage.MoveData.DiagnoseDataStorePagePresenter.DiagnoseDataStore(Object sender, DoWorkEventArgs args) 
[15956] 120907.170311.1795: Storage: An error occured during the execution: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> ErrorCode:0
BaseException: Microsoft.WindowsServerSolutions.Storage.Common.StorageException: Diagnosing the Data Store failed (see the inner exception) ---> ErrorCode:0
BaseException: Microsoft.WindowsServerSolutions.Storage.Common.StorageException: WMI error occurred while accessing drive ---> System.Management.ManagementException: Not found 
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
   at Microsoft.WindowsServerSolutions.Storage.Common.DriveUtil.IsDriveRemovable(String drive)
   --- End of inner exception stack trace ---
   at Microsoft.WindowsServerSolutions.Storage.Common.DriveUtil.IsDriveRemovable(String drive)
   at Microsoft.WindowsServerSolutions.Storage.Common.DataStoreInfo.LoadAvailableDrives()
   at Microsoft.WindowsServerSolutions.Storage.Common.MoveDataUtil.CanMoveData(DataStoreInfo storeInfo, MoveDataError& error)
   at Microsoft.WindowsServerSolutions.Storage.MoveData.DiagnoseDataStorePagePresenter.DiagnoseDataStore(Object sender, DoWorkEventArgs args)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
   --- End of inner exception stack trace ---
   at Microsoft.WindowsServerSolutions.Storage.MoveData.DiagnoseDataStorePagePresenter.backgroundWorker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& 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.Common.Wizards.Framework.WizardChainEngine.Launch()
   at Microsoft.WindowsServerSolutions.Storage.MoveData.MainClass.LaunchMoveDataWizard()
   at Microsoft.WindowsServerSolutions.Storage.MoveData.MainClass.Main(String[] args)

Thanks in advance

SBS 2008: Exchange 2007 SP won't install

0
0

I have been trying to install Exchange 2007 SP3 on our SBS 2008, and it keeps failing the readiness checks, saying "a reboot is pending from a previous install, please restart and try again." I have rebooted several times and continue to get the same results. I can't find anything in the event logs that would give me any clues. Has anyone else seen this issue?

Exchange is still at SP1, I had been wrongly thinking WSUS was taking care of SPs. I also tried to do SP2 with the SBS install tool, but it got the same results.

Thanks,

Dave

sbs 2011 fax service crashes every now and then

0
0

on a sbs 2011 server we keeping getting where the fax service crashes every now and then
We are receiving faxes to a mail enabled public folder but then it sometimes crashes and then the fax sits in the queue

In the event log there are 5 errors listed

I have tried whats listed here
http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver2011essentials/thread/d7cc65c5-3e48-49f9-b3c1-d41799c0a98f

 

1
event id 32108 microsoft fax
The Fax Service encountered a problem and needed to close.
 Error Code: 0x00000000
 This error code indicates the cause of the error.
 A Windows Error Report was generated with full details about the problem.
 The Fax service will restart now.

2
event id 1026 .net runtime
Application: fxssvc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 000007FEBE15D278

3
event id 1000 application error
Faulting application name: fxssvc.exe, version: 6.1.7601.17514, time stamp: 0x4ce7b339
Faulting module name: INETCOMM.dll_unloaded, version: 0.0.0.0, time stamp: 0x4dbf9046
Exception code: 0xc0000005
Fault offset: 0x000007febe15d278
Faulting process id: 0x5974
Faulting application start time: 0x01cd8b80a776324a
Faulting application path: C:\Windows\system32\fxssvc.exe
Faulting module path: INETCOMM.dll
Report Id: aa30a090-f77d-11e1-ae2d-9c8e992fdeb5

4
event id 1001 windows error reporting
Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: fxssvc.exe
P2: 6.1.7601.17514
P3: 4ce7b339
P4: INETCOMM.dll_unloaded
P5: 0.0.0.0
P6: 4dbf9046
P7: 000007febe15d278
P8: c0000005
P9: 0000000000000008
P10:

Attached files:
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WER4A41.tmp.appcompat.txt
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WER4B5B.tmp.WERInternalMetadata.xml
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WER4B6C.tmp.hdmp
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WER6C83.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_fxssvc.exe_613ed4b01120e2cd59fff986b97a801d13dbdadb_cab_6f886e26

Analysis symbol:
Rechecking for solution: 0
Report Id: aa30a090-f77d-11e1-ae2d-9c8e992fdeb5
Report Status: 4

5
event id 1001 windows error reporting
Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: fxssvc.exe
P2: 6.1.7601.17514
P3: 4ce7b339
P4: INETCOMM.dll_unloaded
P5: 0.0.0.0
P6: 4dbf9046
P7: 000007febe15d278
P8: c0000005
P9: 0000000000000008
P10:

Attached files:
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WER4A41.tmp.appcompat.txt
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WER4B5B.tmp.WERInternalMetadata.xml
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WER4B6C.tmp.hdmp
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WER6C83.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_fxssvc.exe_613ed4b01120e2cd59fff986b97a801d13dbdadb_cab_6f886e26

Analysis symbol:
Rechecking for solution: 0
Report Id: aa30a090-f77d-11e1-ae2d-9c8e992fdeb5
Report Status: 0

SharePoint Foundation Error 5767 on SBS 2011

0
0

This error occured in the SBS 2011 Application event log. The server has been running about 2 weeks and I don't remember seeing this error before. I can't find any information on the error and wondered if someone might have suggestions. I have not changed any of the installed accounts manually.

SharePoint Foundation 5767 4/18/2011 12:01:21 PM   Event Details:
Error updating the account password for process identity Id 6e8958d6-8348-45e4-b5b9-a9a3e8364e56, please fix manually. An object of the type Microsoft.SharePoint.Administration.SPWindowsServiceCredentialDeploymentJobDefinition named "windows-service-credentials-SPUserCodeV4" already exists under the parent Microsoft.SharePoint.Administration.SPUserCodeService named "SPUserCodeV4". Rename your object or delete the existing object.

Error MBCA analyzer

0
0

I am trying to migrate a 2003 Server to SBS2011, and I am running into a problem with the Baseline configuration analyzer.

It reports an error:

Migration will fail without fixing this issue. Go to http://bemis.partners.extranet.microsoft.com/2578426 for more details.

When I try to follow the link, I am asked for a UserID and Password. I have no idea who "bemis" is and how I would gt a UserID or password.

Thanks for your help.

Backup disks showing having corruption in Event Log

0
0

I have an SBS 08 server with the System Log containing Event 55 NTFS errors pertaining to the backup disk. Since the disk doesn't have a drive letter due to being used by Windows Server Backup there is no way to run the recommeded chkdsk on it.

Any suggestions as to how to handle this?


Jonathan


SBS 2003 missing service pack 1

0
0

I have a server I am wanting to do a migration with from 2003 to 2011, the best practice analyzer gives me the following errors 

- Windows SBS 2003 Service pack 1 not installed 

- POP3 Connector has not been updated 

From what I can see service pack one was not installed causing this issue. 

I have read other feeds about similar situations, people have said that you can install sp1 after sp2 but no one has confirmed that it works or exactly how to do it. 

The backups are failing so I am scared about doing anything until I know for sure.

Thanks. 

Can not delete email using OWA in SBS11 after applying steps in SBS Best Practices Analyzer

0
0

This is a SBS11 server migrated from SBS2003. The server is at SP1, Exchange is version 14.1 (Build 218.15), which is SP1 with no rollups installed (as reported from EMS using: get-exchangeserver | fl name,edition,admindisplayversion). Two weeks ago I started applying the recommendations from Best Practices Analyzer as we have made some revisions especially to Exchange, such as increasing incoming and outgoing message size limits. There was also a warning about having an empty server listing in Exchange which was fixed with directions by Using ADSI Edit to remove the 'empty' server listing still existing from the orginal migration from SBS2003.

Today, while being remote from my desk, I was using OWA and found that messages were being sent and received within OWA, I could not not delete or move messages; I received a warning "An unexpected error occurred and your requested couldn't be handled". The last time I used OWA (three weeks or so ago), it worked as expected, meaning I could delete messages in OWA with no problem. Outlook attached to the internal Exchange server works normally.

I have read the one other listing about the unexpected error when using OWA but was not certain of the path I should follow. I suspect this issue actually started after applying the items cited in the Best Practices Analyzer as there have been no updates or other changes to the server since then.


Best Regards, Mark

Client mail lost on a new laptop

0
0

I just replaced one of my domain users computer with a new one. On the old laptop, he uses outlook to connect to exchange 2010 and read mails fine. I changed his computer for a newer one and he can't read any of his mails. When I send him test mail he get and can reply, however he can't read any of the previous mail.

Can anyone explain to me the why that happened?

I will be changing another user's computer very soon, how do I backup a single user's mail and restore it in case the same problem occurs again. I'm using Exchange 2010 build 14.01.0393.000 


DCOM Errors

0
0

I am getting large numbers of DCOM 10009 & errors on our SBS 2008 server. Many of them are related to my desktop PC which is running Windows XP. I have looked in the event log on this pc and see lots of NetLogon 5789 errors: Attempt to update DNS Host Name of the computer object in Active Directory failed. The updated value was 'HARVEST-PALE'. The following error occurred: The parameter is incorrect. 

I followed the link to the Help & Support Centre which suggests to check DNS settings, whicvh all look OK (network card is set to automatically determine DNS).

It also suggests to run DCDIAG, so I have downloaded and installed the Windows Server 2003 support tools and run this.

This displays the following error:    ***Error: HARVEST-PALE is not a DC.  Must specify /s:<Domain Controller> or   /n:<Naming Context> or nothing to use the local machine.

So I ran it again with the /s switch specifying the server name. It seems to run lots of tests, all which pass except the systemlog test which generates a long list of the following error repeated many times: 

         An Error Event occured.  EventID: 0xC0002719
            Time Generated: 09/10/2012   09:35:01
            (Event String could not be retrieved)

SBS 2011 Standard Wireless Internet Connection

0
0
I am trying to connect to the internet wirelessly and not sure it is possible with SBS. First off I am having trouble just getting the wireless adapter installed on the computer. So question 1 is whether there is a wireless card that works with SBS 2011? The one I nstalled gives me an error that the Wplani.dll file is not installed. If so will I be able to connect this way, or do I have to be direct connect by ethernet?
Viewing all 8539 articles
Browse latest View live


Latest Images