FM8 -- Acrobat7 Error: A number is out of range

When PDFing a FM8 doc, I got an Acrobat error message: "A number is out of range." Acrobat produced a PDF, but the first page was page Zero! and the Properties of the Acrobat doc were not accessible. Not good.
Searched and searched for answers, but didn't come up with anything.
The FM8 doc is very basic -- only three standard fonts, 10 pages long, nothing fancy. The only unusual thing (if you want to call it that) is that I imported the text (copied in) from a .txt file, which originated as a Word doc.
So, I thought... hmmm... save first as a .MIF, then back to a .FM and see if that helps.
It did.
I don't know much about .MIF files. It must have cleaned up some garbage brought over from Word. You brainiacks who frequent this Forum probably understand completely how the .MIF works its magic.
Anyway, if anyone else gets this error message, I thought I'd document my solution with the error message in the subject line.
From Smokey Northern California,
Karen

The file is corrupt. Get a new undamaged copy.
Mike

Similar Messages

Receiving Error "A Number Is Out of Range" in Acrobat 8.1.2 and 7.0

I create mapbooks for the county I work at using ESRI's ArcMap ArcEditor. Once the book is done I convert it to PDF so that officers, fire fighters, etc. can open it on their laptops. Recently I started receiving the error "A Number is Out of Range" when I finish combining the PDF files into a binder. The error persists anytime I change pages and I have to click OK several times before it goes away. This becomes a problem for emergency management when their trying to search a road, plus it is also very annoying. Does anyone know how to get around this? It didn't use to do this. I thought maybe it was the fonts I was using, so I changed most of them to Arial and Times New Roman, yet it still persists, but seems slightly better. I cannot find anything on Adobes website about A Number is Out of Range. Also, I am using Acrobat Professional 8.1.2 and have also tried Professional 7.0. I'm running Windows XP. I have also tried reverting back to old versions of ArcMap and also the mapbook software MapLogic, but nothing helps. Any help would greatly be appreciated.

I'm getting this error also, and I don't think it's a font issue. Here's my situation.
I created a 144-page manual in Adobe FrameMaker 8.0 using the same template and fonts that I have used in several other large manuals. I saved the manual as a PDF using Acrobat 3D 8.0, and is get the mind-numbingly vague error "A number is out of range." I didn't get this error in previous versions of this manual, nor do I get this error with the other manuals on which I am currently working. I had inserted some EPS technical drawings, so I opened all of them in Illustrator CS3 and Created Outlines for any text that appeared in the illustrations.
After two days of replacing all of the fonts, optomizing PDFs, and distilling, distilling, and distilling again, I was not able to get rid of this message using Acrobat. I finally pulled out my MacBook Pro, opened the PDF manual using Preview, saved the PDF under a different name (no need to apply a Quartz filter), and (abracadabra!) the vague error message is gone!
Fonts may be one cause of the annoyingly vague "A number is out of range" error, but they are not the only one. And with such informative error messages as that, I doubt I'll ever know what is really wrong with my PDF.
Cheers!
Michael Opsteegh

There was an error processing a page. a number is out of range.

When I open a PDF generated from a classic ASP application, some particular documents fail when accessing a page: there was an error processing a page. a number is out of range.
This only happens in Adobe Reader 10 and 11.
The ASP page has a code similar to this:
Response.AddHeader "Content-disposition", "attachment; filename = doc.pdf"
Response.ContentType = "application / pdf"
Response.Write Session ("PDF")
Try adding different settings in the properties AddHeader / ContentType / CharSet etc, but always the same.
In the screenshot you can see the mistake in page 3
Any idea?
thank you very much

Sounds like the pdf is corrupt. Try a forced quit. (command option escape)

Adobe Acrobat Pro XI 11.0.06 when I reduce file size or try to optimize, I get this error: The document could not be saved. A number is out of range. I do the exact same thing every month and it works. I did it a few days ago and it worked. I receated the

Adobe Acrobat Pro XI 11.0.06 when I reduce file size or try to optimize, I get this error: The document could not be saved. A number is out of range. I do the exact same thing every month and it works. I did it a few days ago and it worked. I receated the pdf, I renamed it. tried to do it before I imported more pages. no go. the 16 mg pdf will normally reduce to 5 or 6

