03-02-2009 05:26 PM
Basically, our client has installed a fresh, first-time instance of ACT! v11.0 on a Windows XP SP3 machine. On the “clean” install, ACT! starts just fine. When he installs our FillStaff dll, ACT! kicks back an error during startup :
03-05-2009 02:42 AM
Unfortunately I am not familiar with your product so please excuse what might seem like ignorant questions/comments by me!
Does your product create a new Tab within the Layout and UI or does it create a button etc?
In addition are you creating an additional data source at runtime or is that created at install?
The reason I am asking these questions is that the Null Ref exception could be thrown due to either the client machine running slower or faster than the code anticipates and is not creating the expected objects in the expected order?
On your test machines the data or UI elements may already exist.
I admit its grasping at straws but could be an angle to look at possibly?
03-05-2009 10:02 AM
Thanks for you reply.
Yes, we create a custom tab or two, but ...
As you know, things happen in a specific sequence during ACT! startup. The exe is read and loaded. The Plugin dll's are read and loaded if possible. Act! starts it execution by displaying the splash screen. (I'm not sure of that part of the sequence - not sure if the splash screen can be displayed before all the libraries are added/loaded or not.) Then the splash screen displays various steps during the start up.
The SDK allows for "hooks" at various stages of this startup, including OnLoad, AfterLogon, etc. Our FIRST hook is AFterLogon, because we wnat the user to be able to run non-FillStaff databases as well as ours. ACT! doesn't get to the point of opening - or even ASKING to open - a database, so our code never actually executes at all! Adding those tabs is WAY DOWN in the sequence, no where near the point of failure.
I've never seen an ACT! log file so small - ONE entry. The very first thing ACT! tries to do causes it to crash.
Any other ideas?
03-05-2009 01:34 PM
I would explore the fact that this is a machine specific issue.
Have you had any luck reproducing this in house with the same environment?
Have you checked the machine.config file?
Have you tried reinstalling ACT! on the trouble machine?
You can also increase the verbosity of the ACT log by increasing the values in the ActSage.exe.config file to 4 or 5.
<system.diagnostics> <switches> <add name="ACTCoreSwitch" value="1" /> <add name="ACTUISwitch" value="1" /> <add name="ACTSecuritySwitch" value="1" /> <add name="ACTSyncSwitch" value="1" /> <add name="ACTSyncSetupSwitch" value="1" /> <add name="ACTDesignTimeSwitch" value="1" /> <add name="ACTExtendedSwitch" value="0" /> <add name="ACTReportingSwitch" value="1" /> </switches>
Hope this helps,
03-06-2009 08:49 AM
Thanks for your assistance. We'll look into the areas that you recommend, and post results here.
03-25-2009 05:51 AM
No, increasing the verbosity of the ACT! log file did now show any more info.
Now attempting to manually remove ACT! 11 from the problemed pc, then will re-install ACT!11.0..
One note also; The problemed pc does also have ACT! 6 installed. XP svc pk3 ...
Geoff and I welcome any more suggestions.
Cheers - FSB
04-15-2009 07:09 PM
Yes, it probably is a machine specific issue, but we've tried everything I can think of to resolve it. We've wiped out the HD, reloaded XP and ACT!, and updated the BIOS. What else can we try? We're desperate, and willing to try anything!
What should I look for in the machine.config file?
After setting the verbosity up to 5 on all items, the log is still empty, and the DependentDLL.xml file fails to rebuild.
Anything else you can suggest?