V-79-57344-34004 - End of data set was unexpectedly encountered

Problem

We are using "Backup Exec 10D" with service pack4 from BUE. Currently trying to backup four physical servers, and one server always fails to to backup. Errors generated from the Backup Exec's job log:

Job log
Verify- \\Server\D: Unexpected end of backup set encountered on CERTANCE 1.
V-79-57344-34004 - End of data set was unexpectedly encountered.

Solution

Talked to other techs that use Backup Exec software and they were able to give me some tips for this error.

Fix1:
Force the NIC to the same speed of the switch it's connected to.
1. Go to Device manager by -> right clicking My Computer -> Manage
2. Select Device manager -> select NIC card -> right click NIC card
3. Advance TAB -> in the Property window select Speed & Duplex -> Change value drop down to forced speed, instead of "Auto"


Fix2:
1. Ensure the drivers you're using for the tape drives are compatible. This means if you have a tape library ensure the tape library drivers are manufactuers drivers. This is listed in your device manager as "Medium Changers."
2. Ensure the drivers for your "tape drives" are from Symantec Backup Exec. This is listed under your device manager as "Tape Drives."


The first fix1 solved my supposivly network issue.

error E00084F4 V-79-57344-34036

Backup fails with error E00084F4 (V-79-57344-34036).

Error:

A job failed with systems error e00084f4 unknown error (V-79-57344-34036)

Problem description:
There have been multiple instances in which a setting called the RetryBusyCount setting is set too low and this leads to the failure of the backup jobs.  See below for instructions in order to make the registry change on the backup server.  The original setting calls for a value set at 75 decimal,  but it is recommended to change it to 100 decimal or 64 hex,  as is needed in the registry entry.

NOTE:  Please back up the current registry before making this change to preserve the original version. Be careful when making any registry changes as this can cause serious problems.

If the backup jobs continue to fail, then it is recommended to set this value higher,   It is feasible to have this configuration setting set as high as 250, until the issue is resolved.  If issue persists at max value of 250,  then further troubleshooting steps would be in order to determine the source,  causing the failure. Your registry entry would be under the LTO-4 and not the LTO-3 as shown below.

Solution:  To resolve the media write errors, the following steps were taken to modify the registry in Windows on the media server.
1)  Launch regedit by click start, run and type regedit, click ok

2) Browse to  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SCSI\[device identifier name for the tape LTO-3 tape device]\[numeric device instance id for the LTO-3 tape device]\Device Parameters\

3) Add a key named Storport under Device Parameters (if one does not already exist).

4) Add a key name called BusyRetryCount. The key type is REG_DWORD, and the value should be set to 4b hex (75 decimal).

5) Close regedit

6) Reboot the server

Should do the trick. Worked perfectly when we experienced the issue.

Source: Symantec

http://www.online-it-support.co.uk/?p=1263

Enabling or Disabling the Disk Write Caching

Enabling or Disabling the Disk Write Caching

1. Right-click My Computer, and then click Properties.
2. Click the Hardware tab.
3. Click Device Manager.
4. Click the plus sign (+) next to the Disk Drives branch to expand it.
5. Right-click the drive on which you want to enable or disable disk write caching, and then click Properties.
6. Click the Disk Properties tab.
7. Click to select or clear the Write Cache Enabled check box as appropriate.
8. Click OK.

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

Computer System Product

To know  product key of the computer and some other details run this command:

 

cmd

wmic csproduct list



* Works on Win7/Server 2008 only

Configure OMA in Exchange 2003

One of the coolest things in Exchange Server 2003 is it's ability to allow mobile users to connect to it via a stripped down version of Outlook Web Access called (you guessed right) "Outlook Mobile Access", or OMA for short.

Exchange Server 2003 enables any device capable of running the Windows Mobile 2002 or later, such as browser-enabled cell phones or Windows Mobile–based Personal Digital Assistants (PDAs) to access corporate Exchange information. All changes made on the wireless device are reflected in the live mailbox and can be seen from a full desktop mail client such as Outlook 2003 or Outlook Web Access (OWA).

The best thing about OMA is that it is practically configuration-free. almost nothing to worry about and no buttons to click. Just install Exchange Server 2003 and you're almost ready to go.

Requirements

In order to successfully implement OMA on your organization you need the following:

• Server installed with Windows Server 2003 + Exchange Server 2003 (both Std. and Ent. editions will work just fine)
• Latest Service Packs for both Windows Server 2003 (currently none, expect SP1 in Q1 2005) and Exchange Server 2003 (currently SP2 - Download Exchange 2003 SP2)
• Latest patches for both Windows Server 2003 (see Windows Server 2003 Gold (RTM) Patches) and Exchange Server 2003 (see Exchange 2003 SP1 Patches)
• Optional - Internet connection to your Exchange server and SSL certificate to protect your OMA (see Configure SSL on OMA)