Hi,
Are you facing the issue with any pdf file?
Please try updating Acrobat to 11.0.7 and check.
You might also want to repair Acrobat and see.
Regards,
Rave

Error Message "The document could not be saved. A number is out of range"

Hello to all,
I'm working on a G5/10.4.11/Illust CS3/Acrobat 9 and use to generate .pdfs from .ais by using "Save as pdf" function. Either with LowRes profile and HighRes profile. My pdfs are sent to PC users that use to post it them for changes. But when they need to save them, they get the message "The document could not be saved. A number is out of range".
I know there was a few subject about that but do you have a recent solution to give me to help avoiding this bug ?
Many thanks in advance !
Stekc

As a follow to the above, the problem was related to a file transfer. The PDFs in question were being transfered from a Unix platform to a Windows Server. The transfer was defaulting to ASCII or Text and not binary. Apparently this was never an issue with older versions of Adobe Reader. Once the transfer was switched to binary, Reader X was able to view the files with no missing pages. Something was being stripped from the file that Reader X just didn't like.

NI MAX throughput error and Camera attribute out of range

I recently purchased a Point Grey Grasshopper3 camera, it seems to work fine in the Fly Cap software point grey provides, but I get an error in NI MAX when I try to do a simple grab (shown below). This error shows up every time I try to grab an image the first time after opening NI MAX, even though throughput is set to the max. Then I change the throughput max under device control to any number around the max of 125000000, and the camera works fine for MAX. It will grab images as much as I need. Then I save the camera, exit MAX, open MAX again, it shows my saved settings, I go to grab images and I get the error again. So I change the range to whatever number and it works again in the same session in MAX.
I did have a point grey Zebra2 working fine, and was using it in my LabVIEW program with IMAQdx to acquire images. When I try to use grasshopper3, LabVIEW returns an error of camera attribute out of range from the camera configuration VI. The VI's I am using to test the camera is just open camera, configure acquisition, start acquisition, get image, unconfigure acquisition, and close camera from IMAQdx. I did twice open MAX, change throughput, save camera, close MAX without grabbing an image, and then was able to acquire images in LabVIEW on the first run. Then I would run the VI again and it would return the error for camera attribute out of range. I have changed the packet size, resolution, and frame rate of the camera with out noticing a difference in the errors.
Since I am able to stream images from the camera in point greys fly capture, and in MAX after toggling the throughput setting, it leads me to believe there is some sort of MAX/LabVIEW error preventing me from capturing the images.
Any ideas? Has anyone else had this issue with MAX and LV?
Solved!
Go to Solution.
Attachments:
MAX error.png ‏17 KB

It looks like Point Grey cameras have shown this error before based on out of date firmware. See this link for one such instance. I would monitor the camera file (*.icd) located in the IMAQdx data folder in Public Documents to see if the actual value is being overwritten after the camera configuration is saved in MAX. There is a chance that the GigE .XML file that is transferred from the camera is overwriting these values to the unacceptable value. See this link for a KB regarding this error, which leads me to believe this may be the issue.
Karl G.
Applications Engineer
ni.com/support

ORA-13000: dimension number is out of range when using SDO_GEOM.RELATE

Dear everyone
I am attempting to workout which polygons cover the same area in order to determine distinct polygons. This is so I can then have just one copy of a polygon to a new table and delete all the duplicate polygons in the current table.
I ran the following first to check something:
SELECT SDO_GEOM.RELATE
   (A.geographical_coordinates,
    'DETERMINE',
    B.geographical_coordinates,
    0.05) relationship
FROM MAP_INDEX A,
      MAP_INDEX B
where A.geographical_coordinates is not NULL
and B.geographical_coordinates is not NULL;but got the error message:
Error starting at line 1 in command:
SELECT DISTINCT A.mi_prinx,
SDO_GEOM.RELATE
   (A.geographical_coordinates,
    'EQUAL',
    B.geographical_coordinates,
    0.05)
FROM MAP_INDEX A,
      MAP_INDEX B
where A.geographical_coordinates is not NULL
and B.geographical_coordinates is not NULL
Error report:
SQL Error: ORA-13000: dimension number is out of range
ORA-06512: at "MDSYS.SDO_GEOM", line 70
ORA-06512: at "MDSYS.SDO_GEOM", line 2647
13000. 00000 - "dimension number is out of range"
*Cause:    The specified dimension is either smaller than 1 or greater than
           the number of dimensions encoded in the HHCODE.
