Tuesday, November 6, 2007
MOSS 2007: Event ID: 2424 - The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.
Friday, October 26, 2007
So I did a bit of searching across the net and didn't have problems finding information on it in terms of people talking about it. It seems to be a problem quite a few users were facing. And what makes it even harder to diagnose is that there are multiple reasons for this error. If MOSS 2007 is installed on a DC for example, then a different fix will need to be applied. For my situation that fix did not apply because I have two-machine setup so far. One being the web front end and the other being the SQL database.
To cut a long story short, I did a repair on the MOSS 2007 web front end because I was out of options as the time it was down. So I tried many things, repair being one of them. Now apparently if you do a repair, it seems to only try and fix any damaged or corrupted files but does nothing to the registry (I'm assuming). I had to run the configuration wizard in order to fix the error for "The trial period for this product has expired". The configuration wizard basically updated the registry and all settings that seemed to have been lost during the repair. So while I am still unsure of exactly what caused it, this is my guess.
So, if you encounter this error AFTER a repair of MOSS 2007, remember to run the configuration wizard right away with all the default settings.
Friday, October 12, 2007
To enable this function you will need to add some new values to the Registry. As always before working on the Registry make a quick backup just in case. Never hurts.
Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
- Add/Change new string value to "Default User Name" and set it to the desired username
- Add/Change new string value to "DefaultPassword" and set it to the password of the desired username
- Add/Change new string value to "DefaultDomainName" and set it to the domain that the username resides in
- Change the string value of "AutoAdminLogon" to "1" for enable automatical logon or "0" to disable it
- For Windows 2000, "ForceAutoLogon" must be enabled to stop settings from being reset after reboot.
- Password is viewable by anyone who has access to the Registry
- Bypass auto login by holding down SHIFT during logon process
- Automatic logon will not function properly if "DontDisplayLastUserName" is enabled
Wednesday, September 19, 2007
Here's a nice link that talks on some points when choosing what kind of firewall to get.
Sunday, September 16, 2007
Monday, September 10, 2007
Now I have MS SQL Server 2005 as my backend database. I created a simple type with a couple fields, one being of type "bit", which can hold the values of 1, 0, or null. Since there isn't any boolean type, then this is what should be used for true and false data.
Now, I am programming in ASP.NET which communicates with the database. I was trying to do a simple INSERT command into this table and for awhile I couldn't figure out why it wasn't writing into it.
For example my SQL statement in ASP.NET could be like this:
Ex1. INSERT table1 (x1, x2, y1, y2) VALUES ('hello', 'there', True, False);
Or say I have a couple radio buttons R1 and R2 somewhere:
Ex2. INSERT table1 (x1, x2, y1, y2) VALUES ('good', 'bye', R1.Checked, R2.Checked);
In SQL Server: x1 and x2 are nchar(10), y1 and y2 are bit
Both statements did not work. If I actual values like 1 or 0, those will work.
Ex3. INSERT table1 (x1, x2, y1, y2) VALUES ('good', 'bye', 1, 0);
The only way to get Ex1 and Ex2 to work is to put bound the True or False by single quotes like a string.
Ex4. INSERT table1 (x1, x2, y1, y2) VALUES ('hello', 'there', 'True', 'False');
To me that is very confusing. But that's how SQL Server takes it.
1. Make a new table.
[Rows = 1, Columns = 1, Width = 100%, Cell Padding = 0, Cell Spacing = 0, Border = 0]
2. Check inside the table and set: Horizontal align to "center", Verticle align to "middle"
3. Now make another table of any size inside the one you just made and it will always be centered.
Saturday, September 8, 2007
The problem I was having was trying to connect to MS SQL Server 2005 using ASP.NET. This did not work as I was getting HTTP Error Code 403. This pretty much means that you lack the permission to access whatever you are trying to access. In this case, I had created an .aspx file that will access SQL Server.
So after fiddling around for like an hour I tried accessing .aspx files in IIS first. Sure enough, I got an error. This time a bit more specific. HTTP Error 403.1 - Forbidden: Execute access is denied. After another hour of searching for an answer as to why my asp.net pages won't display, I finally found the answer, which made me feel really stupid.
In anycase, ASP.NET pages are a scripting language, they run code in the background that "talks" to the backend servers. Now, by default, all websites created in IIS having the scripting permissions taken off for security purposes. Well, that's the problem right there. Turn this option on and you are set.
Go to "Properties" of the website in question, click on the "Home Directory" tab, and change the option "Execute permissions" to "Scripts only" or "Scripts and Executables".
What a waste of time! Definitely feel dumb today.
Monday, September 3, 2007
The obvious way would be to install another DC so that it can be up while the other is down. But for this situation, another computer is out of the question. So the best way to do this is to completely remove the hard drive and put in a brand new one and install a fresh new version of the OS. After the OS has been installed and updated, perform a dcpromo and make all settings exactly the same as the old DC.
For nested SWF files, it goes as follows:
1. First SWF (level 0) loads another SWF file into a different level using either loadMovie or loadMovieClip function.
2. The loaded SWF file can then refer to the first SWF by referring to it through "_level0"
For nested movie clips, _root, _parent, this, "instance name of movie clip" can all be used.
_root refers to main timeline
_parent refers to the calling movie clip
Friday, August 31, 2007
Recently I have been trying to figure out a way to detect on a network when certain devices are actively connected to the network. Reason for this is when users need to know when a certain devices is sending and receiving data (especially when we are talking about mission-critical devices - such as metal detection, programmable ovens, etc). Nothing is worse when a user "thinks" that the device is sending data only to find out that it didn't and must redo the entire job again. This not only wastes time, but obviously wastes money.
All this is assuming that the device being used has an internal ethernet adapter or is using wireless.
FREEping is a free software that pings any IP and keeps track of it through time. By pinging a certain device at regular intervals you will know whether or not the device is connected or not. Users can simply view the monitor and know right away. I'm sure there is other ping software out there, but this one does the job well enough.
Another solution which is better is to have some sort of LED light on the outside of the device indicating the connection is good, but of course this usually has to be custom implemented if it wasn't already built-in to the device to begin with, which equals more money. But is a better indicator.
Either way, both solutions work fine and I can finally get this little issue out of the way.
Thursday, August 2, 2007
I can say that from my experience it varies a lot, but there are general guidelines to follow. Most of the IT community (from talking with individuals in the field and through sources on the Internet) agree that the server room should not exceed roughly around 28 degrees Celsius in general. I think that's way too high in my opinion, 28 degrees in a room is pretty warm!
I've had the server room hit 26-27 degrees before and to me it was really warm. APC wrote a white paper to give their general guidelines (http://www.apcmedia.com/salestools/VAVR-5UDSLG_R2_EN.pdf). They say around 22-24 degrees Celsius is adequate with about 35%-50% humidity. Sun Microsystems in a articles (which I cannot find anymore) suggested around 21-23 degree Celsius for temperature.
From what I've read and heard so far and my own opinion on the matter, "normal" server rooms should have temperature of about 19-23 degrees Celsius and about 30%-50% humidity.
Minimum temperature I would say don't go below 16 degrees Celsius and for maximum temperature don't go above 25 degrees Celsius.
Server rooms should always be "cool" and "dry", but not "too cold" or "too dry". Anyway, that's my thoughts on that.
Wednesday, July 25, 2007
Take a look at the site:
Check out "The Possibilities", that's amazing!
Tuesday, July 24, 2007
Many people may overlook this very important folder. By default, Windows 2003 Server gives "authenticated users" full control of this folder. Patches will automatically adjust the security settings to accommodate for it, but you can easily do it yourself after installation of a new 2003 server machine.
The System Volume (Sysvol) is a shared directory that stores the server copy of the domain's public files that must be shared for common access and replication throughout a domain. The Sysvol folder on a domain controller contains the following items:
- Net Logon shares. These typically host logon scripts and policy objects for network client computers.
- User logon scripts for domains where the administrator uses Active Directory Users and Computers.
- Windows Group Policy.
- File replication service (FRS) staging folder and files that must be available and synchronized between domain controllers.
- File system junctions.
Best Practices for Sysvol Maintenance
Authenticated Users Group Has Too Many Permissions to the SYSVOL Network Share
Workstations check with Active Directory every 60 to 120 minutes to see if there are any new policies. If there are, then the workstations apply them - both user and machine policies.
If you are using group policies, local policy is always processed before site, domain, or OU group policies
Policies are reapplied every 90 minutes, with a 30-minute "randomization" to keep the domain controller from getting hit by many computers at once
Policies on DCs are refreshed every 5 minutes
Order in which policies are applied: local > site > domain > OU
If multiple GPOs attempt to set a setting to conflicting values, the GPO with the highest precedence sets the setting
GPO-links that are enforced cannot be blocked from the parent container
Managing inheritence of Group Policy:
Referenced from "Mastering Windows Server 2003" by Mark Minasi
Friday, July 13, 2007
The story, the characters, the music, all top notch. By far, the most emotional ending out there to date.
Dictionaries all over there world should change their definition of "patriotism" to:
Boss from Metal Gear Solid 3.
Thursday, July 12, 2007
I have to admit that this is not the same quality as back in E3 2005, but that's because Sony didn't want to say it really was pre-rendered. But now in E3 2007, they show a trailer with live in-game graphics. Quality might not be the same, but it still looks damn good. Definitely made me drool a bit.
For example, I can go into a colleagues site and view everything. Unless specific permissions were set up, it is all open.
The default security setting is "NT AUTHORITY/Authenicated Users".
So word of advice to anyone using My Site, you'll want to change your security settings right away.
When configuring SSO (Single Sign-On) for MOSS 2007, it is best to create a separate account to run this service.
Under Operations > Manage Settings for Single Sign-On > Manage Server Settings you put in all the accounts that will run this service. After all correct information is put in and you are sure all the accounts have been created and setup properly, clicking OK should finish it off. But nope, it keeps giving you an error message saying it cannot use the account or something along those lines. I can't remember exactly. But the key here is when you press OK, you can see the browser tries to connect to http://localhost/something/soemthing/
Unless you set http://localhost as one of your trusted sites in your Internet browser, it will keep giving you that message until you do.
Amazing, how no books or any material online could be found on this.
When configuring an account for SSO, it is best to you a security group when entering it in. This makes things much more flexible. Create an SSO admin account and make that account a member of the SSO Administrators for example.
Something that should only have taken a couple minutes, ended up taking me many hours. The frustration was just irritating. In any case, here is an example of an LDAP filter that works in MOSS 2007 that retrieves all the users in the "SharePoint Users" security group.
(&(objectCategory=Person)(objectClass=user)(memberOf=CN=SharePoint Users,OU=Information Technology,DC=
Get it all done before you roll it out. I used two sources that helped me out a bit on how to properly implement Kerberos into MOSS 2007.
Microsoft SharePoint: Building Office 2007 Solutions in C# 2005
Author: Scot Hillier
This was another annoying thing I didn't know how to get rid of. Had to do some digging and found a solution which Microsoft provides. This fix requires Visual Studio and the creation of a console application.
Use this when you can't get rid of a particular meeting in a Meeting Workspace. For example, you have 3 meetings in a meeting workspace, each with their own dates. There is no simple way to delete one meeting unless using this method. Hopefully this will be rectified some time later. For now, check out the link above for the how-to.
The following applies to MOSS 2007 as well. This error happened to me as well and made me crap in my pants for awhile as I was clueless as to what happened. After some time I was able to fix it.
When you use Microsoft Office SharePoint Portal Server 2003 (this applies to 2007 as well) on a computer that has an antivirus scan engine installed, you may experience the following symptoms:
When you browse through the Default.aspx page, you receive one of the following error codes:
When you try to open a file from a SharePoint document library, you receive the following error message:
- http://ServerName/Sites/Site/FileName contains the following virus: The Antivirus Scanner scan engine is offline. Please try to contact the scan engine later or contact your administrator.
Additionally, you may find messages that are related to the antivirus scan engine in the Windows SharePoint Services log file. The messages resemble the following:
- 0 08/16 00:09:25 6196 #96000a: infected by "The Symantec AntiVirus Scan Engine is offline. Please try to contact the scan engine later or contact your administrator. " - DOMAIN\USER - /sites/somesite/some document.doc
- 0 08/16 00:09:25 6196 #96000a: infected by "The Symantec AntiVirus Scan Engine is offline. Please try to contact the scan engine later or contact your administrator. " - DOMAIN\USER - /sites/somesite/default.aspx
Note: The Windows SharePoint Services log file is located in the following folder: %WINDIR%\TEMP
[SOLUTION] (with my changes):
- Use Query Analyzer to connect to the SharePoint content database.
- Run the following query to list all the files that are affected:
WHERE (VirusStatus > 0) AND (VirusStatus IS NOT NULL)
- Open your SQL Server Management Studio and go to the Content Database where the page giving you the error is located (WSS_Content database for example)
- Create a new query and run:
WHERE (VirusStatus > 0) and (VirusStatus is not null)
- If any records are displayed, these are the files that have been indicated by the Virus Scanner (ForeFront probably - Sigh... Microsoft, come on!) to be infected, thus it will not let you access the file. If you are certain that these files are Virus free (run a manual scan just in case) then run the following query:
SET VirusStatus = null
WHERE (VirusStatus > 0) and (VirusStatus is not null)
- You may also want to remove the VirusInfo as well since it usually contains a message saying the file has been infected or something all those lines (it's not important to remove, but I like to restore everything back to original state), run:
SET VirusInfo = null
WHERE (VirusInfo is not null)
- After this is done, you will be able to access the files again. You MAY have to reboot your MOSS server and SQL Server if it still does not work even though the status has been cleared.