Translate

18/11/09

How to troubleshoot issues with a Robotic Library (autoloader/changer) or Tape Drive in Backup Exec for Windows Servers



Backup Exec for Windows Servers includes support for a wide array of robotic libraries (also referred to as an autoloader or changer) and tape drives. Prior to proceeding with the rest of this document, confirm that the tape hardware is listed on the Hardware Compatibility List (HCL) for the version of Backup Exec which is installed per the following link:

 http://www.symantec.com/business/support/documentation.jsp?language=english&view=comp&pid=15047

Note:  Tape Hardware which is not listed on the HCL may be detected by or function with Backup Exec, but may not have been tested and is not officially supported by Symantec.

Occasionally, hardware which has been officially tested and is supported by Symantec may not be displayed or may appear offline in the Backup Exec Interface (i.e.: Devices Tab), may not function correctly, or may report specific errors in the job log or Windows Event Viewer Log. This document has several suggestions on how to potentially resolve these issues.


Please note:  Some hardware manufacturers may have implementation and troubleshooting documentation available that have more detailed information for particular device than what is listed below. The following are examples of this:

HP StorageWorks Enterprise Backup Solution with Symantec Backup Exec implementation guide
 http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00097075/c00097075.pdf

Dell Solution Network: Step-by-Step Troubleshooting Wizard for Tape Drives

Please make sure to review the hardware manufacturer's documentation and if there are still issues after doing so and performing the steps below, open a support case with the hardware manufacturer to confirm that the tape hardware is functioning properly.

Basic Configuration and Troubleshooting Procedures:

I. Verify the hardware is detected properly by the Operating System and not being managed by another third party application

a. Open the Device Manager in Windows and verify the hardware is present. Verify the controller, tape drive(s), and robotic library (if applicable, will need to show as an Unknown Medium Changer) are present in Windows Device Manager:

In Windows 2003, right click My Computer and choose Manage. From the Computer Management snap-in, click on Device Manager (Figure 1).

Figure 1

 

In Windows 2008, right-click Computer and choose Manage. From the Server Management snap-in, expand Diagnostics and click on Device Manager (Figure 2).


Figure 2

 

b. Confirm that the Removable Storage Management (<RSM>) service is stopped and disabled.  If a Removable Storage Service Error (RSM cannot manage library or tape device. The database is corrupt.) shows afterward in the System Event Viewer Log, this error can usually be ignored and will stop occurring after one or more reboots of the server have been performed.
c. Check the installed programs in the Windows Control Panel, Add/Remove Programs Applet.  If there are any other third party backup applications, tape tools, etc...  un-install them.  Backup Exec may not be able properly communicate with tape hardware if another vendor's backup application is installed, even if the services for that application are disabled.  Tape Diagnostic Tools should only be installed to test the tape hardware when the Backup Exec Services are not running and then should be removed once the diagnostic tests have been completed.

II. Verify Robotic Library Support is enabled and the latest Backup Exec Tape Device Drivers have been installed

a. In the Backup Exec console click on Tools > Serial Numbers and Installation.  In the installation wizard go past the serial numbers screen and verify that the Enable Robotic Library Support option is selected and installed.

 

If the option is not selected, select the option and proceed with the installation.

b. Ensure that the latest drivers and firmware have been installed for the tape drive, robotic library, and for the SCSI controller. Symantec drivers should be loaded for the tape drive for best performance. Symantec does not test performance or compatibility with Original Equipment Manufacturer (OEM) drivers, unless noted on the Hardware Compatibility List. Backup Exec tape drivers can be downloaded from the Symantec Support Web site at:    http://www.symantec.com/business/support/downloads.jsp?pid=15047

Select the appropriate Backup Exec version number in the Product Version drop-down box, and select Driver as the File Type. Contact the hardware manufacturer for the latest firmware for the robotic library, tape drive, and SCSI controller. To verify that the Symantec Drivers have been loaded for the tape drive, return to Device Manager in Windows and open the properties of the Tape Drive. Verify that the Driver Provider is Symantec.

III. Confirm the tape hardware is properly configured, powered on, detected, & initialized prior to the Windows Operating System booting up

a. If the tape hardware is external to the server, power down the robotic library, tape drive, and server.