*Action:   Make sure that the dimension number is between 1 and the maximum
           number of dimensions encoded in the HHCODE.I then tried the following:
SELECT DISTINCT A.mi_prinx,
SDO_GEOM.RELATE
   (A.geographical_coordinates,
    'EQUAL',
    B.geographical_coordinates,
    0.05)
FROM MAP_INDEX A,
      MAP_INDEX B
where A.geographical_coordinates is not NULL
and B.geographical_coordinates is not NULLwhich produced the following error message:
Error starting at line 1 in command:
SELECT
SDO_GEOM.RELATE
(A.geographical_coordinates,
'EQUAL',
B.geographical_coordinates,
0.05) relationship
FROM MAP_INDEX A,
       MAP_INDEX B
Error report:
SQL Error: ORA-13050: unable to construct spatial object
ORA-06512: at "MDSYS.SDO_3GL", line 4
ORA-06512: at "MDSYS.MD2", line 771
ORA-06512: at "MDSYS.SDO_GEOM", line 2622
ORA-06512: at "MDSYS.SDO_GEOM", line 2649
13050. 00000 - "unable to construct spatial object"
*Cause:    This is an internal error.
*Action:   Contact Oracle Support Services.Does anyone have any idea as to what I might doing wrong? The original polygons were created in MapInfo Professional 8 and I am working in 10.2g
I believe Imust be doing something wrong. I looked into SDO_GEOM_VALIDATE but again that produce the same error message as the first one. I have previously created a spatial index and inserted the values into the USER_SDO_GEOM_METADATA view.
I have been able to get the following to work, I was testing out examples online just to see if I could produce a result on an sdo function:
SELECT NAME_OF_FEATURE, SDO_GEOM.SDO_AREA(GEOGRAPHICAL_COORDINATES,M.DIMINFO)
FROM MAP_INDEX, user_sdo_geom_metadata M
WHERE M.TABLE_NAME='MAP_INDEX' AND M.COLUMN_NAME='GEOGRAPHICAL_COORDINATES'
AND geographical_coordinates is not null;When I drew my polygons in MapInfo, they are likely to have gone partly outside of the boundary dimension values inserted in USER_SDO_GEOM_METADATA. Is that likely to be the cause of my problems or something else?
If it is the cause, is there away of setting up Oracle or MapInfo so that anything drawn outside of the dimension area is clipped.
Kind regards
Tim

