Student access to MyFiles Error - Caused by disallowed Concurrent Logins?

[gomalley]

Got a strange one, and not sure if it is related to our students being restricted to single instance login, when they log into HAP+ and go into MyFiles when they are logged into a school computer they get a warning and no drives, the warning logs this in the server Event Log:

 

An error occurred in Home Access Plus+

 

Page: HAP.AD

 

Something is wrong

 

 

System.Exception: Something is wrong

at HAP.AD.User.ImpersonateContained()

at HAP.MyFiles.API.Drives()

at SyncInvokeDrives(Object , Object[] , Object[] )

at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

 

 

at HAP.AD.User.ImpersonateContained()

at HAP.MyFiles.API.Drives()

at SyncInvokeDrives(Object , Object[] , Object[] )

at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

 

I am waiting to hear if it occurs to them when accessing it from home, or only when they are already logged onto a computer in school (which would actually not be a problem beyond our initial introduction to HAP+ as they are not likely to need it in school where they have the same drives mapped on the computer anyway)!

 

Just wondering if anyone else had experience of this?

Thanks

Guy

[nickbro]

Odd, that shouldn't do that. Are you sure that all users have local logon rights to the server your running HAP+ from?

[gomalley]

Don't think a student user should be able to login to the server, so is that what is causing the error?

[nickbro]

yep, most of use run HAP+ on a web/remote access member server to avoid compromising and dc or valuable server

[gomalley]

I only wish I had a spare server to do this on, will have to build something up and test it.

Thanks

[nickbro]

No virtual server? Windows Server 2008 R2 standard comes 1 virtual OS cal as well for hyper-v

[gomalley]

I wish, my servers are all still 2003, as my predecessor spent stupid amounts on physical servers only two years ago and they have 2003 on as RM didn't support 2008 on CC4 at the time!

 

I think I have found it out though, looked at my test student user that it appeared ok for, and a user it didn't and the difference was membership of the CC4 EasyLink Users Security Group, so I've added that (thought they all had it anyway) and will see if that then works.

 

Many Thanks for your continued support with this.

Guy

[gomalley]

The group membership was the fix, so all working good now

Thanks

Guy

[nickbro]

Good to hear