b. Verify that the device is configured to use the proper addressing scheme.

For robotic libraries, verify that the addressing scheme is set properly between the drives and the robotic library:

  • SCSI ID. If the library and/or drives support SCSI ID addressing, then verify that the library has a lower SCSI ID than the tape drives.
  • Multi-LUN. If the library and/or drives support Multi-LUN addressing, then verify that the drives have a lower LUN number than the library.

For more information on verifying the addressing scheme for the hardware, see the Related Documents or consult your hardware documentation.

c. Verify that the autoloader's media management is set to Random.  

  • If the library is detected, but there are issues with moving or managing media, verify that the library is in Random and not Sequential or Stacker mode. Consult the hardware documentation for configuring this setting

d. Power on the robotic library and/or tape drive. Once the autoloader or tape drive has fully initialized, power the server back on.

Note 1:  Anytime Backup Exec goes from being to able to properly detect or communicate with externally connected tape hardware to not being able to manage it, the procedure above should be repeated.  Even if the Windows Device Manager detects the hardware after hard reboots, warm reboots, or because the library is disconnected or the power is cycled to the device, Backup Exec still may have communication issues with it.  It is also recommended that the tape hardware be plugged into a backup power supply with surge suppression, just as the server or workstation it is connected to should be.

Note 2:  Additional power on procedure steps may be required for tape hardware which is in a SAN (Storage Area Network) Environment because of switch, bridge, etc... equipment which is also involved.

Note 3:  If the tape drive, medium changer, or controller is listed with an error or is not listed in Device Manager after performing the steps listed above, then consult the hardware documentation to verify the hardware is connected/terminated to the server properly. Verify also the controller can detect the device properly POST Bios Screen on boot-up and by booting into the controller BIOS. For further support contact the hardware vendor.

IV. Review the System Event Logs for hardware errors.

While in the Computer Management or the Server Management console, review the System Event Logs and see if there are any hardware errors being reported from the tape drive, robotic library, or controller cards.  This is recommended even if the tape hardware is detected by Backup Exec/Windows and appears to be functioning properly.

The following are examples of hardware errors that might be present in the System Event Logs:

  • Event ID 5: Signifies SCSI parity errors. This can be caused by a faulty SCSI card or faulty SCSI termination. If these errors occur, contact the hardware manufacturer.

  • Event ID 7: Signifies bad blocks. This could be the result of a outdated tape device driver issue, faulty media, or dirty read/write heads on the tape drive. Update to the latest Backup Exec Tape Device Drivers, run a cleaning job and replace the media with new media if possible. If the issue continues with new media, please contact the hardware vendor.

  • Event ID 9: Signifies SCSI bus timeouts. These errors usually occur when the SCSI bus resets itself, or the SCSI hardware does not respond in a timely fashion. Sometimes slowing the SCSI bus down can resolve these issues, as well as installing the latest SCSI drivers and firmware.  Another device on the same cable can cause the issue too.  In certain high end servers, moving the SCSI card to a different Peripheral Component Interconnect (PCI) slot, one that does not share the same bus as a RAID controller, has been known to fix these errors. If these errors occur, contact the hardware manufacturer.

  • Event ID 11: Signifies controller errors. These errors are generally caused by hardware that is not functioning correctly. Attempting to slow the SCSI bus down and verifying that the latest SCSI drivers and firmware are loaded can sometimes resolve these issues. If these errors occur, contact the hardware manufacturer.

  • Event ID 15: Signifies the device is not ready for access. These errors usually occur when the device is malfunctioning or configured incorrectly. They may also occur if the incorrect drivers are loaded, or the drivers are not up to date. If these errors occur, contact the hardware manufacturer.


Advanced Troubleshooting Procedures:

V. Verify the device configuration is supported by Backup Exec

a. Verify that the inquiry string matches the Hardware Compatibility List (HCL)

If the device is presenting itself properly to the operating system, then it should be supplying the operating system with an inquiry string.

In order for the device to work properly within Backup Exec, the inquiry string the device provides must match exactly with what is documented on the HCL:  http://entsupport.symantec.com/carveout_PID_15047_view_CL.htm

The inquiry string can be found in two different places:

1. The ADAMM.LOG file:

