Monty1157

Hi All, I'm wondering if you can help me out on this. I've spent more than a couple of weeks, on and off, banging my head off a brick wall on the setup of this application (v8.7 - The latest release). Every time I go through the setup, which completes successfully, and get the login page coming up, no matter what login I use, be it my own, the domain administrator account, a test staff account, or even a test pupil account, the page just sits trying to connect for a while, then refreshes back to requesting a login. On checking the event viewer on the IIS server itself, I always get the following errors for every attempted login: In the Application Log: Event 1000: Application Error Faulting application w3wp.exe, version 7.0.6002.18005, time stamp 0x49e023cf, faulting module msvcrt.dll, version 7.0.6002.18005, time stamp 0x49e0379e, exception code 0xc00000fd, fault offset 0x0000c7b8, process id 0x%9, application start time 0x%10. Event 1027: .NET Runtime Application: w3wp.exe Framework Version: v4.0.30319 Description: The process was terminated due to stack overflow. In the System Log: Event 5010: WAS A process serving application pool 'HAP' failed to respond to a ping. The process id was '2160'. Looking up on the web (And on this site, but if I've missed a post, forgive me, as I may have been putting in the wrong search terms), for the System Log WAS error, the only solutions to tracing where the problem resides within the web application was to setup debug stack traces, and a programmer I am not, so even although I could do this, the output probably wouldn't mean much to me, and certainly, even if I'd gotten that far, writing a patch solution to something is deffo right out my league. VBScript and Powershell? Yes. .NET C#? No. On the errors that present themselves in the Application Log, most solutions revolved around re-installing IIS, to which I've done. Several times. I've also tried the application on IIS7 (2008 32 and 64 bit) and IIS7.5 (2008R2), and all give the exact same result. Apart from the OS, the setup was done as put on the videos, and in the documentation: IIS, .NET4.0 (Full, not client), and obviously an AD domain (currently at 2003 forest and domain levels). The 2008 IIS server is a domain member, but not a DC. I've checked, double checked, and triple checked all folder permissions, went through the V7 video tutorial, and the V8 beta video tutorial, quadruple checked the documentation, and everything checks out, and the setup, as I said, works perfectly. Any help on this would be very much appreciated.

In all honesty, it's something I've not looked at. I only rolled out the software install earlier this week, and I was assuming that the staff would be putting the files into their personal or shared folders on the network. I've not had any complaints regarding the use of the cameras under this 5.9 install, but although the person who requested this knows that the software's now there, he might not have had the time to test things out in that respect. I'm sure I'll get another call logged to complain about this, if there is a save to network folder problem. Otherwise, all I can suggest is that you follow the links above that Arthur provided, hack the .msi/add the reg keys (delete as applicable ), and try that and see how it goes.

I installed 4.1.4 after removing the launch condition and got the same error. Little messing about comparing the registry keys on the 'corrupted' install with an install done via the setup file revealed that the locale keys in the registry were missing. There's two ways to fix this: Push the correct registry settings via an ADM in group policy/or login script, or change the registry table in the original .msi file. Personally, I'm going for the .msi hack as it's neater all round I think. Registry keys are stored in HKLM/Software/Flip Video/FlipShare and are: country: uk language: en_uk locale: en_uk region: international In the .msi file, in the registry table, it's the third entry to sixth entry on the table you need to change. Same as above. On another note, whilst messing about with all of this, it also downloaded and gave me the chance to update to 5.9, which I did, and I grabbed the new 5.9 .msi out of the %temp% dir. This changed the registry settings to just: locale: en_uk region: international useagestatsenabled: 1 I changed useagestatsenabled in the registry to 0 with no problems, and changed it, and the other two keys, in the .msi registry table (third option down in the 5.9 .msi). Tested both the 4.1.4 install with changed registry table values, and the 5.9 install with changed values, as a GPO install on clean computers, and both put in the correct registry values and worked first time. Lastly, I will say that I noticed that the 4.1.4 install installed 3ivx as well, but a clean install of 5.9 doesn't. I've no idea how much trouble that will cause if it's missing, but I'm sure I'll find out. Cheerie, Monty

Hi All, From the initial script link above, I managed to create the following VB Script to create a user and home folder from a spreadsheet, fill in all the user details into the account, set the password (as well as setting it to change at first login), and point it to the correct location of the home drive. I'm no coder, so please forgive the utterly horrible coding discipline and spelling mistakes. I'm sure someone could probably do a much better job, but it works with very little changes required when switching year/OU/domain and I'm happy with it. All variables to be changed are at the top of the code, and are commented to describe what they are. Hopefully you'll find some use out of it. Spreadsheet setup is also in the comments section at the top of the code. ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ' Name: Createuser.vbs ' ' Author: Monty ' ' Original script coded by Fox / The Scripting Community (http://gallery.technet.microsoft.com/ScriptCenter/en-us/bc330a9b-929d-49fd-8c03-ab69b6fc4fd6) ' ' Several hundred hacks nicked from all over the interwebs. ' ' Build date: 29/07/2010 ' ' Last ammened by: Monty ' ' Last ammendment date: 03/08/2010 ' ' Excel Spreadsheet Layout Format: Column headers and Year on first row. Year is a special header in 6th column for description field(e.g. 2010 Student) ' ' Headers in column order: ' ' 1 SAM ' ' 2 Given Name ' ' 3 Surname ' ' 4 Display Name ' ' 5 Password ' ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Dim oRoot Dim oDomain Dim oCurrent Dim strExcelFileName Dim oOU Dim OUFind Dim count Dim createcount Dim skipcount Dim strCompleteOU Dim strStaticDir Dim strHomeDir Dim strHomeDrive Dim strStudentGroup Dim strDirectory Dim strCommon Dim strXcacls Dim strRun Dim objFolder Dim objShell Dim filesys Dim filetxt Dim fileLoc Const ForWriting = 2 count = 0 createcount = 0 skipcount = 0 OUFind = 0 ' Variable to hold completed folder path. strDirectory = "" ' Partially omplete OU string for where the users are being placed. Keep the setup as it currently is. There's no LDAP:// at the front. strCompleteOU = "OU=2010 Students,OU=school Students,OU=School Users,OU=School Name,OU=Schools,DC=edu,DC=lan" ' Complete OU string for the group that the users are being placed into. strStudentGroup = "LDAP://CN=G SchoolStudents,OU=School Groups,OU=School Name,OU=Schools,DC=edu,DC=lan" ' Drive letter for the home folder that's entered into the user account on creation. strHomeDrive = "W:"' Initial part of the folder structure where the user folders are being placed into. ' Actual folder location on the server this is being run from. strStaticDir = "D:\Studenthome\2010\" ' Initial part of the UNC pathname to the user folder. This is placed into the user account on creation. strHomeDir = "\\school-server\studenthome\2010\" ' Location of the xcacls.vbs script needed for this script to work. ' Yes it needs three sets of double quotes to work, so that the full path works if there's one or more spaces in there. (e.g "C:\Program Files\XCacls\xcacls.vbs") strXcacls = """D:\temp\xcacls.vbs""" ' Excel Spreadsheet name (e.g. d:\temp\import.xls) strExcelFileName = "d:\temp\matched.xlsx" ' Location for output log file. No triple quotes needed here for whatever reason. fileLoc = "D:\temp\output.txt" ' Used to count the amount of users in the OU we're adding to. Sub FindOU(ObjOU) For Each FoundObject in ObjOU If FoundObject.class="organizationalUnit" Then FindOU(FoundObject) End If If FoundObject.class="user" Then count=count+1 End If Next End Sub ' Start. Prepare variables and get the domain name. Set objArgs = WScript.Arguments Set oRoot=GetObject("LDAP://rootDSE") Set oDomain=GetObject("LDAP://" & oRoot.Get("defaultNamingContext")) Set oCurrent = GetObject("LDAP://" & strCompleteOU) ' Opens log file for writing. If log file is already present, it will be overwritten, if not it will be created. Set filesys = CreateObject("Scripting.FileSystemObject") Set filetxt = filesys.OpenTextFile(fileLoc, ForWriting, True) ' Write a little header on the file to give some idea of what it contains. filetxt.WriteLine("SAM Common Name") ' Opens Excel and loads the workbook given in the var strExcelFileName. Set objExcel = CreateObject("Excel.Application") Set objWorkbook = objExcel.Workbooks.Open(strExcelFileName) ' Start at row two in the spreadsheet. Row 1 is left for column headers. intRow = 2 ' Do statement until the first column is read as blank. Which means no breaks in the data. Please. Do Until objExcel.Cells(intRow,1).Value="" On Error Resume Next ' Set initial full OU layout. Adjust the strCompleteOU variable manually above. Set objOU = GetObject("LDAP://"& strCompleteOU) strCommon = "LDAP://cn="& objExcel.Cells(intRow,4).Value &"," & strCompleteOU Set objUser = GetObject(strCommon) If not objUser.sAMAccountName = objExcel.Cells(intRow, 1).Value Then ' Create user from common name in fifth column. Set objUser = objOU.Create("User", "cn=" & objExcel.Cells(intRow,4).Value) ' SAM account name from first column. Rest is kind of obvious. objUser.sAMAccountName = objExcel.Cells(intRow, 1).Value objUser.GivenName = objExcel.Cells(intRow, 2).Value objUser.SN = objExcel.Cells(intRow, 3).Value objUser.Mail = objExcel.Cells(intRow, 1).Value & "@school.sch.uk" objUser.userPrincipalName = objExcel.Cells(intRow, 1).Value & "@edu.lan" ' Special setting next. First row, sixth column is the description (e.g. 2010 Student). objUser.description = objExcel.Cells(1,6).Value objUser.displayName = objExcel.Cells(intRow,4).Value ' Need to do a set info here, otherwise the account won't have been created and will not take some of the following settings correctly. objUser.SetInfo objUser.SetPassword objExcel.Cells(intRow, 5).Value ' Force user to change password on the next login. objUser.Put "pwdLastSet", 0 objUser.AccountDisabled = FALSE ' Add user to the global student group. set objGroup = GetObject(strStudentGroup) objGroup.Add(strCommon) ' Then lets create the home drive. strDirectory = strStaticDir & objExcel.Cells(intRow, 1).Value Set objFSO = CreateObject("Scripting.FileSystemObject") ' Create the folder from the above concantinated string. Set objFolder = objFSO.CreateFolder(strDirectory) Set objShell = CreateObject("WScript.Shell") ' Run the cscript.exe session invisible, and let the calling VBScript wait for the called VBScript to finish. ' Change the 0 to a 1 for the window to momentarily pop up when this command is being run. ' We only add the user to the account here as we've set the parent dir to not inherit anything from further up the folder tree. ' This means that when the folder's created it should initially only have the Administrators group with full control and the following just adds in the user. runCommand = "cscript.exe " & strXcacls & " " & strDirectory & " /T /E /G EDU\" & objExcel.Cells(intRow, 1).Value & ":F" objShell.Run runCommand, 0, True objUser.homeDirectory = strHomeDir & objUser.sAMAccountName objUser.homeDrive = strHomeDrive ' Again use set info to put it all into the account. objUser.SetInfo WScript.echo objUser.sAMAccountName & " " & objUser.displayName & " " & "created." createcount = createcount + 1 Else ' Write SAM and display name to the text file if this object already exists elsewhere in the domain. filetxt.WriteLine(objUser.sAMAccountName & " " & objUser.displayName) skipcount = skipcount + 1 End If ' Finally, increment the row by one, and do the loop again intRow = intRow + 1 Loop ' Close workbook and quit Excel. First line forces a confirmation that the file has been saved even although no changes were made to it. ' This is for scripting compatibility with Excel 2007. objExcel.ActiveWorkbook.Saved = True objExcel.ActiveWorkbook.Close objExcel.Application.Quit ' Close output log file. filetxt.Close ' Finally, report how many users are in the new OU. Just so you can match up the script with what's in the spreadsheet. FindOU(oCurrent) WScript.echo "Total users created: " & createcount WScript.echo "Total users skipped: " & skipcount WScript.echo "Total users in the OU: " & count Cheerie, Monty