One of my remote client was having this issue with her outlook. Outlook was working fine with the email one day ago and now it suddenly stopped working. After searching a little bit and Googling around I got the solution. First I would like to discuss the reason of this error, why this thing happen on outlook and suddenly outlook stop working.
Reason:
This thing mostly happen to people who use the exchange account in outlook and then delete the exchange account and configure the regular e-mail account in outlook. Outlook save the address book in the exchange format that is in name format and link it with the account. Many people on the internet suggested to repair the .PST file and few other things but none of them worked for me. What actually worked for is given below:
Close the outlook and find the .nk2 file under the user profile in windows XP (For windows vista please consult the windows tech net)
C:\Documents and Settings\username\Application Data\Microsoft\Outlook
Please replace the username with your actual name or browse to the above path, for that you have to show your hidden files and also the system protected hidden files (Show hidden Files In Windows XP)
Delete the .nk2 file
Outlook will create a new .nk2 file while opening next time.
You are done! enjoy the new account in outlook
Tags: outlook error, outlook error while sending, outlook unknown error, sending e-mail in outlook
Online storage is available on the internet and couple of services are very good but your have open a web browser locate the path to store the files and most of them are offering limited space.
Speedy Drive is giving another innovative idea to store a huge amount of data online for free and you don’t need to open any browser. You just install a simple client and there will be a drive mapped in your “My Computer”. You can specify any name during the installation of that client on your system.
Store your files online and access them from anywhere just like if they were saved on an USB device thanks to Speedy Drive. Map your Speedy Drive as a network disk (for example S:) on unlimited number of your computers.
Edit your documents, play music or even movies right away without downloading them. All your files will behave like if they were stored locally.
Speedy Drive enhances every single application on your computer by transparently connecting it to remote data. Open, play, edit, and save files directly from within your favorite programs.
With Speedy Drive, you can access your files from Finder and Explorer, no need to download and re-upload files back and forth.
Tags: free 4TB drive, free 4TB online space, free online space, free secure online space, free speedy drive
A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 – No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
If you are getting the above error while connecting with Microsoft SQL server 2005 installed on your system then you are at the right page. I got this error on a developer’s machine and after one hour research on the Google found the correct answer. The first reaction after any error is to check the Event log in windows. I got under given error in application log:
Could not connect because the maximum number of ’1′ user connections has already been reached. The system administrator can use sp_configure to increase the maximum value. The connection has been closed. [CLIENT: ]
After reading the above error anyone can understand the problem and there is also given the solution of this problem. How to solve the above problem, please follow the instruction given below:
-
Open Microsoft SQL Server Management Studio
-
Open a new query
-
Type the under given code and press the execute button
sp_configure ‘show advanced options’, 1;
go
reconfigure
go
sp_configure ‘user connections’, 0
go
reconfigure
go
The reason why you got this error is that the user connections was reset to 1, so only one user was able to connect with the SQL server.
Tags: could not connect because the maximum number has been reached, Microsoft SQL Server Error 233, no process is on the other end of the pipe, sql server error 233
Microsoft project server publish job 0% complete, expected wait time is zero seconds, if you are facing this error while publishing any project on Microsoft Project Server, the solution is given as under:
There is no need to search here and there and check for the new names and entering everything again and again. Just go straight to the administrator of your Microsoft project server and make sure that under given services are running successfully.
To restart these services please follow the steps given as under:
- Go to start menu and enter services.msc command
- Press enter, services panel will be opened
- Go to Microsoft Office Project Event Service and restart
- Go to Microsoft Office Project Server Queue Service and restart
Please share your valuable comments about this post.
Tags: error while publishing project, microsoft project server, ms project server, project server error
In SQL server we often interested in knowing that when last time a specific trigger on a table was updated .
It Requireid especially when a trigger is being update on regular bases or multiple users are allowed to update that trigger.Here comes the power of System tables in SQL SERVER to track such changes in DatAbase.
So we can write a smiple query on sys.triggers by providing trigger name to find out when it was updated like
SELECT modify_date FROM sys.triggers WHERE name LIKE ‘%TRIGGER_NAME%’
Tags: SQL Server, Triggers
USE Database_Name; (Replace the Database_Name with your actual database name)
GO
– Truncate the log by changing the database recovery model to SIMPLE.
ALTER DATABASE Database_Name
SET RECOVERY SIMPLE;
GO
– Shrink the truncated log file to 1 MB.
DBCC SHRINKFILE (Database_Name_log, 10000);
GO
– Reset the database recovery model.
ALTER DATABASE Database_Name
SET RECOVERY FULL;
GO
The Activity Monitor gives us a view of current connections on an instance. The monitor can be used to determine whether we have any processes blocking other processes. To open the Activity Monitor in Management Studio, right click on the Server in the Object Explorer, then select Activity Monitor.
1. Session ID: The unique number assigned to a process connected to SQL Server. This is also called a SPID. An icon next to the number represents what is happening in the connection. If you see an hourglass, you can quickly tell that the process is waiting on or is being blocked by another connection.
2. User Process Flag: Indicates whether processes that are internal SQL Server processes are connected. These processes are filtered out by default. You can change the value to see the SQL Server internal processes by clicking the drop down and selecting the appropriate value.
3. Login: The login to which the process is tied.
4. Database: The current database context for the connection.
5. Task State: Indicates whether the user is active or sleeping. (No, this doesn’t mean the user is active or sleeping at his or her keyboard; it means that SQL Server keeps the connection active even though no activity is coming from the login until the user disconnects.)
6. Done: Completed.
7. Pending: The process is waiting for a worker thread.
8. Runnable: The process has previously been active, has a connection, but has no work to do.
9. Running: The process is currently performing work.
10. Suspended: The process has work to do, but it has been stopped. Additional information about why the process is suspended may be found in the Wait Type column.
11. Command: Shows the type of command currently being executed. For example, you may see SELECT, DBCC, INSERT, or AWAITING COMMAND here, to name a few. This won’t show you the actual query that the user is executing, but it does highlight what type of activity is being run on your server. To see the actual command, select a row in this table, right click and choose Details.
12. Application: The application that is connecting to your instance. This can be set by the developer in the connection string.
13. Wait Time (ms): If the process is being blocked or waiting for another process to complete, this indicates how long the process has been waiting, in milliseconds; it will have a value of 0 if the process is not waiting.
14. Wait Type: Indicates the event you are waiting on.
15. Wait Resource: The text representation of the resource you are waiting on.
16. Blocked By: The Session ID (SPID) that is blocking this connection.
17. Head Blocker: A value of 1 means the Blocked By Session ID is the head of the blocking chain,otherwise 0.
18. Memory Use (KB): The current amount of memory used by this connection. Number of pages in the Procedure cache attributed to this connection. Note this was reported in pages in prior releases.
19. Host: The login’s workstation or server name. This is a really useful item, but in some cases you may have a Web server connecting to your SQL Server, which may make this less important.
20. Workload Group: The name of the Resource Governor workload group for this query.