The adamm.log file is located in x:\Program Files\Symantec\Backup Exec\. Open this log file using a text editor such as Notepad, and scroll to the end of the log file.  The adamm.log file is appended to each time the Backup Exec services are started, and the detailed information for each device is outputted to this log during a process called Device Discovery.

Below is example output from a Device Discovery (Figure 3):

Figure 3:

 

The above shows a single tape drive (Tape0) and a robotic library (MediumChanger0). The Inquiry String for the tape drive is QUANTUM SDLT320, and it is using firmware version 2E2E. The robotic library has an inquiry string of QUANTUM UHDL and is using firmware version 0016.

2. The DEVICEMAP registry:

The Inquiry String, as well as most of the Device Discovery information, can also be found in the DEVICEMAP portion of the SCSI Registry:

HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port #\Scsi Bus #\Target Id #\Logical Unit Id #\

The SCSI Port, SCSI Bus, SCSI ID (TAR), and LUN Number can be found under the SCSI Address in Device Discovery in the adamm.log file (highlighted in Figure3).

Below is the DEVICEMAP registry hive from the tape drive from the above example (Figure 4):

Figure 4:

 

NOTE: The registry settings under DEVICEMAP should not be edited, under any circumstances. These keys should be automatically populated if the hardware is configured and functioning properly.

Comparing the Inquiry Strings with the HCL:

Locate the drive and/or library on the HCL. Compare the Inquiry String found in the Step 1 or Step 2 to that what is in the HCL. The inquiry string must match exactly between the HCL and what is being reported to the server by the device.

NOTE: The ^ character in the Inquiry Strings on the HCL represents the number of spaces that are expected in the actual Inquiry String.

The following is from the HCL for the above device (Figure 5):

Figure 5:

 

NOTE: The above (Figure 5) represents a single entry on the HCL, and would be found in a single line and not on two entries.

b.Verify the connection method matches the HCL.

In addition to verifying the inquiry string, also verify that the method which the hardware is connected to the server matches what is on the HCL (SCSI, Fibre, SAS, IDE, SATA). In addition, tape drives should not be connected to RAID controllers.

Using the above example (Figure 5), this device is supported when connected via SCSI.

NOTE: There are many devices that support multiple connection methods. In such examples, the device would be listed twice on the HCL. If the device supports a connection method that is not listed on the HCL, then it is possible that the device has not been tested for such a connection and therefore support will be given a limited basis. It is also possible that Symantec is in the process of qualifying the particular device for that connection method. In these cases, please open a support case with Symantec.

VI. Use tracer.exe to perform a SCSI trace while restarting the Backup Exec services.

a. Stop the Backup Exec services and launch tracer.exe from the x:\Program Files\Symantec\Backup Exec\ directory. With tracer capturing SCSI information, restart the Backup Exec services using x:\Program Files\Symantec\Backup Exec\Servicesmgr.exe. Once the services have been restarted, review the tracer log for any hardware errors or reservation conflicts.

Please see the following document for more information on capturing and reading tracer logs:

Troubleshooting hardware with the Backup Exec for Windows Servers using the SCSI Trace Utility (tracer.exe).
 http://support.veritas.com/docs/285630

If the option is not selected, select the option and proceed with the installation.

b. Verify that the SCSIChanger service is started.

If the library is not detected, and robotic library support is enabled, verify that the SCSIChanger service has been started. Click on Start > Run and type msinfo32 and hit enter. Expand out Software Environment and the click on System Drivers. Scroll down and find the SCSIChanger service and verify that it is started (Figure 6):

Figure 6:

 

If the SCSIChanger service is not started, or listed, then uninstall the Enable Robotic Library support option and then reinstall it.


VII. Orphaned Devices in Windows Device Manager and/or devices no longer detected or offline in Backup Exec

Please see the following document for how to check for orphaned devices in Windows Device Manager:

How to remove old tape drivers from Windows that are no longer needed or in use.
 http://support.veritas.com/docs/308914

It is quite possible that an orphaned devices may be present in Device Manager, especially after replacing hardware, or performing a firmware or driver update. Verify that there are no orphaned tape drives, medium changers, or controllers.

Remove any orphaned device(s) to eliminate any potential conflict.

