Article ID: 823211 - Last Review: May 7, 2009 - Revision: 5.0 Windows Server 2003 Does Not Identify a Dell PV122T VS80 Medium Changer
On This PageSYMPTOMSA Windows Server 2003-based computer does not identify a Dell PV122T VS80 medium changer device. The device stops working after this
problem occurs. The PV-122T VS80 appears as Benchmark VS640 DLT Autoloader in Device Manager. If you upgrade your firmware from V50 to V57 on the PV-122T VS80, you may experience this problem.
CAUSEThis issue is caused by a code problem in the Microsoft-provided Powerfil.sys driver. When a MoveMedium command is issued, Windows first determines if the transport, source, and destination element
are out of range. A transport address is considered to be out of range if no transports are being reported. The driver does not identify the device
if no transports are being reported. RESOLUTIONThis hotfix was included with Windows Server 2003 Service Pack 1 (SP1). See the following Microsoft Knowledge base article for steps to download the latest service pack for Windows Server 2003:
889100
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003
Hotfix InformationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesNo prerequisites are required.Restart RequirementYou must restart your computer after you apply this hotfix.Hotfix Replacement InformationThis hotfix does not replace any other hotfixes.File InformationThe English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Date Time Version Size File name Platform --------------------------------------------------------------- 08-Jul-2003 00:09 5.2.3790.68 11,264 Powerfil.sys x86 08-Jul-2003 00:09 5.2.3790.68 30,208 Powerfil.sys IA64 STATUS Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
MORE INFORMATION For additional information about how hotfix
packages are named , click the following article number to view the article in
the Microsoft Knowledge Base: 816915
(http://support.microsoft.com/kb/816915/
)
New Naming Schema for Microsoft Windows Hotfix Packages
APPLIES TO
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations |






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
