Tag Archives: Error

SQL Server Database Error: 661

One of my customers had an issue where they failed to open a connection to a particular database they had been testing. The error read: ‘the database e:\somepath\somefolder\jermsmit.mdf’ cannot be opened because it is version 611. The server supports version 655 and earlier. A downgrade path is not supported.

This issue is caused because you are not permitted to use a database from a later release on an earlier system. i.e they are not backwards compatible

Problem: Databases created under a newer version of SQL Server are not compatible with previous versions of SQL Server

Solution(s) that I am aware of in this case:

  • You need to either upgrade your SQL Server instance to the same version as the database or one newer
  • Or copy out the data in that database into an earlier version (using the data migration wizard perhaps)

If you need to know the version of your source and destination databases use the following query:

SELECT @@VERSION

The destination should be the same level or greater in in version.

Best of luck to ya

Issue: Outlook Address Book Not Updating

Symptoms:

New users added to Exchange 2010 do not show up in global address book

Tests Performed:

1. Searched for new users from Outlook – This failed
2. Searched for new users from OWA – This works
3. Put Outlook in non-cached mode and searched – this worked

Suspected Problem:

Offline Address Book Generation is not happening – Possible cause, resources (memory) on host server, service failure.

Steps Taken: *note* I have seen this before so I know where I am looking first

1. Stop the Microsoft Exchange File Distribution Service

2. Stop the Microsoft Exchange Address Book

3. Clear the files from ‘C:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB’ putting them into a backup folder of some sort.

4. Restart the services above.

5. To get the OAM to immediately generate run the following command: Update-OfflineAddressbook “name of offline address book”. You may encounter an issue stating that the System Attendant Service is not running or you do not have permission. 1. Make sure you are running the Exchange Management Shell as Administrator and 2. The System Attendant Service is running. *note* The Service is named “Microsoft Exchange System Attendant”.

6. You will now notice that the GUIDS and files have started to populate under \ExchangeOAB\ folder

Follow-up Testing that things now work:

1. Exit Outlook and delete the Offline Address Book cache from ‘C:\Users\%user profile%\AppData\Local\Microsoft\Outlook\Offline Address Books’

2. Open outlook again cache should repopulate at this point.

3. Open a new email message or click the Address Book and search for the person(s) who were not showing previously.

Conclusion:

The Outlook Client failed to download an updated copy of the Offline Address Book because the services have stopped functioning. I was unable to obtain errors in the event logs regarding this, however having experienced this in the past it has become suspect

- For Darlene

MapiException: TooManyMountedDatabases when mounting database

I was hit with a nice error when attempting to mount several Exchange databases on my new Exchange 2010 SP2 server that I had setup in a lab envionment for production testing.

The error:

——————————————————–Microsoft Exchange Error——————————————————–
Failed to mount database ‘IJ’.IJFailedError:Couldn’t mount the database that you specified. Specified database: IJ; Error code: An Active Manager operation failed. Error The database action failed. Error: Operation failed with message: MapiExceptionTooManyMountedDatabases: Unable to mount database. (hr=0x8004060e, ec=-2147219954). [Database: IJ, Server: EXCHANGE.JERMSMIT.LOCAL].An Active Manager operation failed. Error The database action failed. Error: Operation failed with message: MapiExceptionTooManyMountedDatabases: Unable to mount database. (hr=0x8004060e, ec=-2147219954). [Database: IJ, Server: EXCHANGE.JERMSMIT.LOCAL]An Active Manager operation failed. Error Operation failed with message: MapiExceptionTooManyMountedDatabases: Unable to mount database. (hr=0x8004060e, ec=-2147219954). [Server: EXCHANGE.JERMSMIT.LOCAL]MapiExceptionTooManyMountedDatabases: Unable to mount database. (hr=0x8004060e, ec=-2147219954)
——————————————————–OK——————————————————–

The cause of this issue is because Unlicensed (trial) of Exchange 2010 servers are limited to 5 databases. In the Application event log I noticed the following message:

Event ID: 9591 – Exceeded the max number of 5 MDBs on this server.

It seems I have exceeded the number of databases that can be mounted during my trail. I will now apply a MSDN license and see how things work out.

 

 

 

[SOLVED] Segmentation faulty tree…

I had this issue where I could not install anything new in my Ubuntu server. After some searching I come to lean that the packages cache seemed to be corrupted

# symptom is something such as this
root@media:~# apt-get update
root@media:~# apt-get install htop

Reading package lists… Done
Segmentation faulty tree… 50%

# and this is what fixed the problem
# you need to be as root or su into root
sudo rm /var/cache/apt/*.bin

I am happy again.

PlayStation Network Down (Again)

It would seem once again Sony’s PlayStation Network is down again. After trying many of the online tips and even going as far as to boot my router (problem is so not my router) this issue persists.

It seems that Sony has responded to the issue and acknowledges there are ongoing problems, but offer not details to what this problem is or an ETA for its resolution.  Even attempts to log into their website indicate they are under some site maintenance and the server (WHAT SERVER) is down.

The error code provided on the console “80710A06” also uninformative.

 

Update 1: PSN is acknowledging on its EU blog that the network outage may be a result of “the possibility of targeted behavior by an outside party.” Still no ETA for when services will be restored.

Update 2: PSN is now reporting that the network may be offline for “a full day or two.”

 

Sony PlayStation Error 80710B20

It seems Sony’s PlayStation Network is once again down.   This morning I was not able to get online “Error 80710B20″ when I attempted to log into my PlayStation Account.  For now its unknown as to why this is happening.  All support steps provided have failed me.  I will update this post with new info I find.  For now I am game-less.

Thanks Sony, for messing up my free time.

 

— Update

So, after keeping my PlayStation off for about 10 minutes and attempting to log in the problem seems to have resolved itself.

How I got my eth0 back

After a recent Ubuntu Linux (server) installation inside in a virtual machine, I decided to move the virtual machine to new a new host where I can run it.  After the move I noticed that I could no longer connect to my system via the IP I had assigned.  So the story begins.

With the discovery that I no longer had network connectivity, I did an ‘ifconfig’ and noticed that my eth0 was missing.  So, I tried to force it to start by issuing the command ‘ifup eth0’ and go the following error:

eth0: ERROR while getting interface flags: No such device…
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth0

I did some searching, as I have run into this issue in my past and could not remember for the life of me what I needed to do to correct this problem (the right way).  The method I used in the past was to edit /etc/network/interfaces and change iface eth0 inet (static or dhcp) to eth1  This would change my static or dynamic settings to use the new interface…  This is not what I wanted to; “lazy admin approach”.

What I did do is… wait! Here is some background info:  When a Virtual Machine starts up, it generates a new MAC address and a new UUID for the guest system. My system had already known of a MAC address and thus made a new one.

Back to what I did to correct my problem

Locating the file /etc/udev/rules.d/70-persistent-net.rules, I removed the former MAC address info and modified the new one, changing the existing eth1 to eth0, and issued a restart

Example:
# PCI device 0×8086:0x100f (e1000)
SUBSYSTEM==”net”, DRIVERS==”?*”, ATTRS{address}=”[bad mac]“, NAME=”eth0″