VIII. Disable, delete and re-enable the device in Backup Exec

From the devices tab in Backup Exec, right-click the device and select Enable. This should remove the check mark next to the device and disable it. After disabling the device, right-click the device again, this time choosing delete.

NOTE:  During the delete process you may be prompted to re-target your backup jobs to other devices or device pools. Please be mindful of the jobs to be re-targeted and remember to change the jobs back after resolving the hardware issue.

After deleting the device(s), stop the Backup Exec services. With the services stopped, run Tapeinst.exe from x:\Program Files\Symantec\Backup Exec\. Choose the following options (Figure 8):

Figure 8:

 

Tracer.exe should also be running at this time as indicated in step #4 to review for any SCSI errors. Restart the Backup Exec services, and see if the devices are detected properly.

IX. Verify that the Device and Media Service is running under a Domain Admin account and/or built-in Administrator Account

If the media server is part of a domain, the Backup Exec Device and Media Service, in addition to all the Backup Exec Services (except the Remote Agent Service) should be using an account with Domain Admin privileges and/or built in Administrator Rights. Please see the Backup Exec Administrator's Guide for further information regarding the required rights for the Backup Exec services account.

For additional troubleshooting information, please refer to the TechNotes in the Related Documents Section below.

This document is also available in the following languages:
French:

Related Documents:

322812: Reviewing hardware configuration on Backup Exec for Windows Media Servers using TILDBG.TXT
 http://support.veritas.com/docs/322812


190653: How to enable BIOS Multiple LUN (Logical Unit Number) support for an Adaptec SCSI Card
 http://support.veritas.com/docs/190653


191158: How to resolve SCSI bus timeouts
 http://support.veritas.com/docs/191158


191694: The error message "Error on a request to space to end of data. The request could not be performed because of an I/O error" is reported in Symantec Backup Exec for Windows Servers (BEWS) when attempting any tape media operation.
 http://support.veritas.com/docs/191694


231488: Reasons why the data throughput rate can be slower than the theoretical maximum when backing up to or restoring from tape media or disk (B2D) & how to troubleshoot or improve backup performance
 http://support.veritas.com/docs/231488


237047: How to resolve hardware communication/detection issues with Backup Exec
 http://support.veritas.com/docs/237047


241684: Event ID 7 is generated in the System Event log when performing a media operation on a tape device.
 http://support.veritas.com/docs/241684


241706: Advanced Autoloader Support and Troubleshooting Guide for VERITAS Backup Exec (tm) on Windows operating systems
 http://support.veritas.com/docs/241706


251466: Where to find a list of supported devices for Backup Exec for Windows Servers and the latest drivers for supported tape drives and robotic libraries
 http://support.veritas.com/docs/251466


252385: Event ID 58053: "The robotic library hardware is offline! Please confirm that the robotic library hardware is powered on and properly cabled" is reported in the Event Viewer Application Log.
 http://support.veritas.com/docs/252385


255502: Unable to perform Sony or Spectralogic robotic library operations with Backup Exec for Windows Servers 9.x and above
 http://support.veritas.com/docs/255502


268942: When attempting to run an inventory, quick erase, or relabel media, job either hangs in a queued state or fails without generating a job log.
 http://support.veritas.com/docs/268942


269214: How to uninstall the Original Equipment Manufacturer driver for the medium changer in a robotic library so as to make it "Unknown medium changer"
 http://support.veritas.com/docs/269214


269712: Backup jobs hang in a running state and have to be canceled, and/or fail with "Final error: 0x456 - The media in the drive may have changed." or "Incorrect function" error.
 http://support.veritas.com/docs/269712


269843: How to manually lock or unlock a robotic library via the VERITAS Backup Exec (tm) User Interface
 http://support.veritas.com/docs/269843


270077: After ejecting and reloading the magazine in a Certance Robotic Library, Backup Exec cannot communicate with the library until the hardware is power cycled.
 http://support.veritas.com/docs/270077


275454: What is the VSD Load Table for Driver Release 45 (Backup Exec 10.0 build 5484)
 http://support.veritas.com/docs/275454


276143: Files in Service Pack, Hotfix, or Device Driver Installer (DDI) would revert to the original revision
 http://support.veritas.com/docs/276143


