when checking a file larger sometimes docman functionality gives an error “Object reference not set to an instance of an object” The reason for the error is happen due to the IIS server limited the maximum allowed content size. Changing this parameter can fix the problem.
To adjust the parameter need to login to the relevant IIS server machine(IFS home server) and run the IIS manager (Check image1).
Then click on the server name and double click on the ‘Request Filtering’ (image 2) .
In the next window click on the Edit Feature Settings…
Now you can adjust the maximum allowed length as highlighted below.
Hope this will helps.
Hi Amila
This is not suitable for IFSMWS because there is no IIS server. Is there any option to limit upper file size uploaded into IFS Applications(IFS9, IFS10)?
BS
Piotr
Side question but are these “Large” files being stored in the Oracle or an FTP site?
The DB storage really only benefits documents or at least files with recognised text, photos or videos etc are best stored outside of the db to prevent issues with db size which can occur…
Customers by default store all files in the Oracle LOB’s. So they realized problem after LOB tablespace is so big.
Anyway, is there any possibility to move attachment from LOB stored repository to FTP for example?
Piotr
Where these documents (or LOB’s) will be stored is depend on the repository defined in the DOCMAN settings. If the repository is set as database, then the document will be stored in a table as LOB. You can always move documents between repositories, like between DB and FTP etc
But I want to know is there any easy way to move repository between LOB and for example FTP?
It about 200GB.
Hi
An Object is an instance of a Class , it is stored some where in memory. A reference is what is used to describe the pointer to the memory location where the Object resides. The message "object reference not set to an instance of an object" (NullReferenceException) means that you are referring to an object the does not exist or was deleted or cleaned up. In order to prevent the error, objects that could be null should be tested for null before being used.
if (mClass != null)
{
// Go ahead and use mClass
mClass.property = ...
}
else
{
// Attempting to use mClass here will result in NullReferenceException
}
A NullReferenceException typically reflects developer error and is thrown in the following scenarios:
- Forgotten to instantiate a reference type.
- Forgotten to dimension an array before initializing it.
- Is thrown by a method that is passed null.
- Get a null return value from a method, then call a method on the returned type.
- Using an expression to retrieve a value and, although checking whether the value is null.
- Enumerating the elements of an array that contains reference types, and attempt to process one of the elements.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.