- This topic is empty.
October 26, 2009 at 8:32 pm #5416
I have a rather peculiar issue. When trying to delete or add a package of any type in the WDM Console, I have been receiving the ActiveX error 429 “ActiveX component can’t create object”.
Win2K3 server with IIS 6 and WDM 4.5.3
SQL 2005 DB on separate W2K3 server
All the prerequisite services are started and the SQL server is online and functional. Earlier last week, there was a GPO issue that was resolved in regards to the SAM service.
Anyone have any clues??October 30, 2009 at 7:03 pm #16845
I am still experiencing these errors and am at a loss as to why they are occuring.
Anyone seen this type of error before?November 2, 2009 at 8:51 am #16852
You are using the WDM Enterprise Version?
Can you check the ftprootrapport folder if the corresponding folder to the packages you want to delete still exist? If not, create ablank one and try to delete the package again.
CGNovember 2, 2009 at 5:03 pm #16867
Yes I do have an Enterprise License. The issue hasn’t occured before in over a year of using the product. The folder was deleted, but when I recreated the folder or try to add a new package, I get the same ActiveX errors.
I tried making a fresh server and the same issues occur, so the only things I know that are the same is the following:
1) The Microsoft patches applied to the server.
2) The GPO that is applied to the server.
3) The SQL server build that the database is installed on.
4) The version of WDM that is installed.
I am going to try and eliminate the top two reasons for I believe it is there where the problem is.November 2, 2009 at 9:36 pm #16871
I would start with eliminating the GPO first – at least for the time of testing.
CGNovember 3, 2009 at 7:12 pm #16878
Well at least I know it is the GPO. I built a WDM server with the same SQL DB build, same WDM version, and the same Microsoft patches. The only difference is I placed the computer account in an OU without GPOs applied to it. The ActiveX errors are gone so now it is just a matter of finding the offending GPO setting that is screwing this up.November 4, 2009 at 3:21 pm #16889
Cool. Let us know your findings, please.
- You must be logged in to reply to this topic.