skip to main |
skip to sidebar
Problem Statement :
I've set the maxRequestLength property of an IIS7 website I have running in Integrated Pipeline mode to 116384. According to the docs, that should be 116MB. I've also set the executionTimeout property to 3600 (1 hour). However, I found myself unable to upload larger files. I then did a test of a whole series of files to see how large I could go. Anything up to 29,280KB successfully uploaded. Anything from 29,318KB and above failed. I added a BeginRequest event on my upload module and set a breakpoint on the first line of code. The successful uploads hit the breakpoint. The failed uploads don't. This means to me that there is some process that comes before the BeginRequest event that is refusing to accept these posts. I also read the configuration settings using reflection, application.Context.GetConfig("system.web/httpRuntime"), etc and it returned the amount I had set, 116384. Is there another setting I need to make? Does anyone know why these larger posts are not being handled by my module?
Solution :
Edit upload_max in the php.ini to bigger size. Well, this was interesting. The error code was 404.13. After some searching on that, I eventually tracked down that IIS7 requires two different settings and apparently, the default is 30000000 bytes, which is the exact limit I ran into (29,296kb). As a note, in case anyone else runs into this problem, there is one other step (which I had already done). Since requests are streamed into memory before being processed, sometimes the application pool will recycle if it is using too much memory. I implemented a solution shared by many file uploading components, that intercepts the HttpWorkerRequest and streams the data directly to disk, parsing out the MIME Boundries and such. Anyway, adding the second attribute to the web.config solved the problem for me.
Problem Statement :
BOOTMGR missing after deploying a custom image
I'm stuck. I followed the "Deploying Vista Step by Step Guide". As a server I've used Vista Ultimate. Then I installed a target machine using autounattend file and Vista CD.
Run sysprep (Sysprep.exe /oobe /generalize /shutdown). I created PE, captured an Image from target machine to a network share (z:\Tools\Imagex.exe /compress fast /capture C: z:\\Myimage.wim "my Vista Install" /verify).
Image was created successfully. I booted target machine with PE and created partition with diskpart:
diskpart
select disk 0
clean
create partition primary size=40000
select partition 1
active
format
exit
Next I dropped an image (z:\tools\imagex.exe /apply z:\myimage.wim 1 c:
As this far everything has gone as planned. But when dropping an image there are quite a lot of this kind of text:
[INFO] c:\windows\system32\config\systemprofile\AppData\LoaclLow\desktop.in [Restore Sec. Descriptor: -> SACL is going away ]
I get quit a lot of those but those are only INFO so does it matter? What causes those INFO messages?
After image has dropped completely I boot the target machine resulting BOOTMGR is missing. Press Ctrl + alt + del to restart.
I tried to find answer everywhere but without any success...
Solution :
I ran into the same “BOOTMGR / NLTDR is missing” problem with Windows 7 after applying a WIM image using diskpart and ImageX and I managed to resolve it by running this command after applying the image "bcdboot c:\windows"
