Does anyone know whether there is a page limit in an XPS document I have created a 10,000 page XPS document printed with the Microsoft XPS Document Writer from Crystal Reports XI. I can open this document in the XPS viewer with no problems.
However, when I create a 100,000 page document using the same package, the XPS document does not open in the XPS viewer and the memory use on my computer jumps and keeps on rising.
I am working on Windows XP. Any ideas, anyone
Hi,
Spec says max. number of fixed pages in a fixed document is 1,000,000. But if your xps document is created in interleaved (default, document writer creates in non-interleaved), zip32 has a limitation on item count.
Try creating document in non-interleaved and see. it is possible still you may have the problem because of zip limitation.
Thank you CTA,
This information is very useful. In further tests I was able to print upto 30,000 pages using the MXDW in non-interleaved format. I will need to look at the zip32 limitation. My document is quite simple though (1 logo on each page (same logo on each page), an address and 3 paragraphs of text on each pages), so I am a bit worried if this proves to go beyond a limit.
did you also see that massive memory usage when printing your 10,000 page XPS file
Hi Jo,
I have not tried more than 300 page document,
Is it graphics intense document if not, is it possible that visuals are not cleaned up properly after printing each page. I have seen that massive memory usage for graphics intense pages.
Hej Charlee ,
Jo0815,
When I am printing large files I am not seeing the increase in memory. Although I am having the problem mentioned eariler about opening files over 30,000 pages. The code I am using to print is below. I hope that this helps.
Dim vxpsd As System.Windows.Documents.Serialization.SerializerWriterCollator
vxpsd = xpsWriter.CreateVisualsCollator
vxpsd.BeginBatchWrite()
objXPSPage = New System.Windows.Documents.FixedPage
objXPSPage = objXPSDocumentPage.Visual
' The next line adds a FixedPage and applys it and an "overlay" into a ContainerVisual
objNewPage = objMarkupPage.Apply(objXPSPage)
Dim objPrintTicket As New System.Printing.PrintTicket
' Set Duplexing On Page By Page Basis
Select Case lngDuplexingType
Case 1
objPrintTicket.Duplexing = Duplexing.OneSided
Case 2
objPrintTicket.Duplexing = Duplexing.TwoSidedShortEdge
Case 3
objPrintTicket.Duplexing = Duplexing.TwoSidedLongEdge
Case Else
objPrintTicket.Duplexing = Duplexing.Unknown
End Select
objPrintTicket.InputBin = New InputBin
objPrintTicket.InputBin = 1
vxpsd.Write(objNewPage) ' , objPrintTicket)
objNewPage = Nothing
xpsOld.Close()
vxpsd.EndBatchWrite()
Hej,
I found the reason for that huge memory usage when printing lot's of visuals via the visuals batchwriter...
Back in January I was unable to create a 100,000 page XPS document using the Microsoft XPS Document Writer (see first message in this post). Replies to this post informed me that there was a limit, but this is 1 million pages. I was only at 10% of this. I have now got a Vista test machine with full Vista Business installed. I still cannot produce a 100,000 page XPS document using the Microsoft XPS Document Writer. I cannot believe this, as we have invested a lot of resource in developing software for this XPS document format.
Has anyone got any ideas or has anyone successfully created a large XPS document
Help Me Please...
The problem you're experiencing is a bug in the implementation, not the limitation of XPS format itself. This will be considered for a future release. If you're blocked by this issue, try to write or find a tool which can repair ZIP files.
Thanks
Try this small piece of repair code:
NOTE:
1) This only works for this case (file with lots of pages generated by MXDW).
2) The original file is over-written, so make a copy of it before using it.
int ZipRepair(const wchar_t * pFileName)
{
HANDLE hFile = CreateFile(pFileName, GENERIC_READ | GENERIC_WRITE, FILE_SHARE_READ, NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL);
if (hFile == INVALID_HANDLE_VALUE)
{
return -1;
}
DWORD sizeHigh;
DWORD sizeLow = GetFileSize(hFile, & sizeHigh);
DWORD buffer[25];
DWORD read = 0;
if (SetFilePointer(hFile, sizeLow - 22, NULL, SEEK_SET))
if (ReadFile(hFile, buffer, 22, & read, NULL))
{
DWORD entry = (buffer[2] & 0xFFFF) + 0x10000;
DWORD size = buffer[3];
DWORD offset = buffer[4];
memset(buffer, 0, sizeof(buffer));
buffer[0] = 0x06064b50;
buffer[1] = 44;
buffer[3] = 0x002d002d;
buffer
= entry;
buffer
= entry;
buffer[10] = size;
buffer[12] = offset;
buffer[14] = 0x07064b50;
buffer[16] = sizeLow - 22;
buffer[18] = 1;
buffer[19] = 0x06054b50;
buffer[21] = 0xFFFFFFFF;
buffer[22] = 0xFFFFFFFF;
buffer[23] = 0xFFFFFFFF;
if (SetFilePointer(hFile, sizeLow - 22, NULL, SEEK_SET))
{
if (WriteFile(hFile, buffer, 98, & read, NULL))
{
printf("%S repaired\n", pFileName);
}
}
}
CloseHandle(hFile);
return 0;
}
Thanks for pushing the limits
Feng Yuan
The two lines with funny icons should have been:
buffer[ 6 ] = entry;
buffer[ 8 ] = entry;