Hi Tim,
Since Oracle 8.1.6 Oracle has suggested the use of 4 digit SDO_GTYPE values, which encode the number of dimensions in the geometry. Examples of 4 digit SDO_GTYPES include 2001 for a 2D point, 3001 for a 3D point, 2002 for a 2D linestring, 3002 for a 3D linestring, 2003 for a 2D polygon and 3003 for a 3D polygon.. Contrast these with single digit values of 1 for a point, 2 for a linestring, and 3 for a polygon.
My guess is that at least some of your data is loaded using single digit SDO_GTYPE values, and in the function Oracle does not know the dimensionality of the data (is a vertex identified by 2, 3, or four numbers?). You can check this by doing a:
select distinct a.geographical_coordinates.sdo_gtype from MAP_INDEX A;
If any of the values returned are single digit values then you will know this is the problem.
You have a few options.
You can have Oracle automatically fix the data by migrating the data:
execute sdo_migrate.to_current('MAP_INDEX','GEOGRAPHICAL_COORDINATES');
This will not only set the SDO_GTYPE correctly but will also fix any ring rotation problems (ensures exterior rings are stored counter-clockwise, and interior rings are stored clockwise), it will fix ring ordering problems (ensuring an exterior ring is followed by its interior rings), and it will appropiately set values in the SDO_ELEM_INFO_ARRAY.
After you do this you should be good to go. However, if you are using a tool to update the data and it resets the information back, then the problem will continue to plague you. You should check with your vendor if that is the case.
Another option is to change the query to a different signature which uses the SDO_GEOM_METADATA to get the dimensionality of the data. Instead of writing the query as you have, you would change it to:
SELECT SDO_GEOM.RELATE
(A.geographical_coordinates,
C.DIMINFO,
'DETERMINE',
B.geographical_coordinates,
C.DIMINFO) relationship
FROM MAP_INDEX A,
MAP_INDEX B,
USER_SDO_GEOM_METADATA C
WHERE A.geographical_coordinates is not NULL
and B.geographical_coordinates is not NULL
and C.TABLE_NAME='MAP_INDEX'
and C.COLUMN_NAME='GEOGRAPHICAL_COORDINATES';
So either of those should fix the problem you are seeing, but neither of those are the best way to accomplish what you want to do.
If I were you I would follow first set of directions (migrate your data), make sure I have a spatial index on my table:
select index_name
from user_sdo_index_info
where table_name='MAP_INDEX';
If no rows are returned, create the index:
create index MAP_INDEX_SIDX on MAP_INDEX(GEOGRAPHICAL_COORDINATES)
indextype is mdsys.spatial_index;
You could use SDO_JOIN to perform a self-join:
http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28400/sdo_operat.htm#BGEDJIBF
using the EQUAL mask. Note the section on optimizing self-joins.
If you don't have too much data, this might be a start to doing what you want:
create table dups_rowids as
select /*+ ordered */ a.rowid rowid1,b.rowid rowid2
from MAP_INDEX A,
MAP_INDEX B
where SDO_EQUALS (a.geographical_coordinates,b.geographical_coordinates)='TRUE'
and a.rowid <> b.rowid;
create table nodup_rowid (noduprid VARCHAR2(24));
create table dup_rowid (duprid VARCHAR2(24));
set serveroutput on;
declare
rowida varchar2(24);
rowidb varchar2(24);
rowidt varchar2(24);
type myCursor is ref cursor;
acursor myCursor;
cursor c1 is select rowid1,rowid2 from dups_rowids;
begin
for r in c1 loop
rowida := r.rowid1;
rowidb := r.rowid2;
rowidt := NULL;
open acursor for 'select duprid from dup_rowid where duprid = :rowida' using rowida;
fetch acursor into rowidt;
if rowidt is null
then
execute immediate 'insert into nodup_rowid values (:rowida)' using rowida;
execute immediate 'insert into dup_rowid values (:rowida)' using rowida;
execute immediate 'commit';
end if;
close acursor;
rowidt := NULL;
open acursor for 'select duprid from dup_rowid where duprid = :rowidb' using rowidb;
fetch acursor into rowidt;
if rowidt is null
then
execute immediate 'insert into dup_rowid values (:rowidb)' using rowidb;
execute immediate 'commit';
end if;
close acursor;
end loop;
end;
Then your final table would have the geometries from the original table that had no match:
create table MAP_INDEX_NODUPS
as select * from MAP_INDEX where rownum < 1;
insert into MAP_INDEX_NODUPS
(select *
from MAP_INDEX
where ROWID not in
(select ROWID1 from DUPS_ROWIDS));
plus only one of the geometries that were equal:
insert into MAP_INDEX_NODUPS
(select *
from MAP_INDEX
where ROWID in
(select ROWID1 from NODUP_ROWID);
Hope this helps.

Error in RunLogicAgainstSelection:Subscript out of range

Dear experts,
I'm writing a cross application *RUNALLOCATION from application InvCost.
While validating the logic I ot this error saying
"error in RunLogicAgainstSelection: Subscript out of range" and here's the code
*RUNALLOCATION
*FACTOR=1/TOTAL
*APP               WHAT=FINANCE;          WHERE=INVCOST;          TOTAL=<<<
*DIM TIME          WHAT=%TIME_SET%;     WHERE=<<<;          TOTAL=<<<
*DIM DATASRC          WHAT=TEMP;          WHERE=INPUT;          TOTAL=INPUT
*DIM LOB          WHAT=00000;          WHERE=;               TOTAL=
*DIM COSTCENTER          WHAT=122;          WHERE=;               TOTAL=
*DIM MACCT          WHAT=5601;          WHERE=;               TOTAL=
*DIM FACTORY          WHAT=0000F;          WHERE=[L_f]="7";     TOTAL=EACH([L_f]="7")
*DIM INTFAC          WHAT=;               WHERE=NONINTFAC;     TOTAL=EACH(BASE(ALLINTFAC))
*DIM INVACCT          WHAT=;               WHERE=FUC_L;          TOTAL=FFACTOR
*DIM PARNO          WHAT=;               WHERE=NONPARTNO;     TOTAL=EACH([INVTYPE]="L")
*DIM SACCT          WHAT=00;          WHERE=;               TOTAL=
*DIM CATEGORY          WHAT=ACTUAL;          WHERE=<<<;          TOTAL=<<<
*DIM RPTCURRENCY     WHAT=LC;          WHERE=<<<;          TOTAL=<<<
*ENDALLOCATION
From WHAT there's only one value and devid by TOTAL then put into all base members of WHERE.
Factory part is a little tricky cause I'm not sure if it'll give me only base members for the given condition.
Any helpful comments are welcome. Thanks a million...
,Jim Hsu

Hi Jim,
I think you need to use the "USING" clause, as in this simple example. This is where you define the allocation driver.
*RUN_ALLOCATION
*FACTOR USING/TOTAL
*DIM Product What=NoProduct; Where=[ProductLevel]="5"; USING=<<<; TOTAL=<<<
*DIM Account What=MarketingExpense; Where=<<<; Using=Revenue; Total=<<<
*ENDALLOCATION

Image Manager : upload image - error message String index out of range

Hello,
i'm facing an issue with the upload functionality of 'Image Manager'.
When i upload a file, systematicaly an error message pops up :
"error message String index out of range : - XXX"
Where XXX is a value as large as the size of the file.
I have the feeling that the problem may come from the installation of VC.
Did someone encountered this issue ?
Thank you

Hi,
Plz check the below link
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bip/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes.do
Govindu

FPM Error: An internal error occured: String index out of range -4

Hi All,
I have imported the SSA BP to my EP (7.0), however, when I tried to create a custom FPM view & FPM Application for my custom WD application....the system will just prompt the error message "An internal error occured: String index out of range -4".
Can anyone advise what could be the problem? and how to resolve it?
Thanks in advance!
Best Regards,
SY

Hi,
You are trying to call the index of the String whose length is 4., but in the code you may have called from 1 to 4.. which should be 0 to 3.
If you can show the stack trace of the exception, we can pinpoint the code / line.
Just check the WD code..!!
Thanks,
Raags

MP Error: StringIndexOutOfBoundsException: String index out of range: -1

Hi All,
We are using PI 7.1 EHP1, Where in we would like to see the capabilty of User-Module for Conversion of IDoc Messages Between Flat and XML Formats. Gone thru the blog (/people/sap.user72/blog/2005/07/04/get-into-the-zone - Part 2) and maintained the necessary NWA configurations and maintained the necessary module parameters (SAPRelease, SourceJRA, TargetDestination) in Sender File Adapter.
Now the file is not been picked by file adapter upon checking the Comm Channel Monitoring below error:
MP: exception caught with cause java.lang.StringIndexOutOfBoundsException: String index out of range -1
Any help would be highly appreciated.
Thanks in advance

Hi Ramani,
I hope you must have found a solution on this, if not then kindly consider changing your source files, as this error corresponds to only one thing: i.e. DATA Issue. You need to correct the data which you providing to the module for conversion.
I faced this problem and corrected it by just correcting my test file.
Regards,
Nipun Shedhani

Error : CLI0111E Numeric value out of range

Hello:
While extracting data through generic datasources, extraction fails in the source system with the following error message.
Database error text........: "CLI0111E Numeric value out of range.
SQLSTATE=22003 row=1 col=12"
Any idea what does this mean?
Thanks

Hello:
While extracting data through generic datasources, extraction fails in the source system with the following error message.
Database error text........: "CLI0111E Numeric value out of range.
SQLSTATE=22003 row=1 col=12"
Any idea what does this mean?
Thanks

FOR/NEXT loop produces Error in ProcessSQL: Subscript out of range

Hi all,
The 2nd FOR/NEXT loop in the following code produces Subscript ouf of Range error:
*LOOKUP RATEAPP
*DIM MODEL:RATEENTITYDIM= DRIVEDIM.DRIVER_ENTITY
*DIM MODEL:RATEACCOUNTDIM= DRIVEDIM.DRIVER
*DIM MODEL:INPUTCURRENCYDIM = "EUR"
*ENDLOOKUP
// Select lookup and normal members by group
*SELECT(%DRIVERSA%, ID, DRIVEDIM, "[GROUP] = 'A' AND [DRIVER] <> ''")
*SELECT(%MANUALSA%,ID,DRIVEDIM, "[GROUP] = 'A' AND [SOURCE] = 'MAN'")
*XDIM_MEMBERSET DRIVEDIM= %MANUALSA%, "U_TEMP"
*WHEN ACCOUNTDIM.ACCTYPE
*IS *
     *REC(EXPRESSION=1, NOADD, DRIVEDIM="U_TEMP")
*ENDWHEN
*GO
// this is ok
*FOR %MANSET% = %MANUALSA%
     *WHEN DRIVEDIM
     *IS %MANSET%
     *WHEN %VALUE%
     *IS <> 0
               *REC(FACTOR=GET(DRIVEDIM="AD.TEMP"),DRIVEDIM="AD.TEMP")
     *ENDWHEN
     *ENDWHEN
*GO
*NEXT
*XDIM_MEMBERSET DRIVEDIM= %DRIVERSA%, "U_TEMP"
// this is not OK
*FOR %DRIVSET% = %DRIVERSA%
     *WHEN DRIVEDIM
     *IS %DRIVSET%
          *WHEN %VALUE%
          *IS <> 0
               *REC(FACTOR= GET(DRIVEDIM="U_TEMP") * LOOKUP(MODEL),DRIVEDIM="U_TEMP") // * LOOKUP(MODEL)
          *ENDWHEN
     *ENDWHEN
*GO
*NEXT
If I remove the FOR/NEXT loop, this runs fine. The error occurs everywhere - in logic debugger, in DB, in ExecuteBaseLogic if included in Default logic. The REC statement inside the loop can be anything, even as simple REC(FACTOR=1,DRIVEDIM="U_TEMP"), so the problem is in the loop, not anything else. It validates nicely and the compiled logic looks just as expected.
This error could occur sometimes if the membersets are too large. However, in this example, the number of members is rather limited. In the debugger is is possible to limit the data region to single specific intersection and the DRIVEDIM membersets combined is exacly 15.
Could it be possible that the error is caused by member ID-s like AD.1.AVGWAGEGROWTH (length=18)? Is there anything else that can cause trouble?
Any ideas appreciated.
Thanks
Madis
Edited by: Madis Udam on Mar 24, 2011 11:06 AM

I don't think you should have"." dot's in you ID's.
think about it, in your code you have ACCOUNTDIM.ACCTYPE, which represents the account type of the dimension.
If you have an id "AD.1.AVGWAGEGROWTH"; wouldn't it think that you are trying the get a value of some member?
That's just a guess, we established that we wouldn't use any special characters on our id's
It's working so far
Try changing the line
*IS %DRIVSET%
to
*IS "%DRIVSET%"
Edited by: Leandro Cardoso Feliciano on Mar 28, 2011 10:45 PM

I have an alm Tiway host cmd error response 0002: address out of range

Some of the i/o points do not display either as alias or as native memebers.

Hello,
Thank you for contacting National Instruments
I�m not completely clear on your issue. Here are a few questions that should help me answer your questions better:
1) What version of Lookout are you using?
2) Are you using the Lookout Tiway object? If not, what Lookout object are you using?
3) How are you receiving this error message? Is this being received from the Alarms Window?
4) Has this communication with your Tiway ever worked? If so, what has changed since stopped working?
5) Can you give me more information on the way you are connecting and communicating to the Tiway? Also, can you tell me what model of PLC you are using?
6) What data members are not reading correctly from the Tiway object? Which data members, if any, are reading correctly?
I have included a link to a Knowledgebase article which may help out in diagnosing the communications from the Tiway object:
How Do I Create a Communication Diagnostic File for the Lookout Tiway Object?
I hope this helps. Please let me know the answers to the above questions.
Ken S.
Applications Engineering
National Instruments

Compiler error. Ivrt patch out of range: ofst=0xC547

Compiler error occured during full ATE run.

Please report this through technical support, and attach the VI that
this took place in.
Greg McKaskle

FM8 -- Acrobat7 Error: A number is out of range

Similar Messages

Maybe you are looking for