Archives of the TeradataForum
Message Posted: Tue, 01 Jul 2003 @ 19:32:42 GMT
Upgrade from 4.1.1 to 4.1.3 should not have changed the responses received from PMPC. (Although I can not fully rule out an accidentally introduced regression in the DBS/PMPC code)
The fact that you are seeing the problem only occasionally does lead me to beleive that it is probably data related. If it were a mismatched dll (if you have installed Teradata Manager 6.0, for example, and your path structure is such that it is picking up the wrong version of [probably] monpm.dll) I would expect it to fail all the time.
The problem with Excel is that everything is treated as a variant so we have no idea which variable it might be refering to. (A VB app might narrow it down a bit.)
Do you by any chance have any app running that is dumping the Session information at the same time this app is running? (The Session Information app in Teradata Manager allows you to do this - use the menu: Tools, Log to file.) That would allow you to see what the data looks like at the time of the problem. (Or maybe to see a different [better?] error message.)
Is this happening every night or only occasionally? Does the excel app crash when it hits this problem? (If so, you may be able to recover by adding an 'On Error' block to trap and 'eat' the error, then continue.)
If you need help debugging this please feel free to contact me directly.
|Copyright 2016 - All Rights Reserved
|Last Modified: 15 Jun 2023