Symantec Backup Exec 2010 R3 SP3 – There was a problem running the DBCC

When backing up SQL databases you might get the following error message.

V-79-57344-65085 - There was a problem running the DBCC.

DBCC results for “Database”

To resolve the error take the following steps.

1. Connect to SQL Management Studio

2. Run manual SQL backups on the Database in question

3.  Right click Database and select “new query”

4. Type the below commands exactly as is. It will only scan the Database and report what is wrong with it.

Use dfin_mac_live


5. In my case it was a table miss match and the report said I should run DBCC UPDATEUSAGE

6. I created a new query with the following details:


After this my Backups completed successfully again.




Configure your windows pc as a Wireless Access Point

I found the interesting post on how to configure your computer to serve as a wireless access point.


1. Open command prompt as administrator
2. netsh wlan show drivers Look for Wifi driver – find ‘Hosted network supported’ – if Yes, then OK
3. netsh wlan set hostednetwork mode=allow ssid=your_chosen_ssidkey=8_or_more_character_key
4. netsh wlan start hostednetwork
5. Go to network and sharing center –> Change adapter settings. Right click your internet connected adapter and go to properties. Click the sharing tab. Check the ‘allow other network users to connect through this computer’s internet connection.

Create a shortcut to the command in step 4 preceeded by ‘cmd.exe /c ‘ and stick on the desktop or wherever to make it easier to start the hotspot after rebooting. Remember to change the shortcut properties (advanced) to run as administrator. To stop the hotspot, replace start in step 4 with stop.

Exchange SMTP connectors

Exchange 2007/2010 to 2010 migration  =  Don’t need to create new SMTP connector in Exchange 2010 – Just add Exchange 2010 as source server and after migration remove old server as source.


Exchange 2003 to 2010 migration = Need to create new SMTP connector on Exchange 2010 server.


You will receive the below error when you try to the add the new Exchange 2010 server to the SMTP connector that already exists in Exchange 2003 (In Exchange 2010 EMC). Exchange 2010 doesn’t recognize the 2003 SMTP connector so a new connector has to be created.

Enable Powershell remoting and connect

I’ve had to search around a bit to find all the commands to enable remotely connecting to Server 2012 using powershell.

#To enable remote connections on the server:


#To connect remotely from your workstation

Enter-PSSession -computername Server_Name -Credential administrator

Remember you have to use the server name and not the IP address otherwise it will deny you access.




Error when trying to promote DC – Failed to configure the service NETLOGON as requested “The wait operation timed out”


The following resolution steps can be taken should you receive this error.

  • Changed DNS on local network adaptor – Enter IP of another DNS server (Don’t put local IP as DNS).
  • Check entries in DNS server and remove A records of server you are trying to promote (Might have legacy records if it was a DC before).
  • Run dcpromo while Netlogon service is stopped
  • Import registry setting from working DC for netlogon
  • Rename netlogon files and restart netlogon service
  • Ensure time is correct – Compare to working DC’s
  • Stopped any services that might be using the Netlogon service
  • Uninstall DNS from the server you are trying to promote

Important things to note on Exchange 2013

  • Can’t migrate from Exchange 2003 directly to Exchange 2013.
  • You need SP3 installed for Exchange 2010 and latest roll up update for Exchange 2007 when migrating to Exchange 2013.
  • Can run on Server 2008 R2
    • Need more pre-requisites installed compared to Server 2012
  • No longer 5 roles – Broken down to Client access and Mailbox role.
    • Unified messaging included in mailbox role.
    • Currently no Edge server but Exchange 2010 Edge server can be used with Exchange 2013.
  • Only 50 databases can be mounted on a mailbox server – Exchange 2010 could mount up to 100.
  • Public folders are no longer replicated in multi-site environment. It will be located in one location.
  • Exchange 2013 is much less resource intensive with regards to IOPS on disks, so cheaper disks can be used for your Exchange server. There is approximately a 99% IOPS reduction compared to Exchange 2003.
  • Web App now can now be used offline.
  • Built-in anti-malware (Previously only anti-spam).
  • Automatic failover to DR site.