Problem connecting Groupwise system from ASP.NET

[jpatel]

I am trying to Connect Groupwise and change password .It works fine in VS2005 environment but fails when deployed on IIS.

Here is my sample code...

Imports AdminTypeLibrary
 
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
 
Dim PO, Dom As String
Dim objDomain, objDom, objPOs, objPO, objCurPO As Object
Dim objdlists, objdlist
Dim DomPath As String = "Z:\GRPWISE\DOMAIN"
 
PO = "<PO String>"
Dom = "<Domain>"
 
Try
Dim objAdminSystem As Object
objAdminSystem = CreateObject("NovellGroupWareAdmin")
 
<------------following line fails per error "COM Exception : could not connect to domain database" in IIS , but works fine when running it in the VS2005 environment
objDomain = objAdminSystem.Connect("Z:\GRPWISE\DOMAIN")

i have tried impersonation to admin user using web.config,even added ASPNET user to admin group,given full permission to virtual directory and set IIS running in lowest secure mode,gave IIS Admin service rights to interact with desktop but nothing works...

[kenobewan]

Have you created a domain or virtual directory to run under for IIS?

[jpatel]

Yes i have created virtual directory and i am accessing pages using http://localhost/MyDir/Mypage.aspx. Acutual problem is that IIS is blocking call to COM Library (or any executable that calls COM library) for some reason and VS2005 inter web server is not blocking it so code woeks fine in VS2005 but fails in IIS. I have tried everything with IIS from giving IIS worker process admin privilages to impersonating user in web.config and even giving NTFS permissions to ASPNET user to read/write to everything but nothing is working for me...

[Shashi Sadasivan]

is the firewall blocking it?

there should be incoming firewall rules (i am not aware of the setup of this)
probably it could be the firewall causing this issue.

You cud try diabling the firewall from admistraion and try it (this firewall is different to windows firewall)

[kenobewan]

Your reference Z:\GRPWISE\DOMAIN may be the problem in my opinion.

[jpatel]

Finally i have done it,no impersonatin or permission issue is there.following code to change password on groupwise
runs on IIS without any change in IIS
Configuration,only thing is i had to login in novel using code and map drive from code so that its available to whtever user
account IIS process is using. NovellGroupWareAdmin library(gwcmb1.dll) is part of groupwise client installation and NWsess.ocx is available from novell site and both should be included in project.

loNWSess = CreateObject("NWSessLib.NWSessCtrl.1")

loNWSess.Bindery = True
loNWSess.RunScripts = False
loNWSess.DisplayResults = False


' Attempt to log the user into the novell server
ValidateUser = loNWSess.Login(lsServer, _masterUser, _masterPassword, False)

loNWSess.DriveMappings.Add("y:", "Z:\GRPWISE\DOMAIN", True)


objAdminSystem = CreateObject("NovellGroupWareAdmin")

objDomain = objAdminSystem.Connect("y:")

Dim match As Match = New Regex("(\S+)\.(\S+)\.(\S+)").Match(UserName & "." & "PO.DOMAIN")

If Not match.Success Then
Throw New Exception("Unable to parse User ID")
End If

Dim user As Object
user = objAdminSystem.Users.Item(match.Groups.Item(1).Val ue.Trim, match.Groups.Item(2).Value.Trim,match.Groups.Item( 3).Value.Trim)
user.SetPassword(NewPassword)

[veei]

I think the reason NWSess.OCX and GroupWareAdmin only work when you use CreateObject rather than As New like you are supposed to in .NET, is because of something I was reading about called Apartment Threading mode (Single vs Multi). MTA vs STA. Works fine in VBScript but anything using .NET to call the API or COM won't work. I tried with PowerShell and ASP.NET. Both with the same results.

I tried using your solution and it worked for me as well..... for a while. But, because it keeps mapping a drive... after a while, it will lose the connection to the drive or have problems remapping.

Perhaps it is the way I'm putting in the code but it is not a stable solution for me. Wish I could just authenticate and access the \\servername\share\db instead of mapping a drive that doesn't even show on server.

Is your program running stable after a long period of time?