Recently I had to do some work on a legacy application for a client and they were getting errors when trying to upload some files that I would consider to be of relatively small sizes of around 300kb. It turns out that IIS 6 is configured by default to a maximum upload size of 204,800 bytes (200kb) which is of little use these days. The fix I implemented required me to open the metabase.xml file located in c:\Windows\System32\Inetsrv and locate the setting AspMaxRequestEntityAllowed and amend the value to something more suitable. For good measure I then did an IIS reset and the problem went away.
May 7th, 2012
Solve Problem
Goto Control Panel -> Administrative Tools -> Event Viewer
Click Event Viewer
User IUSR_WEERACHAI error.
Open Component Services
Click DCOM Config
Right Click Microsoft Excel Application -> Properties
On tab Security Click Edit
Click Add
Click Advanced..
Add New user IUSR_Machine-name และ IWAM_Machine-name
Click OK
and Select All Allow
Click OK.
.
.
Example
asp_connect_excel.asp
- <%Option Explicit%>
- <html>
- <head>
- <title>ShotDev.Com Tutorial</title>
- </head>
- <body>
- <%
- Dim xlApp
- Set xlApp = Server.CreateObject(“Excel.Application”)
- If IsObject(xlApp) Then
- Response.write(“Connect to Excel.Application”)
- Else
- Response.write(“Cannot Connect to Excel.Application”)
- End IF
- %>
- </body>
- </html>
<%Option Explicit%>
<html>
<head>
<title>ShotDev.Com Tutorial</title>
</head>
<body>
<%
Dim xlApp
Set xlApp = Server.CreateObject("Excel.Application")
If IsObject(xlApp) Then
Response.write("Connect to Excel.Application")
Else
Response.write("Cannot Connect to Excel.Application")
End IF
%>
</body>
</html>
Create a asp file and save to path root-path/myasp/
Run
http://localhost/myasp/asp_connect_excel.asp
Screenshot
.
.
May 6th, 2012
I had issues uninstalling the 32 bit SQL 2005 Express and SQL 2005 Standard from a customers machine running Windows 2003 64bit. This was due to Systems Center Essentials requirement of having a 64 bit SQL when running on a 64 bit box with registry redirection.
The server ha two previous versions of the 32 bit reporting services (SQL and SQL Express)…and even after a complete uninstall, I could not reinstall SQL 2005 x64 bit and have function properly. I received errors after the 64 bit install on the Configuration Tools > Reporting Services Configuration (WMI Error 80040219). Also, when connecting to the reporting instance through SQL 2005 Management Studio (Could not complete operation, WinMgmt). When I tried to reinstall SQL using the default instance, I received an error that the default instance was installed, even when I removed everything (add/remove programs, SQL services, program files).
So, even after I thought I had removed all of the 32 bit SQL services on the machine, I kept having errors with 64 bit reporting services not being able to be configured. It was because the instance name still existed in the redirected 32 bit node of the registry (WOW6432node)
The quick fix to this problem was to delete the old 32 bit SQL configuration that was preventing the 64 bit version of reporting services from working from:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432node\Microsoft\Microsoft SQL Server
Note – That will destroy any 32 bit SQL running on your 64 bit box…please make sure the services are deleted as detailed below.
Uninstalling SQL 2005 Manually
First, here are the recommended steps to manually uninstall SQL 2005:
http://support.microsoft.com/kb/909967
If that doesn’t work, this is how you can manually uninstall all versions of SQL 2005 so that SQL can be reinstalled: .
Note – This method will delete all databases and configuration, you must have a backup of your existing SQL databases (which this uninstall will delete) before proceeding. (Again, this is not supported, please call Microsoft PSS for supported methods)
- Uninstall all SQL components possible in Add/Remove Programs (including the SQL client and VSS writer)
- Stop all SQL Services and configure them to disabled using Start > SQL Configuration Manager
- Delete the following registry to get rid of the services. If you have multiple instance installed, it will be Keyname$Instance (i.e. MSSQLServer$OFFICESERVERS)
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServer
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SQLServerAgent
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLServerADHelper
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ReportServer
- Verify that the services do not exist in the SQL Configuration Manager.
- Delete the SQL Configuration in the registry
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
- HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server
- Note – if you installed a 32 bit version of SQL on 64 bit version of Windows, you will need to also delete them from the 32 bit registry node that is redirected. More Info MS 896459.
* HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432node\Microsoft\MSSQLServer
* HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432node\Microsoft\Microsoft SQL Server
- Delete the SQL Program files – Note this will also delete the existing databases on the system that must be restored from backup.
- Delete the directory: C:\Program Files\Microsoft SQL Server
Note – if you installed a 32 bit version of SQL on 64 bit version of Windows, you will need to also delete them from the 32 bit program files:
C:\Program Files (x86)\Microsoft SQL Server - You might need to reboot to close all files before you can delete the directory.
- Delete the directory: C:\Program Files\Microsoft SQL Server
Now you can reinstall a clean 32 bit or 64 bit SQL without errors.
May 6th, 2012
First of all, you don’t need to create any websites but a default website that binds to all hostnames.
Create two server farms, one called Farm1 and the other called Farm2, and set them up as you please.
Now go to the IIS level settings and enter the URL Rewrite module settings. Create two new blank rules called “test.domain.com” and “test2.domain.com” – the naming is purely for your own sake, they have no practical effect.
Make sure they’re set to use wildcards and that the matching pattern is “*”. Now, the important thing is to add a “Condition” with an input of “{HTTP_HOST}” and set the pattern to “test.domain.com” for the first rule and “test2.domain.com” for the second rule accordingly. For each rule, make sure the action type is set to “Route to Server Farm” and that the matching server farm is chosen.
This will make sure the rules match any URLs and thanks to the condition we setup, only one rule will match each domain name and route it to the related server farm.
If you prefer the non-GUI way, here’s how to setup the rewrite rules in the C:\Windows\System32\inetsrv\config\applicationHost.config file:
<rewrite>
<globalRules>
<rule name=”test.domain.com” patternSyntax=”Wildcard” stopProcessing=”true”>
<match url=”*” />
<action type=”Rewrite” url=”http://Farm1/{R:0}” />
<conditions>
<add input=”{HTTP_HOST}” pattern=”test.domain.com” />
</conditions>
</rule>
<rule name=”test2.domain.com” patternSyntax=”Wildcard” stopProcessing=”true”>
<match url=”*” />
<action type=”Rewrite” url=”http://Farm2/{R:0}” />
<conditions>
<add input=”{HTTP_HOST}” pattern=”test2.domain.com” />
</conditions>
</rule>
</globalRules>
<rewriteMaps>
</rewriteMaps>
</rewrite>
<webFarms>
<webFarm name=”Farm1″ enabled=”true”>
<server address=”learn.iis.net” enabled=”true” />
</webFarm>
<webFarm name=”Farm2″ enabled=”true”>
<server address=”bing.com” enabled=”true” />
</webFarm>
<applicationRequestRouting>
<hostAffinityProviderList>
<add name=”Microsoft.Web.Arr.HostNameRoundRobin” />
<add name=”Microsoft.Web.Arr.HostNameMemory” />
</hostAffinityProviderList>
</applicationRequestRouting>
</webFarms>
In the above example I’ve setup Farm1 to proxy the learn.iis.net site and Farm2 to proxy bing.com. Thus if I setup test.domain.com and test2.domain.com to point to 127.0.0.1 using the hosts file and I then access the URL test.domain.com in my browser, I’ll basically browse learn.iis.net and likewise I’ll browse bing.com using test2.domain.com.
Below is step by step
Setting up the farms
Start by installing the Application Request Routing module if you haven’t done so already. Now create two sever farms called “News” and “Search”. Add the search & news websites to each of their server farms like so:
You may also setup the farms directly in applicationHost.config:
<webfarms> <webfarm enabled="true" name="News"> <server enabled="true" address="cnn.com"> <server enabled="true" address="foxnews.com"> <server enabled="true" address="english.aljazeera.net"> </server></server></server></webfarm> <webfarm enabled="true" name="Search"> <server enabled="true" address="google.com"> <server enabled="true" address="bing.com"> <server enabled="true" address="yahoo.com"> </server></server></server></webfarm> <applicationrequestrouting> <hostaffinityproviderlist> <add name="Microsoft.Web.Arr.HostNameRoundRobin"> <add name="Microsoft.Web.Arr.HostNameMemory"> </add></add></hostaffinityproviderlist> </applicationrequestrouting></webfarms> |
Setting up the rules
Go to the IIS level “URL Rewrite” settings page. If any default rules were created in the installation of IIS ARR, delete them now. Create a new rule from the blank template and call it “search.local”. Set the Match URL to use Wildcards and enter a pattern of “*”. This ensures that the rule matches and URL that we send to the server – no matter the hostname.
Expand the Conditions pane and add a new condition. Set the input to “{HTTP_HOST}” and type the pattern “search.local”. The {HTTP_HOST} condition ensures that this rule only matches requests to the search.local hostname.
Finally set the action type to “Route to Server Farm” and choose the Search server farm. Tick the “Stop processing of subsequent rules” as the request should be routed onto the server farm as soon as this rule matches.
As the last step, create a second identical rule except it should be named news.local and have an {HTTP_POST} condition matching the news.local hostname. Setting up the rewrite rules can also be done in applicaitonHOst.config directly:
<rewrite> <globalrules> <rule name="search.local" stopprocessing="true" patternsyntax="Wildcard"> <match url="*"> <action url="http://Search/{R:0}" type="Rewrite"> <conditions> <add pattern="search.local" input="{HTTP_HOST}"> </add></conditions> </action></match></rule> <rule name="news.local" stopprocessing="true" patternsyntax="Wildcard"> <match url="*"> <action url="http://News/{R:0}" type="Rewrite"> <conditions> <add pattern="news.local" input="{HTTP_HOST}"> </add></conditions> </action></match></rule> </globalrules></rewrite> |
Once done, your rules should look like this
Testing the farms
Create two host entries in your %windir%\System32\Drivers\etc\hosts file that makes news.local and search.local point to 127.0.0.1. Now when you open a browser and enter news.local or search.local, you should hit the search engines and news sites we setup earlier. By default IIS ARR will distribute the requests to the server with the least current requests – and since we’re the only ones hitting them we’ll basically always just hit the first server. To alleviate this you can change the load distribution mode to a weighted round robin with even distribution, that’ll ensure you hit the sites one by one in turn.
Note that this’ll only load CNN and Bing correctly as several of the other domains only listen to their configured domains (IIS ARR will proxy the reuqest onto the origin servers with a hostname request of search & news.local respectfully). I’ll follow up on how to fix that later on
April 19th, 2012
What does the new advanced firewall offer & how can it help you?
New with Windows Server 2008, the built-in firewall is now “advanced”. And it isn’t just me saying that, Microsoft now calls it the “Windows Firewall with Advanced Security” (let’s abbreviate that as WFAS).
Here are the new features that help justify that new name:
- New GUI interface – an MMC snap-in is now available to configure the advanced firewall.
- Bi-directional – filters outbound traffic as well as inbound traffic.
- Works better with IPSEC – now the firewall rules and IPSec encryption configurations are integrated into one interface.
- Advanced Rules configuration – you can create firewall rules (exceptions) for Windows Active Directory (AD) service accounts & groups, source/destination IP addresses, protocol numbers, source and destination TCP/UDP ports, ICMP, IPv6 traffic, and interfaces on the Windows Server.
With the addition of being a bi-directional firewall, a better GUI, and advanced rules configuration, the Windows Advanced firewall is bordering on being as good as traditional host-based firewalls (like ZoneAlarm Pro, for example).
I know that the first concern of any server admin in using a host-based firewall is: what if it prevents critical server infrastructure apps from functioning? While that is always a possibility with any security measure, WFAS will automatically configure new rules for any new server roles that are added to the server. However, if you run any non-Microsoft applications on your server that need inbound network connectivity, you will have to create a new rule for that type of traffic.
By using the advanced windows firewall, you can better secure your servers from attack, your servers from attacking others, and really nail down what traffic is going in and out of your servers. Let’s see how it is done.
What are the options for configuring Windows Firewall with Advanced Security?
Previously, with Windows Server, you could configure the Windows firewall when you went to configure your network adaptor or from the control panel. The configuration was very basic.
With Windows Firewall with Advanced Security (WFAS), most admins will configure the firewall either from Windows Server Manager or the MMC with only the WFAS snap-in. Here is what they both look like:
Figure 1: Windows 2008 Server Manager
Figure 2: Windows 2008 Firewall with Advanced Security MMC only
What I have found is that the quickest & easiest way to start the WFAS MMC is to just type firewall in the Start menu Search box, like this:
Figure 3: Windows 2008 Firewall with Advanced Security MMC only
There is also a new netsh advfirewall CLI option for configuring WFAS.
What can I configure using the new WFAS MMC Snap-in?
Because there are so many possible features you can configure with the new WFAS MMC snap-in, I can’t possibly cover them all. If you have ever seen the configuration GUI for Windows 2003 built-in firewall, you will quickly notice how many more options there appear to be with WFAS. However let me hit on a few of the most frequently used.
When you first go into the WFAS MMC snap in, by default, you will see that WFAS is ON and blocking inbound connections that don’t have a matching outbound rule. In addition, the new outbound firewall is turned off.
Something else you will notice is that there are also different profiles for WFAS (see Figure 4 below).
Figure 4: Profiles now available in Windows 2008 Firewall with Advanced Security
There is a domain profile, private profile, and public profile for WFAS. What these different profiles allow you to do is take the many inbound & outbound rules you may have and apply that group of firewall rules to your computer based on where your computer is connected to the network (say the corporate LAN vs. the local coffee shop).
Out of all the improvements we have talked about with WFAS, in my opinion, the most significant improvement is the more sophisticated firewall rules. Take a look at the Windows 2003 Server Firewall option to add an exception (a rule), in Figure 5.
Figure 5: Windows 2003 Server Firewall Exception window
Now, let’s compare that to Windows 2008 Server:
Figure 6: Windows 2008 Server Advanced Firewall Exception window
Notice how the Protocols and Ports tab is just a small part of the multi-tabbed window. You can also configure rules to apply to Users & Computers, Programs and Services, and IP address Scopes. With this type of sophisticated firewall rules configuration, Microsoft has pushed WFAS more toward Microsoft’s IAS server.
The number of default rules offered by WFAS is truly amazing. In Windows 2003 Server, there were the 3 default exceptions (rules). Not so in Windows Server. WFAS offers about 90 default inbound firewall rules and at least 40 default outbound rules – WOW!
Figure 7: Windows 2008 Server Advanced Firewall Default Inbound Rules
How to Create an Inbound Custom Firewall Rule
So how do you create a rule using the new Windows Advanced Firewall? Let’s step through it.
Say that you have installed Apache web server for Windows on your Windows 2008 Server. If you had used IIS, built-in with Windows, the port would have been automatically opened for you. However, as you are using a third party web server and you have the inbound firewall enabled, you must manually open the port.
Here are the steps to follow:
- Identify the protocol you want to filter – in our case, it is going to be TCP/IP (as opposed to UDP/IP or ICMP)
- Identify the source IP address, source port number, destination IP address, and destination port number – our web traffic will be coming from ANY IP address and any port number, going to this server, on port 80. (note that you could also create a rule for a certain program, such as the apache HTTP Server).
- Open the Windows Firewall with Advanced Security MMC
- Add the Rule – Click on the New Rule button in Windows Firewall with Advanced Security MMC to bring up the New Inbound Rule Wizard
Figure 8: Windows 2008 Server Advanced Firewall MMC – new rule button
- Select that you want to create a rule for a port
- Configure protocol & port number – take the default of TCP and enter the port number as 80 and click Next.
- Take the default of “allow this connection” & click Next.
- Take the default of applying this rule to all profiles & click Next.
- Give the rule a name and click Finish.
At this point, you should have a rule that looks like this:
Figure 9: Windows 2008 Server Advanced Firewall MMC – after rule was created
I tested that my newly installed Apache web server would not work when just installed with the firewall enabled. However, after the rule, it works great!
March 15th, 2012
How to generate a CSR in Microsoft IIS 7
- Click Start, then Administrative Tools, then Internet Information Services (IIS) Manager.
- Click on the server name.
- From the center menu, double-click the “Server Certificates” button in the “Security” section (it is near the bottom of the menu).
- Next, from the “Actions” menu (on the right), click on “Create Certificate Request.” This will open the Request Certificate wizard.
- In the “Distinguished Name Properties” window, enter the information as follows:
Common Name – The name through which the certificate will be accessed (usually the fully-qualified domain name, e.g., www.domain.com or mail.domain.com).
Organization – The legally registered name of your organization/company.
Organizational unit – The name of your department within the organization (frequently this entry will be listed as “IT,” “Web Security,” or is simply left blank).
City/locality – The city in which your organization is located.
State/province – The state in which your organization is located.
Country/region – If needed, you can find your two-digit country code in our list.
- Click Next.
- In the “Cryptographic Service Provider Properties” window, leave both settings at their defaults (Microsoft RSA SChannel and 2048) and then click next.
- Enter a filename for your CSR file.
Remember the filename that you choose and the location to which you save it. You will need to open this file as a text file and copy the entire body of it (including the Begin and End Certificate Request tags) into the online order process when prompted.
SSL Certificate Installation in IIS 7
Installation:
- Open the ZIP file containing your certificate. Save the file named your_domain_name.cer to the desktop of the web server you are securing.
- Click on Start, then Administrative Tools, then Internet Information Services (IIS) Manager.
- Click on the server name.
- From the center menu, double-click the “Server Certificates” button in the “Security” section (near the bottom of the menu).
- From the “Actions” menu (on the right), click on “Complete Certificate Request.” This will open the Complete Certificate Request wizard.
- Browse to your_domain_name.cer file that was provided to you by DigiCert. You will then be required to enter a friendly name. The friendly name is not part of the certificate itself, but is used by the server administrator to easily distinguish the certificate.
- Clicking “OK” will install the certificate to the server.
Note: There is a known issue in IIS 7 giving the following error: “Cannot find the certificate request associated with this certificate file. A certificate request must be completed on the computer where it was created.” You may also receive a message stating “ASN1 bad tag value met”. If this is the same server that you generated the CSR on then, in most cases, the certificate is actually installed. Simply cancel the dialog and press “F5″ to refresh the list of server certificates. If the new certificate is now in the list, you can continue with the next step. If it is not in the list, you will need to reissue your certificate using a new CSR (see our CSR creation instructions for IIS 7). After creating a new CSR, login to your DigiCert account and click the re-key button for your certificate.
- Once the SSL certificate has been successfully installed to the server, you will need to assign that certificate to the appropriate website using IIS.
- From the “Connections” menu in the main Internet Information Services (IIS) Manager window, select the name of the server to which the certificate was installed.
- Under “Sites,” select the site to be secured with SSL.
- From the “Actions” menu (on the right), click on “Bindings.” This will open the “Site Bindings” window.
- In the “Site Bindings” window, click “Add…” This will open the “Add Site Binding” window.
- Under “Type” choose https. The IP address should be the IP address of the site or All Unassigned, and the port over which traffic will be secured by SSL is usually 443. The “SSL Certificate” field should specify the certificate that was installed in step 7.
- Click “OK.”
- Your SSL certificate is now installed, and the website configured to accept secure connections.
February 8th, 2012
C.5.4.1. How to Reset the Root Password
If you have never set a root password for MySQL, the server does not require a password at all for connecting as root. However, this is insecure. For instructions on assigning passwords, see Section 2.18.2, “Securing the Initial MySQL Accounts”.
If you know the root password, but want to change it, see Section 12.7.1.6, “SET PASSWORD Syntax”.
If you set a root password previously, but have forgotten it, you can set a new password. The following sections provide instructions for Windows and Unix systems, as well as generic instructions that apply to any system.
On Windows, use the following procedure to reset the password for all MySQL root accounts:
- Log on to your system as Administrator.
- Stop the MySQL server if it is running. For a server that is running as a Windows service, go to the Services manager: From the Start menu, select Control Panel, then Administrative Tools, then Services. Find the MySQL service in the list and stop it.If your server is not running as a service, you may need to use the Task Manager to force it to stop.
- Create a text file containing the following statements. Replace the password with the password that you want to use.
UPDATE mysql.user SET Password=PASSWORD('MyNewPass') WHERE User='root'; FLUSH PRIVILEGES;Write the
UPDATEandFLUSHstatements each on a single line. TheUPDATEstatement resets the password for allrootaccounts, and theFLUSHstatement tells the server to reload the grant tables into memory so that it notices the password change. - Save the file. For this example, the file will be named
C:\mysql-init.txt. - Open a console window to get to the command prompt: From the Start menu, select Run, then enter cmd as the command to be run.
- Start the MySQL server with the special
--init-fileoption (notice that the backslash in the option value is doubled):C:\>
C:\mysql\bin\mysqld-nt --init-file=C:\\mysql-init.txtIf you installed MySQL to a location other than
C:\mysql, adjust the command accordingly.The server executes the contents of the file named by the
--init-fileoption at startup, changing eachrootaccount password.You can also add the
--consoleoption to the command if you want server output to appear in the console window rather than in a log file.If you installed MySQL using the MySQL Installation Wizard, you may need to specify a
--defaults-fileoption:C:\>
"C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt.exe"--defaults-file="C:\\Program Files\\MySQL\\MySQL Server 5.0\\my.ini"--init-file=C:\\mysql-init.txtThe appropriate
--defaults-filesetting can be found using the Services Manager: From the Start menu, select Control Panel, then Administrative Tools, then Services. Find the MySQL service in the list, right-click it, and choose thePropertiesoption. ThePath to executablefield contains the--defaults-filesetting. - After the server has started successfully, delete
C:\mysql-init.txt.
You should now be able to connect to the MySQL server as root using the new password. Stop the MySQL server, then restart it in normal mode again. If you run the server as a service, start it from the Windows Services window. If you start the server manually, use whatever command you normally use.
On Unix, use the following procedure to reset the password for all MySQL root accounts. The instructions assume that you will start the server so that it runs using the Unix login account that you normally use for running the server. For example, if you run the server using the mysql login account, you should log in as mysql before using the instructions. Alternatively, you can log in as root, but in this case you must start mysqld with the --user=mysql option. If you start the server as root without using --user=mysql, the server may create root-owned files in the data directory, such as log files, and these may cause permission-related problems for future server startups. If that happens, you will need to either change the ownership of the files to mysql or remove them.
- Log on to your system as the Unix user that the mysqld server runs as (for example,
mysql). - Locate the
.pidfile that contains the server’s process ID. The exact location and name of this file depend on your distribution, host name, and configuration. Common locations are/var/lib/mysql/,/var/run/mysqld/, and/usr/local/mysql/data/. Generally, the file name has an extension of.pidand begins with eithermysqldor your system’s host name.You can stop the MySQL server by sending a normalkill(notkill -9) to the mysqld process, using the path name of the.pidfile in the following command:shell>
kill `cat /mysql-data-directory/host_name.pid`Use backticks (not forward quotation marks) with the
catcommand. These cause the output ofcatto be substituted into thekillcommand. - Create a text file containing the following statements. Replace the password with the password that you want to use.
UPDATE mysql.user SET Password=PASSWORD('MyNewPass') WHERE User='root'; FLUSH PRIVILEGES;Write the
UPDATEandFLUSHstatements each on a single line. TheUPDATEstatement resets the password for allrootaccounts, and theFLUSHstatement tells the server to reload the grant tables into memory so that it notices the password change. - Save the file. For this example, the file will be named
/home/me/mysql-init. The file contains the password, so it should not be saved where it can be read by other users. If you are not logged in asmysql(the user the server runs as), make sure that the file has permissions that permitmysqlto read it. - Start the MySQL server with the special
--init-fileoption:shell>
mysqld_safe --init-file=/home/me/mysql-init &The server executes the contents of the file named by the
--init-fileoption at startup, changing eachrootaccount password. - After the server has started successfully, delete
/home/me/mysql-init.
You should now be able to connect to the MySQL server as root using the new password. Stop the server and restart it normally.
The preceding sections provide password-resetting instructions for Windows and Unix systems. Alternatively, on any platform, you can set the new password using the mysql client (but this approach is less secure):
- Stop mysqld and restart it with the
--skip-grant-tablesoption. This enables anyone to connect without a password and with all privileges. Because this is insecure, you might want to use--skip-grant-tablesin conjunction with--skip-networkingto prevent remote clients from connecting. - Connect to the mysqld server with this command:
shell>
mysql - Issue the following statements in the mysql client. Replace the password with the password that you want to use.
mysql>
UPDATE mysql.user SET Password=PASSWORD('MyNewPass')->WHERE User='root';mysql>FLUSH PRIVILEGES;The
FLUSHstatement tells the server to reload the grant tables into memory so that it notices the password change.
You should now be able to connect to the MySQL server as root using the new password. Stop the server, then restart it normally (without the --skip-grant-tables and --skip-networking options).
February 7th, 2012
this resolution works with:
- 64-bit Windows 7
- 64-bit MS Office
- Please reply to this thread if it worked for you so i can make this a full “compatibility list”
trying to connect to an Access database in visual studio but keep getting this error?
try installing this first: http://www.microsoft.com/download/en/details.aspx?id=13255
however if, like me, that doesnt work for you, try the following method:
NOTE: this DOES work for office 2010 even though it is for 2007 office, dont ask me why it just does 
1. download and install this: http://www.microsoft.com/download/en/confirmation.aspx?id=23734
2. in VS click add data source, follow the wizard and enjoy!
P.S thanks to everyone that helped me at my original thread: http://social.msdn.microsoft.com/Forums/en-US/csharpgeneral/thread/ebb05600-055a-44c4-8cd3-d33a79878b23
i did give up and tried storing to text files, but oh my god was that a bad choice! so i came back to trying to resolve this and managed to after HOURS AND HOURS of searching.
this thread is for all of those people being given a hard time connecting to Access databases!
February 3rd, 2012
notice use of undefined constant id – *******
For solve this error check below steps
Open PHP.ini file.
In this file search for the phrase “ error_reporting = E_ALL” ,[without inverted commas]
Here replace this with “error_reporting = E_ALL & ~E_NOTICE & ~E_WARNING “
Restart iis or apache tomcat server and check website
February 1st, 2012
installing ionCube PHP extension
The free ionCube PHP loader is required to install and run TestRail on your server. This extension decrypts the protected TestRail PHP files and optimizes their execution. See below to learn how to install ionCube on Windows and Unix/Linux systems.
Installing ionCube on Windows
You can download the ionCube loader for Windows here (you might need a different version if you didn’t install PHP via the Web Platform Installer):
After downloading and extracting the files on your server, copy the loader extension ioncube_loader_win_5.3.dll or ioncube_loader_win_5.2.dll to your PHP‘s ext directory (usually C:\Program Files (x86)\PHP\v5.3\ext or similar). Now activate the extension by adding the following line to your PHP.ini file (please adjust the directory accordingly and use two backslashes as directory separator). You must specify the full path to the file. You can find the PHP.ini file in your PHP installation directory (usually C:\Program Files (x86)\PHP\v5.3 or similar):
zend_extension="C:\\Program Files (x86)\\PHP\\v5.3\\ext\\ioncube_loader_win_5.3.dll"
You can verify that the ionCube loader extension has been successfully installed by running php -v in the Windows Command Prompt (you need to change to PHP‘s installation directory in order the execute this command).
The ionCube loader extension is successfully installed if php -v outputs something like this (note the ionCube PHP Loader line):
PHP 5.2.10 (cli) (built: Jun 17 2009 16:06:30)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies
with the ionCube PHP Loader v3.1.34, Copyright (c) 2002-2009, by ionCube Ltd.
Please note: In order for IIS to be able to load the extension, it might be needed to change the permission of the ionCube extension file. To do this, right-click the file in Explorer, Properties, select the Security tab and add the Users group.
To reload PHP, you now need to restart the IIS web server. The easiest way to do is to restart the World Wide Web Publishing Windows service. You can do this by opening the Services application from the Administrative Tools and restarting the service (please note that this restarts all IIS application pools and websites; if you are hosting other websites and applications on this server, you might want to restart the relevant application pool only).
Installing ionCube on Unix/Linux
You can download the relevant ionCube edition for your operating system from ionCube’s website. After downloading and extracting the files on your web server, place the files in a directory of your choice, for example /opt/ioncube.
To activate ionCube, add the relevant ionCube loader extension to your PHP.ini. To do this, make sure to use the zend_extension or zend_extension_ts configuration directives and specify the full path to the extension:
zend_extension=/opt/ioncube/ioncube_loader_lin_5.2.so
If you are using PHP 5.3 (you can verify the version by executing php -v), you would need to load the ionCube loader for PHP 5.3:
zend_extension=/opt/ioncube/ioncube_loader_lin_5.3.so
If you are unsure which ionCube extension you need to activate for your server system, please copy the loader-wizard.php script to your web server directory and access it from your web browser and follow the installation instructions. After installing the extensions, please restart your web server to load the newly installed extensions.
You can verify that the ionCube loader extension has been successfully installed by running php -v. Please note though that the PHP command line interface might use a different configuration file than the PHP version that is used by your web server. Please make sure that ionCube is activated in all relevant PHP.ini configuration files. The ionCube loader extension is successfully installed if php -v outputs something like this (note the ionCube PHP Loader line):
PHP 5.2.4-2ubuntu5.7 with Suhosin-Patch 0.9.6.2 (cli) (built: Aug 21 2009 19:52:39)
Copyright (c) 1997-2007 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies
with the ionCube PHP Loader v3.1.34, Copyright (c) 2002-2009, by ionCube Ltd.