Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationActive Directory 01.00.04.36979 Beta Active Directory 01.00.04.36979 Beta
Previous
 
Next
New Post
6/20/2008 3:45 PM
 

Hi Mike,

I'm going to try your suggestion of a manual rip-out and reinstall.

If I run the uninstall of the provider (whether it is enabled or not) I get an error.  When I reinstall it, it already "knows" my domain and user information, and since I cannot get the roles to sync on production (works fine in test), I have to think perhaps I'm not really running your current code.  FYI, and PS, I didn't see any VB files in the source download, is that something you might look at with your next release?

Here's what the uninstall process said:

Package Uninstall Logs
 
StartJob Reading Installation Manifest file
Info Reading Component Manifest - AuthenticationSystem
Info Parsed Authentication Manifest Successfully
Info Reading Component Manifest - Assembly
Info Reading Component Manifest - File
Info Reading Component Manifest - Config
EndJob Manifest file finished successfully
 
StartJob Starting Package Uninstall
Info Starting Package Uninstall - DNN_ActiveDirectoryAuthentication
Info Starting Component Uninstall - AuthenticationSystem
Info ActiveDirectory Authentication unregistered successfully
Info Component uninstalled successfully - AuthenticationSystem
Info Component Uninstall Successful - AuthenticationSystem
Info Starting Component Uninstall - Assembly
Info Assembly unregistered - bin\Providers\DotNetNuke.Authentication.ActiveDirectory.dll
Info Deleted - bin\Providers\DotNetNuke.Authentication.ActiveDirectory.dll
Info Component uninstalled successfully - Assembly
Info Component Uninstall Successful - Assembly
Info Starting Component Uninstall - File
Info Deleted - App_LocalResources\Login.ascx.resx
Info Deleted - App_LocalResources\Settings.ascx.resx
Info Deleted - Login.ascx
Info Deleted - Settings.ascx
Info Deleted - license.txt
Info Deleted - WindowsSignin.aspx
Info Component uninstalled successfully - File
Info Component Uninstall Successful - File
Info Starting Component Uninstall - Config
Info Component uninstalled successfully - Config
Info Component Uninstall Successful - Config
Failure ExceptionSystem.Data.SqlClient.SqlException: DELETE statement conflicted with COLUMN REFERENCE constraint 'FK_PackageAssemblies_PackageAssemblies'. The conflict occurred in database 'TPD_Net', table 'Assemblies', column 'PackageID'. The statement has been terminated. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Data.SqlDataProvider.DeletePackage(Int32 packageID) at DotNetNuke.Services.Packages.PackageInfo.UnInstall() at DotNetNuke.Services.Packages.InstallerInfo.UnInstall() at DotNetNuke.Services.Packages.Installer.UnInstall()
 
--

Roberta

 

 
New Post
6/20/2008 3:53 PM
 

The .vb files are in the .resources file. Jut change the extension to .zip.

 
New Post
6/20/2008 4:25 PM
 

Aha!   Thanks!  Now I have my weekend reading.

 
New Post
6/20/2008 6:16 PM
 

Hi Mike, - Ok here's the latest.  there were some left over files, so I deleted those and removed the .dll from the bin/providers folder. In the db, I removed a line from the authentication, packages and assemblies tables. Attempted to reinstall the module and received the same error as shown in my first post (where it looked like it couldn't copy the web.config). So, the error shows that it basically rolled back the installation. In the site files, a folder "ActiveDirectory" and a sub folder for local resources was left behind, but no files; just empty folders. But, all the database entries were still there - nothing was rolled back here. Either way, not a successful installation. I'm just curious if you are doing any kind of checking to see if the entry already exists in the config file. If so, do you need to copy and back it up? I'm saying this because it would be very easy to add the one line web.config entry and continue with the installation rather than having the entire provider fail because it can't access my config file. I remember back when dnn 4.0 was just getting put out there, I was having a heck of a time trying to get dnn installed on a godaddy hosting account because they didn't give write access to the root. I don't know, it just seems like maybe you could provide an option to manually add the web.config entry instead of a complete failure. also, just thought you may be interested in seeing what's left behind when the installation fails. If you have any more suggestions, I would be VERY happy to hear them! :-) Thanks so much, Mike. You're doing a great job on this provider and all the help you provider (so quickly might I add) to the community.


Check out the open source DNN Testimonials project on CodePlex and help build it!
 
New Post
6/21/2008 2:30 AM
 

Unfortunately I have no control over the actual installation code for the provider. That's all handled by the core. If you want to try installing it so that nothing is written to the web.config you could extract the .dnn file, edit it, and put it back into the .zip file.

If you remove the <component type="config">all the config lines</component> from the .dnn file nothing is written to the web.config. And now that I look at the .dnn file it's supposed to overwrite the line if it already exists.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationActive Directory 01.00.04.36979 Beta Active Directory 01.00.04.36979 Beta


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out