Guys,

I am having problems with Excel 2000 to Excel 2003 dll in production.

I am having version 2003 in my PC and I used the below code change to
open password protected excel files in my application. My application
is in ASP.NET

From:
objExcel = New Excel.Application
objExcel.Workbooks.Open(strFileName, , False)
To:
objExcel = New Excel.Application
objExcel.Workbooks.Open(strFileName, , False, ,
file_pwd.Trim)

The above change is working fine in my local PC.

I moved the code change into production where I had Excel 2000
version.

It did not work. I got an error:

Object reference not set to an instance of an object. at
Excel.Workbooks.Open(String Filename, Object UpdateLinks, Object
ReadOnly, Object Format, Object Password, Object WriteResPassword,
Object IgnoreReadOnlyRecommended, Object Origin, Object Delimiter,
Object Editable, Object Notify, Object Converter, Object AddToMru,
Object Local, Object CorruptLoad) at
SentryDotNet.FileParsing_FTP.FTPLoadFile(String strFileName, Int32
intClientID)


So I requested for Excel 2003 version in production and Server team
has installed Version 2003 in production server

Now I am getting different error as below

Server execution failed at
SentryDotNet.FileParsing_FTP.FTPLoadFile(String strFileName, Int32
intClientID)

I am really worried. I called server team and found out that they did
not restart the server after they installed 2003 version the reason
being it had not asked for restart.

Do we have to restart the server after installing 2003?

How to resolve the above issue?

Please help.. Do we have to register the Excel dll into production?
How to do this?

Please help.

Thanks.

I don't think the restart is required. But they have to open Excel under the
user account your product works and answer all the questions.

Also, check if they installed 2003 PIAs. As far as I remember, there is an
item called ".NET support" or such when you install Office 2003.

Also, the file you open can contain macros. Make sure that Excel behaves in
the way you expect with such files. All-in-all, try to open in Excel the
file you process.

Regards from Belarus (GMT+2),

Andrei Smolin
Add-in Express Team Leader


wrote in message
...
Guys,

I am having problems with Excel 2000 to Excel 2003 dll in production.

I am having version 2003 in my PC and I used the below code change to
open password protected excel files in my application. My application
is in ASP.NET

From:
objExcel = New Excel.Application
objExcel.Workbooks.Open(strFileName, , False)
To:
objExcel = New Excel.Application
objExcel.Workbooks.Open(strFileName, , False, ,
file_pwd.Trim)

The above change is working fine in my local PC.

I moved the code change into production where I had Excel 2000
version.

It did not work. I got an error:

Object reference not set to an instance of an object. at
Excel.Workbooks.Open(String Filename, Object UpdateLinks, Object
ReadOnly, Object Format, Object Password, Object WriteResPassword,
Object IgnoreReadOnlyRecommended, Object Origin, Object Delimiter,
Object Editable, Object Notify, Object Converter, Object AddToMru,
Object Local, Object CorruptLoad) at
SentryDotNet.FileParsing_FTP.FTPLoadFile(String strFileName, Int32
intClientID)


So I requested for Excel 2003 version in production and Server team
has installed Version 2003 in production server

Now I am getting different error as below

Server execution failed at
SentryDotNet.FileParsing_FTP.FTPLoadFile(String strFileName, Int32
intClientID)

I am really worried. I called server team and found out that they did
not restart the server after they installed 2003 version the reason
being it had not asked for restart.

Do we have to restart the server after installing 2003?

How to resolve the above issue?

Please help.. Do we have to register the Excel dll into production?
How to do this?

Please help.

Thanks.

I did n't really get you.. What is the meaning of "they have to open
Excel under the
user account" ? How could they do this?

What is 2003 Pl ? They installed Office 2003 and selected Excel 2003
component

The file has no macros in it and I can open the same file in the
application running in my local machine.


On Dec 13, 10:40 am, "Andrei Smolin [Add-in Express]" <andrei dot
smolin @ add-in-express dot_com wrote:
I don't think the restart is required. But they have to open Excel under the
user account your product works and answer all the questions.

Also, check if they installed 2003 PIAs. As far as I remember, there is an
item called ".NET support" or such when you install Office 2003.

Also, the file you open can contain macros. Make sure that Excel behaves in
the way you expect with such files. All-in-all, try to open in Excel the
file you process.

Regards from Belarus (GMT+2),

Andrei Smolin
Add-in Express Team Leader

wrote in message

...

Guys,

I am having problems with Excel 2000 to Excel 2003 dll in production.

I am having version 2003 in my PC and I used the below code change to
open password protected excel files in my application. My application
is in ASP.NET

From:
objExcel = New Excel.Application
objExcel.Workbooks.Open(strFileName, , False)
To:
objExcel = New Excel.Application
objExcel.Workbooks.Open(strFileName, , False, ,
file_pwd.Trim)

The above change is working fine in my local PC.

I moved the code change into production where I had Excel 2000
version.

It did not work. I got an error:

Object reference not set to an instance of an object. at
Excel.Workbooks.Open(String Filename, Object UpdateLinks, Object
ReadOnly, Object Format, Object Password, Object WriteResPassword,
Object IgnoreReadOnlyRecommended, Object Origin, Object Delimiter,
Object Editable, Object Notify, Object Converter, Object AddToMru,
Object Local, Object CorruptLoad) at
SentryDotNet.FileParsing_FTP.FTPLoadFile(String strFileName, Int32
intClientID)

So I requested for Excel 2003 version in production and Server team
has installed Version 2003 in production server

Now I am getting different error as below

Server execution failed at
SentryDotNet.FileParsing_FTP.FTPLoadFile(String strFileName, Int32
intClientID)

I am really worried. I called server team and found out that they did
not restart the server after they installed 2003 version the reason
being it had not asked for restart.

Do we have to restart the server after installing 2003?

How to resolve the above issue?

Please help.. Do we have to register the Excel dll into production?
How to do this?

Please help.

Thanks.