Lamer note: Make sure you have all things set up and that your Exchange organization is flawlessly working. We do not want to blame OMA for messing up your settings, because it won't.

Pre-SP1 installations of Exchange Server 2003 required that you install .NET Framework 1.1 Device Update 4.0. If, for some strange reason, you do not want to install SP1 for Exchange, make sure your install DUP. SP2 does not require any additions.

Any mobile phone or mobile device–based browsers that support HTML, XHTML, or Compact Hypertext Markup Language (cHTML) can be used to connect to OMA. For a list many supported devices click HERE.

Enabling OMA

As stated above, you actually do not need to install anything to get OMA up and running.

1. Open the Exchange System Manager.
2. Navigate to the Global Settings folder, expand it and go to Mobile Services. Right-click Mobile Services and choose Properties.

1. In the Mobile Services properties window, under Outlook Mobile Access, click to select the Enable Outlook Mobile Access and the Enable Unsupported Devices check boxes.
2. Click Ok.

Firewall and Internet connection

I won't go into detail here, but you should make sure that your Firewall allows TCP Port 80 and 443 (optional) to your server (the Exchange server that holds the OMA site) and to the following URL: http://FQDN/OMA (replace FQDN with the Fully Qualified Domain Name of your server).

In cases where your organization uses a Front-End/Back-End topology, you should allow access to the Front-End server(s).

SSL and security

You can protect the OMA traffic by using SSL. Read the following article on how to do that: Configure SSL on OMA.

Enabling/Disabling per user settings

By default, all mailbox-enabled users have OMA enabled. If you want, you can disable OMA on a per-user basis, while retaining the OMA functionality for other users.

Do disable (and later enable) a specific mailbox-enabled user from using OMA perform the following steps:

1. On your Exchange server, open Active Directory Users and Computers.
2. Navigate to (or find) the required user account.
3. Double-click the required user account, or right-click it and select Properties.
4. Go to the Exchange Features tab, select Outlook Mobile Access, and press the Disabled button.

1. Click Ok all the way out.

To re-enable OMA for the specific user, reverse your actions.

Test OMA

You should now Test OMA in Exchange 2003 from a regular web browser (just to see that it's working), from any Pocket Explorer or WAP browser emulator (as I did with the following screenshots) or from your mobile phone/Pocket PC/Palm OS.

Provide your username and password:

Begin browsing your mailbox:

Working with OMA

As with Outlook Web Access (OWA), as long as you maintain a connection to your server you can browse and work with your mailbox.

Most settings and options are self explanatory, such as browsing the folder tree:

Answering mail:



http://www.petri.co.il/configure_oma.htm

Config Fortigate PPTP VPN

In V4.0 you will not get the PPTP VPN option by default in the GUI. You need to add the widget manually (Create a customized Admin profile and login with that)

Here is the CLI:

config cpn pptp

set status enable

set sip 192.168.0.1

set eip 192.168.0.10

set usrgrp PPTP_USER

show

end

now you have to

1.add right permission to pptp_user group

2.configure the pptp rule in the firewall

More information:

http://docs.fortinet.com/fgt/archives/3.0/install/FortiGate-110C_Install_Guide_01-30006-0481-20080728.pdf
http://kb.fortinet.com/kb/microsites/search.do?cmd=displayKC&docType=kc&externalId=100112

http://www.youtube.com/watch?v=oH2FH1Y4nzU

כיצד נתמודד עם תקלה 0x80070424 במהלך הורדת עידכונים

בעיית התקנת עדכונים ב - XP
תקלה זו נגרמת בשל חוסר רישום או רישום פגום של קבצי מנגנון העידכונים
על מנת לטיפל בבעיה זו בצע/י את הפעולות הבאות:
1. לחץ/י על "התחל"-"הפעלה" רשום/י CMD ולחץ/י על "אישור".
2.הקלד/י את הפקודות הבאות, לאחר על אחת לחץ/י על מקש [Enter] ועל "אישור" בחלון סיום הפעולה:
regsvr32 wups.dll
regsvr32 wuaueng.dll
3. סגור/י את החלונות הפעילים והורד שוב את העידכונים.
לחילופין, תוכל/י להוריד ולהפעיל את הסקריפט WindowsUpdatedFix. לחץ/י כאן להורדה.
http://www.regevnet.com/downloads/files/WindowsUpdatedFix.cmd

קרדיט לרגבנט