277425: Inventory, Lock, Unlock, Label, & Erase jobs do not run against a Robotic Library and "Ready; No Idle Devices are available" shows in the Job Monitor if a backup job is queued and prompting for a user to insert more media.
 http://support.veritas.com/docs/277425


278111: How to configure Standalone Tape Drive/Auto loader/Library with Symantec Backup Exec for Windows Servers
 http://support.veritas.com/docs/278111


280026: Backup Exec for Windows Servers reports that "the media is bad."
 http://support.veritas.com/docs/280026


280508: A backup or restore job fails with the error "Final error: 0xe00084ed - A hardware error occurred."
 http://support.veritas.com/docs/280508


281310: A Robotic Library set to Emulation Mode is either not detected by or cannot be properly managed by the Backup Exec Software
 http://support.veritas.com/docs/281310


285630: Troubleshooting hardware with Backup Exec for Windows Servers using the SCSI Trace Utility (tracer.exe).
 http://support.veritas.com/docs/285630


285732: Event ID 15 is reported during a cleaning job
 http://support.veritas.com/docs/285732


286598: Symantec Device Driver Installer (tapeinst.exe) hangs when installing tape device drivers for Windows.
 http://support.veritas.com/docs/286598


289555: Unable to detect hardware in Backup Exec for Windows Servers (BEWS) when EMC PowerPath software is installed.
 http://support.veritas.com/docs/289555


294326: Backup Exec for Windows Servers fails to detect the tape drive
 http://support.veritas.com/docs/294326


294545: Backup job fails with the error "V-79-57344-34033 - The media in the storage device was changed"
 http://support.veritas.com/docs/294545


295508: When Backup Exec for Windows attempts to detect and communicate with an HP Autoloader, the system stops responding and has to be shutdown manually
 http://support.veritas.com/docs/295508


300454: Backup Exec for Windows Servers generates the alert "RSM database is corrupt"
 http://support.veritas.com/docs/300454


302699: Backup Exec detects libraries with multiple tape drives properly, but some of the jobs initiated fail to run
 http://support.veritas.com/docs/302699


303436: "0xe000821e - library error - incompatible storage media detected in the robotic library." occurs when attempting to backup to tape media
 http://support.veritas.com/docs/303436


303504: Why Tape Hardware Device(s) are not recognized within Backup Exec for Windows Servers
 http://support.veritas.com/docs/303504


307422: The Device Configuration Wizard does not run TapeInst.exe when a user is not the root administrator on a Windows 2008 media server.
 http://support.veritas.com/docs/307422


308027: Usage Parameters for the SCSI Tracercli.exe Utility
 http://support.veritas.com/docs/308027


308914: How to remove old tape drivers from Windows that are no longer needed or in use.
 http://support.veritas.com/docs/308914


319285: How to change Backup Exec's robotic library locking behavior
 http://support.veritas.com/docs/319285


295757: Error "connection to target system has been lost" occurs when backing up to a tape library
 http://support.veritas.com/docs/295757


315349: Incorrect function error occurs during a tape inventory if more than one type of tape drive is in an autoloader or library
 http://support.veritas.com/docs/315349


323433: "Event ID 65313: Backup Exec" appears in the Event Viewer Application Log when a Backup job is targeted to tape.
 http://support.veritas.com/docs/323433


323456: Backup Jobs to tape hang in Queued State indefinitely until canceled
 http://support.veritas.com/docs/323456


318581: Backup or restore job fails with Final error: 0xe00084ed - A hardware error has occurred.
 http://support.veritas.com/docs/318581


323364: Jobs goes to queued state and all tapes are marked as not appendable (media full) without writing data, even after running a quick erase on new tape media
 http://support.veritas.com/docs/323364


199542: Backups fail to get double the amount of the native capacity recorded to a media, even when hardware compression is being utilized, or the total byte count in the job log is higher than the maximum possible compression rate of the tape media.
 http://support.veritas.com/docs/199542


320867: LTO tape drive shows a yellow question mark on, is detected under other devices in the Windows Device Manager, and the Symantec tape device drivers cannot be loaded
 http://support.veritas.com/docs/320867


