The user misconfiguration issue was resolved - user had a 1GB disk quota in
effect... so the 4GB upload tripped over the limit. Once the disk quota was
adjusted, large uploads did not have any problems.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Narayana Mahankali [MSFT]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
First of all, I apologize for the delay in responding to your problem.
Usually we are pretty responsive but recently we have been extremely busy
with new features for Windows Vista.
Anyway coming back to your problem BITS upload feature is designed to
support pretty large uploads and after I saw your posting I tried uploading
a 5GB file and it succeeded. So I can't say what really went wrong. We need
the following information to troubleshoot further.
1. Enable BITS server logging on the server machine using the following
instructions. Run them from a command prompt:
md c:\bitslog
cacls c:\bitslog /e /p everyone:f
set BitsKey=HKLM\Software\Microsoft\BITSServer
reg add %BitsKey% /v LogFileName /t REG_EXPAND_SZ /d
c:\bitslog\bitssrv.log /f
reg add %BitsKey% /v LogFlags /t REG_DWORD /d 0xff /f
reg add %BitsKey% /v LogSize /t REG_DWORD /d 0x20 /f
iisreset
2. Enable BITS client logging on the client machine using the following
instructions. Run them from a command prompt:
set BitsRegKey=HKLM\Software\Microsoft\Windows\Current Version\BITS
reg add %BitsRegKey% /v LogFileFlags /t REG_DWORD /d 0xfbcf /f
reg add %BitsRegKey% /v LogFileSize /t REG_DWORD /d 0x100 /f
reg add %BitsRegKey% /v LogFileMinMemory /t REG_DWORD /d 0x30 /f
net stop bits
net start bits
3. Start a network packet trace using either Microsoft Network Monitor or
Ethereal (
http://www.ethereal.org) on both the client and server machines
4. Now reproduce the problem (by uploading a huge file using BITS)
5. Stop the network packet traces on both client and server machines and
save them as client.cap and server.cap respectively
6. Stop the BITS service on the client machine ( net stop bits)
7. Send me the following files:
1. %windir%\system32\bits.log from the client machine
2. %windir%\system32\bits.bak (if exists) from the client machine
3. client.cap file from the client machine
4. server.cap from the server machine
5. c:\bitslog\bitssrv.log from the server machine
6. IIS logs from the server machine
You can send these files directly to me instead of posting on the newsgroup.
Please remove "online" from my email address.
--
Narayana Mahankali
Microsoft, BITS
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Håkan" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I have verified that the filename only uses a to z, no non ascii
>charectaer.
>
> A collegue of min have reproduced the error on another server and another
> client, but this tiem the file was rather small, just 5 MB, and it reports
> no disk space. so it seams that this is not related to 4 GB at all.
>
> I have done some more checking in the log, and it seams the file is partly
> transfered befor the error cocour. I included log records from my iis
> server...you can se that the request that fail is a lot larger then the
> previous....perhaps this could be a hint...
>
> /Håkan
>
>
> "Egbert Nierop (MVP for IIS)" <(E-Mail Removed)> wrote in
> message news:%(E-Mail Removed)...
>> "Håkan" <(E-Mail Removed)> wrote in message
>> news:u0L$(E-Mail Removed)...
>>>I built the dotNET dll I am using from the bits20.idl file and I am using
>>>windows xp sp2 as the client and windows 2003 sp1 as the server.
>>>
>>> /Håkan
>>>
>>>
>>> "Egbert Nierop (MVP for IIS)" <(E-Mail Removed)> wrote in
>>> message news:(E-Mail Removed)...
>>>> "Chris" <(E-Mail Removed)> wrote in message
>>>> news:91712168-B703-437E-8BBE-(E-Mail Removed)...
>>>>> Hi
>>>>>
>>>>> Fat32 is not being used anywhere is it? This has a maximum file size
>>>>> of
>>>>> 4GB
>>>>>
>>>>> Chris.
>>>>>
>>>>
>>>> In addition, BITS 1.2 does not garantuee up/downloads of 4GB +...
>>>> BITS 2.0 does however.
>>
>> I suspect, that there is a BUG in one of the Atl API (if they use Atl or
>> so).
>> So does CAtlFile have a bug, it gives you the idea that a file size >
>> 4GB
>> can be reported, but since the MS developer programmed GetFileSize
>> instead
>> of GetFileSizeEx, the library will report no more than 4GB.
>>
>> A similar error can be there in BITS, but this would mean that MS never
>> tested BITS with sizes above 4 GB.
>> Anyway, I will post your error lets see what they'll answer.
>>
>
>
>
Similar Threads
Linear Mode
