TommyGun665

There is a better way. I remove my services through Add/Remove Programs. These installers are built with Windows in mind and can be removed using normal window uninstalls.

Fixed Heres how: The restarting of the Server did not fix matters. The fix came after uninstalling IIS 5.0 and reinstalling IIS 5.0 and then installing the Framework again (version 1.0). Warning: You will have to set up all those "Virtual Directories" for all your applications...and IIS 5.0 interface is TERRIBLE at doing it. I get the most success by right-clicking on the directory with the application...then properties...then Web Sharing...and creating a new alias. If it is in a sub-directory like mine (ie. /dev/MyApplication) make sure that you include that in the alias. Conclusion: I may be wrong on this...but my lesson is...If you are using Visual Studio 2002 to develop ... DONOT install Framework 1.1 or your validation controls will experience backward compatibility problems...BUT if you happen to have done all this and wish to get back to just 1.0...then you will need to start by uninstalling IIS 5.0. It really terrible...but then again it might be because I don't know enough about IIS and the Framework. What I do know from this is that: IIS determines which of those aspnet client files directories is going to be used...and if its not using the correct one...then reinstall IIS and install the frame work again. :(

Unable to find script....Correction I'd like to correct a piece of the information I supplied and update what else I've tried: Correction: Originally I said that the /aspnet_client/system_web/1_0_3705_288/WebUIValidation.js file it was looking for existed in the WINNIT directory. However this is not important...as the javascript generated is looking for it under the wwwroot directory of IIS...and UNDER THERE the '_288' is an '_0'. So really the directory does not exist. Since then I've done the following withoug results: 1) Re-installed Framework 1.0 on the deployment server 2) Un-installed Framework 1.1 and Framework 1.0 on the development server 3) Re-installed the Framework 1.0 on the development server As it stands...everything works fine on the development server (which DOES NOT have the directory _288...but also does not fail because it asks for the _0 directory!...I can see this in the generated source in the browser) So I'm going to try restarting the deployment server (where the source is looking for the _288 directory...and see if IIS doesn't start looking in the _0 directory. {Sigh} Hope its successful.

Working on a development platform with both 1.0 and 1.1 framework installed. Deploying on a platform with only 1.0 (because 1.1 was causing problems validating controls). I'm probably answering my own question here but I keep getting the error: "Unable to find script library '/aspnet_client/system_web/1_0_3705_288/WebUIValidation.js'. Try placing this file manually, or reinstall by running 'aspnet_regiis -c'." So running the aspnet_regiis doesn't fix a thing. The directory as described in the error message is located under WINNT/system32/inetsrv/iisadmin and the file it complains of exists. Any Ideas? Background information: Visual Studio .NET 2002 Windows 2000 platforms IIS 5.0

OK problem fixed...but a rather puzzling solution. I hope I don't run into problems in the future. Basically I uninstalled .NET Framework 1.1 from the problem server. Installed .NET Framework 1.0 and then installed .NET Framework 1.1 again. This should have mimicked my development environment. However it still did not function...it would skip my "required field" validation controls. So as a last desperate move I uninstalled the .Net Framework 1.1....and PRESTO it works. CONCLUSION: It would seem they are rather serious about their statement that Studio 2002 is for Framework 1.0 and Studio 2003 is for framework 1.1. What still is unkown is why my development server still works even though Framework 1.1 is also installed :( Can't win 'em all. I'm going to uninstall 1.1 from development and see what happens but I guess this thread is finished. Thanks for listening to me vent. {sigh}

Database Connection String here is what I'm using I can show you what I'm using successfully with MS SQL Server...but you should note that my SQL server is on a different host...so i imagine a difference for you in the Data Source name...you should be able to use localhost? Anyway here is what I have: 'This is the string used to connect to the database for this application Public Const DbConnStr = "Data Source=caaserver;" & _ "Initial Catalog=DEVCAAapplication;User ID=application;Password=apassword" . . . 'The call to connect 'Get Database connection Dim conn As SqlConnection Dim appLog As New ApplicationLog() Try conn = New SqlConnection(New ApplicationCfg().DbConnStr) Catch exc As Exception ApplicationLog.logError(ApplicationCfg.AppLogSrcStr, "Failure creating SQL Connection on AppointmentCollection DeleteOlderThan:" _ & exc.Message) success = False End Try ============================== There are parts that won't mean much to you but heres the string explained so you can compare it to yours: Data Source - I have the DNS name for the Windows2000 server Initial Catalog - the Database with the tables that is on that SQL Server implementation UserId - the SQL login (configured in MS SQL Server) Password - the SQL login's password (configured in MS SQL Server) Please also note that you need to have permissions set for SQLlogin id to be able to access the database, its tables and any stored procs you may have used (but that would be a different error than you are getting now). Sorry but the best I can do is show you what is working for me. I have lots to learn yet. :) Good luck,

Sorry to be posting my life (well...bugs life) story here. I hope it helps someone with a similar problem. I found something on the self support section of Mircrosoft site under developer|.NET Framework http://msdn.microsoft.com/netframework/default.aspx?pull=/library/en-us/dnnetdep/html/sidexsidenet.asp It states this: Terminology A 1.0 application is an application that targets version 1.0 of the .NET Framework. All applications built with Visual Studio .NET 2002 are 1.0 applications. A 1.1 application is an application that targets version 1.1 of the .NET Framework. All applications built with Visual Studio .NET 2003 are 1.1 applications. =========================================== I don't know yet what this means but I think it points out something I forgot to mention with my problem...I'm developing in Visual Studio ..NET 2002 Enterprise Architect...and if I'm reading the above correctly then it requires Framework 1.0 or to expect some incompatibilities with 1.1. So I noticed on my development server there is actuall a directory for the Framework 1.0 AND for the Framework 1.1. So I'm going to try uninstalling the 1.1 on the problem server...then installing 1.0...then installing 1.1 again...to simulate what I have on the development server. I'll let you know what happens. I'm still going to submit this to Microsoft if I find a place where I can for free. Thanks again.

Even More: Page Source Differences (javascript) I've been using the Browser to view the "html source" of the same page on the two different servers. The page I'm viewing is a submit form with "Required Field Validators" for three textboxes. There is one difference (aside from the encrpyted piece holding control information at the top of the form) and it is with the Javascript function near the end of the page source. The source from the web server where validation works: ============================================== var Page_ValidationActive = false; if (typeof(clientInformation) != "undefined" && clientInformation.appName.indexOf("Explorer") != -1) { if (typeof(Page_ValidationVer) == "undefined") alert("Unable to find script library '/aspnet_client/system_web/1_1_4322/WebUIValidation.js'. Try placing this file manually, or reinstall by running 'aspnet_regiis -c'."); else if (Page_ValidationVer != "125") alert("This page uses an incorrect version of WebUIValidation.js. The page expects version 125. The script library is " + Page_ValidationVer + "."); else ValidatorOnLoad(); } function ValidatorOnSubmit() { if (Page_ValidationActive) { ValidatorCommonOnSubmit(); } ============================================== The source from the web server where validation does not work: ============================================== var Page_ValidationActive = false; if (typeof(clientInformation) != "undefined" && clientInformation.appName.indexOf("Explorer") != -1) { if ((typeof(Page_ValidationVer) != "undefined") && (Page_ValidationVer == "125")) ValidatorOnLoad(); } function ValidatorOnSubmit() { if (Page_ValidationActive) { ValidatorCommonOnSubmit(); } } ============================================== You can see that the successful one uses different code...seems to check for version of validation script library...but what ever it does...the code generated on one server is different than the other despite both having same version of .NET Framework. So the development environment has some differences from the production...and that is frustrating. I think I need to try and knock on the gates of Mircrosoft and see if they care about one lowly relatively inexperienced .NET developer with a potential bug? I'll let you know what I find. :)

Field Validation problems: Further things tried Just wanted to keep you updated on some of the things I've tried to fix this problem: 1) Uninstalled the Visual Studio .NET Architect components that I had on the production server ...to support my earlier plan of developing from that server (Turns out that was way too many difficulties and errors to make happen...so I just treat it like a production server and just copy the complete code to the developement directory and just aspx and binaries plus a few others to the test and live directories) 2) Uninstalled the .NET Framework ...and downloaded the framework 1.1 again and installed it. The difference in size (Under Control Panel | Add/Remove programs) still shows larger on the development server and the versions are identical. I'm assuming that Visual Studio .NET is responsible for the additional files. That also happens to be the server that "Required Field Validation" controls work on. :( I'm still trying to find other possible reasons/solutions but I'm quickly running out of things I can do. Does anyone have any suggestions (no matter how far fetched). The workaround is rewriting a LOT of coded pages for how they process field validation. :( Getting desperate! Thanks, Tom

Problem: Validation is not stoping me from entering blank fields on another server...while the same code on my laptop works correctly. Description: The page has two text boxes and a dropdown listbox. The textboxes each have a "Required Field" validation control assigned to them. There is a validationSummary control which displays the actual messages. On my laptop, I can enter nothing in the textboxes, click save...and I'll get the error messages stating the required fields. I copy the ENTIRE code directory (from project up including .aspx, .vb, \bin, etc) just to make sure I'm working with the same stuff...and for some reason doing the same thing on the server...allows the Item to be saved with blank fields. Environment: In my environement I am developing from my laptop and implementing on a company web server. On that server I have a "live", "test" and "dev" environment. Dev is a complete copy of the code...the other two are just the binaries and the ASPX pages (and a few other runtime files) The .NET Framework on each server is Version 1.1.4322 (but strangely enough...under Add/Remove programs they show up as different sizes 38.8MB on the server and 84.5 on laptop...however the laptop has Studio .NET installed so maybe that causes the difference) I'm really hoping this is one of those "uh...duh" things...and there is an obvious solution. :) I need to get this into testing and soon after that into production... Thanks, Tom