DonatShell
Server IP : 180.180.241.3  /  Your IP : 216.73.216.252
Web Server : Microsoft-IIS/7.5
System : Windows NT NETWORK-NHRC 6.1 build 7601 (Windows Server 2008 R2 Standard Edition Service Pack 1) i586
User : IUSR ( 0)
PHP Version : 5.3.28
Disable Function : NONE
MySQL : ON  |  cURL : ON  |  WGET : OFF  |  Perl : OFF  |  Python : OFF  |  Sudo : OFF  |  Pkexec : OFF
Directory :  /Windows/System32/en-US/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :

[ HOME SHELL ]     

Current File : /Windows/System32/en-US//qmgr.dll.mui
MZ@	!L!This program cannot be run in DOS mode.

$uEEELlDLl
DRichEPEL`[J!	P@.rsrc@@00H`x?				 8~pPMUI&̍ř|{II䛁$iiXMMUIen-US'Background Intelligent Transfer ServiceTransfers files in the background using idle network bandwidth. If the service is disabled, then any applications that depend on BITS, such as Windows Update or MSN Explorer, will be unable to automatically download programs and other information.(an unknown user)PA.@@,@@@	@@@@@@@PmBmB      * * U U 0000$PP
ppldeD @!,1p(33,//?@  @E  tH  W ) <Y+ . e> I 8hP T 0oV V sTudv
x!؂;@0FSȌefL #L-7@@@@@@
@@@8While canceling job "%2", BITS was unable to remove some temporary files. To recover disk space, delete the files listed below.  The job ID was %1.  %3

<While canceling job "%2", BITS was unable to remove some temporary files. To recover disk space, delete the temporary files. Note: Due to space limitations, not all files are listed.  Check for additional files of the form BITxxx.TMP in the same directory.  The job ID was %1.  %3

Job "%2" owned by %3 failed to notify its associated application.  BITS will retry in %4 minutes.  The job ID was %1.

dThe BITS service failed to start.  Error %1.

BITS has encountered an error communicating with an Internet Gateway Device.  Please check that the device is functioning properly. BITS will not attempt to use this device until the next system reboot. Error code: %1.

Error %3 occurred when BITS tried to change the state of firewall rule "%1" to %2.  Restarting the BITS service may correct the problem.

The Per-user job limit (%2) specified through Group Policy must be less than or equal to Per-computer job Limit (%3).  To correct the problem, modify BITS Group Policy settings and restart the BITS service.

XA new BITS job could not be created. The current job count for the user %1 (%2) is equal to or greater than the job limit (%3) specified through group policy.  To correct the problem, complete or cancel the BITS jobs that haven't made progress by looking at the error, and restart the BITS service. If this error recurs, contact your system administrator and increate the per-user and per-computer Group Policy job limits.

`A new BITS job could not be created. The current job count for this computer (%2) is equal to or greater than the per-computer job limit (%3) specified through Group Policy.  To correct the problem, complete or cancel the BITS jobs that haven't made progress by looking at the error and restarting the BITS service. If this error recurs, contact your system administrator and increase the per-computer Group Policy job limits.

BITS could not add file(s) to %1 job. The file count for %1 job (%2) has exceeded the per-job file limit (%3) specified through Group Policy.  To correct the problem, increase the Computer s per-job file limit Group Policy settings and restart the BITS service.

BITS could not add ranges to %1 file. The range count for %1 file (%2) has exceeded the per-file range limit (%3) specified through group policy.  To correct the problem, increase the per-file range limit Group Policy setting and restart the BITS service.

The BITS service has detected an exception, Function: %1, Line: %2 Error code: %3.

A bandwidth profile is not configured correctly. The value of a Group Policy setting is missing or is not within the allowed range. Make sure that you configure the Group Policy settings correctly, and then try again.

The BITS service is configured to run as %1. BITS works correctly only when configured to run as the system account.

hThere is no additional error context available.

BITS has deleted some of the transferred files because they were incomplete.

BITS was unable to delete some temporary files. Check the system event log for the complete list of files that could not be deleted.

DThe proxy server was changed.

The configuration preferences were saved successfully, but one or more of them are overridden by Group Policy.

Start

Stop

Resume

Suspend

Send

Hreplying to an incoming request

Xdenying or ignoring an incoming packet

Error

Warning

 Information

Verbose

ppeer neighbor list (server) - listening for clients

llisten via WS-Discovery for server announcements

Pa peer search for a particular URL

\a particular request within a peer search

Pa particular auth-exchange request

hHTTP status 100: The request can be continued.

HTTP status 101: The server switched protocols in an upgrade header.

HTTP status 200: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.

HTTP status 201: The request was fulfilled and resulted in the creation of a new resource.

HTTP status 202: The request was accepted for processing, but the processing has not been completed yet.

HTTP status 203: The returned metadata in the entity-header is not the definitive set available from the server of origin.

HTTP status 204: The server has fulfilled the request, but there is no new information to send back.

HTTP status 205: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.

HTTP status 206: The server fulfilled the partial GET request for the resource.

HTTP status 300: The server could not return the requested data.

HTTP status 301: The requested resource was assigned to a new permanent Uniform Resource Identifier (URI), and any future references to this resource should use one of the returned URIs.

HTTP status 302: The requested resource was assigned a different Uniform Resource Identifier (URI). This change is temporary.

HHTTP status 303: The response to the request is under a different Uniform Resource Identifier (URI) and must be retrieved using a GET method on that resource.

HTTP status 304: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.

HTTP status 305: The requested resource must be accessed through the proxy given by the location field.

HTTP status 307: The URL has been temporarily relocated. Try again later.

HTTP status 400: The server cannot process the request because the syntax is not valid.

HTTP status 401: The requested resource requires user authentication.

HTTP status 402: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.

HTTP status 403: The client does not have sufficient access rights to the requested server object.

HTTP status 404: The requested URL does not exist on the server.

lHTTP status 405: The method used is not allowed.

HTTP status 406: No responses acceptable to the client were found.

pHTTP status 407: Proxy authentication is required.

HTTP status 408: The server timed out waiting for the request.

dHTTP status 409: The request could not be completed because of a conflict with the current state of the resource. The user should resubmit the request with more information.

HTTP status 410: The requested resource is not currently available at the server, and no forwarding address is known.

HTTP status 411: The server cannot accept the request without a defined content length.

HTTP status 412: The precondition given in one or more of the request header fields evaluated to false when it was tested on the server.

HTTP status 413: The server cannot process the request because the request entity is too large.

4HTTP status 414: The server cannot process the request because the request Uniform Resource Identifier (URI) is longer than the server can interpret.

HTTP status 415: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.

HTTP status 416: The server could not satisfy the range request.

HTTP status 417: The server could not meet the expectation given in an Expect request-header field.

HTTP status 449: The server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.

HTTP status 500: An unexpected condition prevented the server from fulfilling the request.

HTTP status 501: The server does not support the functionality required to fulfill the request.

@HTTP status 502: The server, while acting as a gateway or proxy to fulfill the request, received an invalid response from the upstream server it accessed.

xHTTP status 503: The service is temporarily overloaded.

HTTP status 504: The request was timed out waiting for a gateway.

HTTP status 505: The server does not support the HTTP protocol version that was used in the request ErrorCode.

LThe requested job was not found.

$The requested action is not allowed in the current job state. The job is read-only. The job may have been canceled or completed transferring.

There are no files attached to this job. Attach files to the job, and then try again.

No file is available because no URL generated an error code.

No protocol is available because no URL generated an error code.

`The error occurred in an unknown location.

The error occurred in the Background Intelligent Transfer Service (BITS) queue manager.

The error occurred while the local file was being processed. Verify that the file is not in use, and retry.

The error occurred while the remote file was being processed.

The error occurred in the transport layer. The client could not connect to the server.

$The error occurred while the notification callback was being processed. Background Intelligent Transfer Service (BITS) will try again later.

The destination file system volume is not available. Verify that another program, such as CheckDisk, is not running, which would lock the volume. When the volume is available, Background Intelligent Transfer Service (BITS) will try again.

HThe destination volume has changed. If the disk is removable, it might have been replaced with a different disk. Reinsert the original disk and resume the job.

PNo error information is available.

(There are currently no active network connections. Background Intelligent Transfer Service (BITS) will try again when an adapter is connected.

8The server did not return the file size. The URL might point to dynamic content. The Content-Length header is not available in the server's HTTP reply.

TThe server does not support HTTP 1.1.

PThe server does not support the necessary HTTP protocol. Background Intelligent Transfer Service (BITS) requires that the server support the Range protocol header.

Background Intelligent Transfer Service (BITS) cannot be used remotely.

The drive mapping for the job is different for the current owner than for the previous owner. Use a UNC path instead.

The new owner has insufficient access to the local files for the job. The new owner might not have permissions to access the job files. Verify that the new owner has sufficient permissions, and then try again.

The HTTP proxy list cannot be longer than 32,000 characters. Try again with a shorter proxy list.

The HTTP proxy bypass list cannot be longer than 32,000 characters. Try again with a shorter bypass proxy list.

hThe server's response was not valid. The server was not following the defined protocol. Resume the job, and then Background Intelligent Transfer Service (BITS) will try again.

XNo more files can be added to this job.

The local file was changed during the transfer. Recreate the job, and then try to transfer it again.

|The program on the remote server reported the ErrorCode.

The specified session could not be found on the server. Background Intelligent Transfer Service (BITS) will try again.

XThe job is too large for the server to accept. This job might exceed a job size limit set by the server administrator. Reduce the size of the job, and then try again.

LThe specified string is too long.

The client and server versions of Background Intelligent Transfer Service (BITS) are incompatible.

Execute permissions are enabled on the Internet Information Services (IIS) virtual directory associated with the remote file specified in the job. To upload files to the virtual directory, disable execute permissions on the virtual directory.

The job is not making progress.  The server may be misconfigured.  Background Intelligent Transfer Service (BITS) will try again later.

The user name cannot be longer than 300 characters. Try again with a shorter name.

The password cannot be longer than 65536 characters. Try again with a shorter password.

The authentication target specified in the credentials is not defined.

The authentication scheme specified in the credentials is not defined.

The specified file name does not match any of the files in the job.

The requested byte range extends beyond the end of the web page.  Use byte ranges that are wholly within the page.

The list of byte ranges contains some overlapping ranges, which are not supported.

XA connection could not be established.

XThe connection was closed prematurely.

Group Policy settings prevent background jobs from running at this time.

tThe supplied proxy server or bypass list is invalid.

The format of the supplied security credentials is invalid.

xThe application chose an unsupported hashing algorithm.

The chosen peer-cache record has been deleted.  The attempt to update it has been abandoned.

Another application thread is already updating the peer-cache record.

The system is already searching for peers.  Retry the operation after a few seconds.

A Universal Plug and Play (UPnP) error has occured.  Please check your Internet Gateway Device.

The test option is blocking the download after the search completed.

<Peer-caching is disabled.

The peer-cache record is in use and can not be deleted at this time. Try again later.

The job count for the current user has exceeded the per-user job limit.

The job count for the current computer has exceeded the per-computer job limit.

The file count for the current job has exceeded the per-job file limit.

The range count for the current file has exceeded the per-file range limit.

The application requested data from a web site, but the response was invalid.                               Using Event Viewer, check the log 'Application Logs \ Microsoft \ Windows \ Bits-client \ Operational' for more details.

BITS timed out while downloading the job. The download did not complete within the maximum download time set for the job.

tThe job is configured to use a different security token for some operations, but the token is not currently available.  The application must provide a token and then resume the job.

DMicrosoft-Windows-Bits-Client

System

\Microsoft-Windows-Bits-Client/Operational

XMicrosoft-Windows-Bits-Client/Analytic

`BITS job "%2" with ID %1 has been resumed.

dBITS job "%2" with ID %1 has been suspended.

tThe BITS service created a new job: %1, with owner %2

The transfer job is complete.%nUser: %1%nTransfer job: %2%nJob ID: %3%nOwner: %4%nFile count: %5

Job cancelled. User: %1, job: %2, jobID: %3, owner: %4, filecount: %5

lBITS started listening for peer-client requests.

BITS was not able to listen for peer-client requests.  The error code was %1.  BITS jobs from other machines will not be able to use this machine as a peer server.  To fix this problem, try stopping the BITS service and restarting it.

lBITS stopped listening for peer-client requests.

tBITS started listening for peer-server announcements.

BITS was not able to listen for peer-server announcements.  The error code was %1.  BITS jobs on this machine will not be able to use peer-caching.  To fix this problem, try stopping the BITS service and restarting it.

tBITS stopped listening for peer-server announcements.

`BITS has sent an inquiry for peer servers.

tBITS has read the policy parameters for peer-caching.

XThe peer list rejected an incoming server announcement. This event is generated if the request is not valid, not if the server is merely in a different Windows domain.

4A new peer was added.

0A peer was updated.

XA peer was removed from the peer list.

TA cached peer was restored from disk.

TAn application cleared the peer list.

|BITS has replied to a client's inquiry for peer servers.

pThe server received a peer inquiry but rejected it.

PA peer search for an URL has begun.

4A peer search ended.

HA search request is being sent.

HA search request has completed.

hA search request has completed unsuccessfully.

\The peer's record %2 matched the request.

BITS updated the set of IP addresses used for peer-caching.

BITS started the %2 transfer job that is associated with the %4 URL.

BITS stopped transferring the %2 transfer job that is associated with the %4 URL. The status code is %6.

BITS stopped transferring the %2 transfer job that is associated with the %4 URL. The status code is %6.

<The BITS job named "%1" belonging to user %2 received inconsistent data while downloading. The URL was "%3". The transfer will continue using a different server.  If the problem occurs often, an administrator should scan the peer server for viruses or corruption in its hard drive.

tThe BITS job %1 is configured to launch %3 after transfer of %2. The notification program returned error %4, BITS will continue to launch the program periodically until it succeeds.

The BITS job %1 is configured to launch %3 after transfer of %2. The service failed to launch the program with error %4, BITS will continue trying to launch the program periodically until it succeeds.

BITS received a peer-cache request from a client at address %1.

The client's search request is for "%1" with timestamp %2.

pThe cache found a matching cache record with ID %1.

While processing the client's request, BITS encountered error %1.

xBITS rejected the client's request with HTTP status %1.

lBITS has finished processing the client request.

|The request includes the client's event-log activity ID.

\BITS search for peer-servers has started.

BITS has encountered %1 error while reading the peer-cache information. BITS will now attempt to delete and re-create the peer-cache.

BITS has successfully deleted the peer-cache. All the files cached until this point have been removed. The peer-cache will be re-created again as needed for handling the future requests.

BITS has successfully enabled peer-client and/or peer-server related components.

BITS has encountered %1 error while starting one or more peer-client or peer-server components.

\BITS accessed group policy value %1 : %2.

`BITS defaulted group policy value %1 : %2.

dThe peer's response to a search was invalid.

pThe file ranges associated with a transfer attempt

While transferring %1, BITS encountered error %2 using %3 as the HTTP proxy server.  This may indicate a problem with the proxy server or with the client's network configuration.  If this error occurs frequently, then an administrator should investigate. Details: {Job: %4}, {owner: %5}, {jobid: %6}, {URL: %1}, {xferId: %7}, {proxyServerList: %8}, {hr: %2}.

The BITS job named "%1" was unable to contact any HTTP proxy server in its proxy list.  This may indicate a problem with the proxy servers or with the client's network configuration.  An administrator should verify whether the proxy list is correct.  BITS will periodically try to transfer the job.  The HTTP proxy list is "%6".  The proxy-bypass list is "%7".

TWhile transferring %1, BITS encountered error %7 using %6 as the HTTP proxy server.  The web server or proxy server does not support an HTTP feature required by BITS.  This problem can only be corrected by the adminstrator of the web server or proxy server.  Details: {job: %1}, {owner: %2}, {jobId: %3}, {url: %4}, {xferId: %5}, {proxyServer: %6}, {hr: %7}, {urlContentLength: %8}, {urlHttpVersion: %9}, {urlRange: %10}

The BITS service provided job credentials in response to an authentication challenge from the %1 server for the %2 transfer job that is associated with the following URL: %3.%nThe credentials were accepted.

(The BITS service provided job credentials in response to an authentication challenge from %1 for job %2, url %3. The credentials were rejected.

TA bandwidth slot transition occurred.

lThe service is generating its common global data.

lThe service is reading its group policy settings.

lThe service is creating its performance counters.

dThe service is searching for gateway devices.

lThe service is starting the peer-caching client.

lThe service is starting the peer-caching server.

pThe service is reading the job list from the disk.

The service is updating its list of active network connections.

tThe service is updating its list of logged-in users.

xThe service is creating the Volume Shadow Copy writer.

`The service is registering its COM objects.

`The BITS service has started successfully.

The BITS service has started successfully, but it was delayed long enough that there may be a problem. For more information on the delay, enable the analytic log for BITS, then stop and restart the BITS service.

The peer-cache client startup phase of startup has completed.

DThe service is shutting down.

LThe service shutdown is complete.

hThe BITS service loaded the job list from disk.

LIt took %1 seconds to write a change file to the BITS job list. If this is excessive, the number of BITS jobs may be larger than this machine can handle quickly.

The BITS service shut down successfully, but it was delayed for %1 seconds. This might cause delays when you turn off your computer. For more information on the delay, enable the analytic log for BITS, then stop and restart the BITS service.

The BITS peer cache was unable to find any peers in the network.

The initialization of the peer helper modules failed with the following error:  %1.

The BITS peer transfer with the %1 ID for the %2 transfer job resulted in the following error: %4.

The administrator %4 canceled job "%2" on behalf of %3.  The job ID was %1.

The administrator %3 modified the %4 property of job "%2".  The job ID was %1.

The administrator %4 took ownership of job "%2" from %3.  The job ID was %1.

Job "%2" owned by %3 was canceled after being inactive for more than %4 days.  The job ID was %1.

 The BITS job list is not in a recognized format.  It may have been created by a different version of BITS.  The job list has been cleared.

@BITS Peer-caching protocol

HWeb Services-Discovery protocol

The BITS service provided job credentials in response to the %4 authentication challenge from the %1 server for the %2 transfer job that is associated with the following URL: %3.%nThe credentials for the %5 user were accepted.

The BITS service provided job credentials in response to the %4 authentication challenge from the %1 server for the %2 transfer job that is associated with the following URL: %3.%n The credentials for the %5 user were rejected.

4VS_VERSION_INFO@@?StringFileInfo040904B0LCompanyNameMicrosoft Corporationx(FileDescriptionBackground Intelligent Transfer Servicel&FileVersion7.5.7600.16385 (win7_rtm.090713-1255)2	InternalNameqmgr.dll.LegalCopyright Microsoft Corporation. All rights reserved.B
OriginalFilenameqmgr.dll.muij%ProductNameMicrosoft Windows Operating SystemBProductVersion7.5.7600.16385DVarFileInfo$Translation	PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPAD

Anon7 - 2022
AnonSec Team