304178: BSOD with 11d 7170 sp2 which resultant of scsichng.sys and qntm3520.vsd drivers conflicting
 http://support.veritas.com/docs/304178


316894: Slow performance when backing up to the Dell RD1000 Internal Sata Drive.
 http://support.veritas.com/docs/316894


235210: How do I Identify and Troubleshoot my SCSI devices?
 http://support.veritas.com/docs/235210


322814: Viewing hardware configuration and detection using Discover.exe
 http://support.veritas.com/docs/322814


316878: Hardware Fault Errors may occur when performing operations with a tape device
 http://support.veritas.com/docs/316878


326507: Utility job complete's with exceptions and a warning message 'Library security has been compromised'
 http://support.veritas.com/docs/326507


311736: When selecting block size in the tape device properties that is greater than 64KB, the warning message "If you choose a block size that is larger than 64KB, you may not be able to restore the data." pops up
 http://support.veritas.com/docs/311736


327704: Medium Changer drivers won't bind to Emulex HBAs (Host Bus Adapters) using STORport drivers
 http://support.veritas.com/docs/327704

Supplemental Material:

System: Ref.#Description
Error Code: e00084ed A hardware error occurred
UMI: V-79-57344-34029 A hardware error occurred.
Error Code: 0000045d The request could not be performed because of an I/O device error.
Error Code: 0xe000810b Physical Volume Library Drive not found.
UMI: V-79-57344-33035 Physical Volume Library Drive not found.
Error Code: 0xe00084ed A hardware error occurred
UMI: V-79-57344-34032 The Device Timed Out
Event ID: 5 Parity errors
Event ID: 7 Bad blocks
Event ID: 9 SCSI bus timeouts
Event ID: 11 Controller errors
Event ID: 15 Device not ready
UMI: V-79-57344-57350 The Storage device reported a CRC error on a request to read/write data to/from media. This could be caused by either a dirty tape drive, bad media, or a SCSI problem.
Error Code: 0xa00084f0 The device timed out
UMI: V-79-65535-34032 The device timed out
UMI: V-79-57344-34037 Error e00084f5: The block sized being used is bad.
Error Code: e00084f5 The block sized being used is bad.
UMI: V-79-57344-34001 End of data was encountered before a set map could be located.
Error Code: e00084d1 End of data was encountered before a set map could be located.
UMI: V-79-57344-33313 Library error - the magazine is missing or not properly installed.
Error Code: 0xE0008221 Library error - the magazine is missing or not properly installed.
UMI: V-79-57344-33317 Library error - storage device is missing.
Error Code: 0xE0008225 Library error - storage device is missing.

Fuente:  http://support.veritas.com/docs/255501

Jorge.

23 comentarios:

  1. Este comentario ha sido eliminado por un administrador del blog.

    ResponderEliminar
  2. hеу therе and thank yοu for yοur info –
    I've certainly picked up anything new from right here. I did however expertise some technical points using this site, as I experienced to reload the site a lot of times previous to I could get it to load properly. I had been wondering if your hosting is OK? Not that I am complaining, but sluggish loading instances times will sometimes affect your placement in google and can damage your high-quality score if advertising and marketing with Adwords. Anyway I'm adԁing this RЅS to my email
    anԁ cоuld looκ out foг much more of your reѕpectіve exciting
    сontent. Make ѕure you update thіs аgаin verу sοon.


    Ηere iѕ mу websitе payday loans

    ResponderEliminar
  3. Sorry to break your illusion, but Cutler himself has admitted that he uses steroids.

    If you google Ronnie Coleman steroids you'll get to a page where there's
    a video in which Cutler admits himself and a lot of other pro
    bodybuilders utilizing. He claims that they require to acquire an edge irrespective of what it
    takes, after which he talks about steroids. So there you go.


    Take a look at my web site :: six pack shortcuts members login page

    ResponderEliminar
  4. hello there and thank you for your info – I've definitely picked up anything new from right here. I did however expertise several technical points using this website, as I experienced to reload the web site lots of times previous to I could get it to load properly. I had been wondering if your hosting is OK? Not that I am complaining, but sluggish loading instances times will sometimes affect your placement in google and can damage your quality score if advertising and marketing with Adwords. Anyway I am adding this RSS to my e-mail and could look out for a lot more of your respective intriguing content. Ensure that you update this again very soon.

    My blog post: visit us

    ResponderEliminar
  5. Quаlіty poѕts іs the sеcret to be а focus for the useгs
    to gο to see the ωeb page, that's what this site is providing.

    Also visit my web-site reputation management

    ResponderEliminar
  6. Some websites are there like females seeking men and men in search of girls in chennai/bangalore etc.
    ..But for that previous five many years am preserve on publishing and anticipating some reply from the lady.
    But not but received any girl response..Could it be very good approach
    to lookup girl buddy or searching woman buddy by means of internet site
    by no means function out?.....then inform me another idear to get lady pal?

    .......

    Feel free to surf to my web blog - how to get a girls attention

    ResponderEliminar
  7. Great job on these new articles or blog posts!
    I
    used to be constantly surprised how Bale was able to rework himself in
    that short amount of your time.
    Muscle Memory is
    correct but I bet roids have been also concerned when you
    said: his paycheck trusted it.

    Also visit my homepage: building muscle mass diet for women

    ResponderEliminar
  8. I loved as much as you'll receive carried out right here. The sketch is attractive, your authored subject matter stylish. nonetheless, you command get bought an impatience over that you wish be delivering the following. unwell unquestionably come further formerly again since exactly the same nearly a lot often inside case you shield this hike.

    my webpage; office furniture Services memphis tn

    ResponderEliminar
  9. Good, I like which you share this online video Schooling is not the filling of a vessel,?
    however the kindling of a flame, I want success always

    Feel free to surf to my web site - tips to attract women on facebook

    ResponderEliminar

  10. I am really impressed along with your writing skills and also with the format on your blog.

    123.hp.com/setup 4500

    ResponderEliminar

  11. Awesome blog! I am really impressed by this blog! The pictures are really nice and cool

    123 HP Setup

    ResponderEliminar
  12. Wow this blog is very nice …Crafsol is India's best Robots and Device Solutions Company
    Robots and Device Solutions

    ResponderEliminar
  13. Wow...! awesome you did a great job and superb blog thank you so much for this blog. Here I want to tell something about the configure Gmail configuration in Microsoft outlook those who all want to know about the email configuration in outlook please refer my site.

    ResponderEliminar
  14. Thank you so much for this fantastic blog, The windows update error 80072ee2 message is displayed on the screen when the update process fails or files stored on your system are corrupted. To fix the error 80072ee2 on windows 10, read the troubleshooting instructions that are listed here.

    ResponderEliminar
  15. Thank you so much for this blog, If you are not receiving emails on your POP3(Post Office Protocol version 3) account in Outlook 2016, check the internet connection first and restart your Outlook application. Close all other running applications running on your computer. Check if you are using the obsolete OS version.

    ResponderEliminar
  16. Thanks a lot for this awesome one..! The brother mfc j6945dw scan to email function can be done following the procedure press the settings icon on the control pannel's LCD screen navigate to all settings and select print reports choose network configuration from this list, this is the basic functions if want to know more about this visit this site.

    ResponderEliminar
  17. Thanks a lot for this blog..! Windows update error code 8007000e on your computer this is simple to fix an easy way of methods, some of the methods are listed below if you want to know about this error code visit here also solve the related error codes.

    ResponderEliminar
  18. Thank you so much...Post Office Protocol version 3 is the updated version of POP. The POP3 is a server protocol that is responsible for downloading or receiving e-mails from the internet server and also do configure Gmail in outlook 2007. If you have more doubts please visit us.

    ResponderEliminar
  19. Awesome blog thank you so so much..,The Brother MFC J6945DW scan to e-mail function can be done following the procedure given below. Brother printer has done the multi-task when compared to your older printer, it has the new features so visit here and know what are the features available.

    ResponderEliminar
  20. Thank you so much for this blog, certain PS's enabled on windows 10 come with SIM cards that allow you to connect to a mobile network and configure cellular settings in windows 10. This means that you can get over a network wherever you have a cellular signal.

    ResponderEliminar
  21. Thank you so much for this giving blog, Here I want to say about the brother MFC j6945dw printer wired setup. if you want to know about this printer please refer to my site.

    ResponderEliminar