MSSql Error 1088 - Cannot find the object "tuition_account_info" because it does not exist or you do not have permissions

Following error is a simple and most easily seen error in transaction replication. The solution is also very simple. Read following blog to solve this in minutes.

MSSql Error 1088 - Cannot find the object "tuition_account_info" because it does not exist or you do not have permissions
Command attempted:
if @@trancount > 0 rollback tran
(Transaction sequence number: 0x00025E0E00011BE2000100000000, Command ID: 1)

Let's Understand: The problem is that the object doesn't reside at the subscriber. The object is either deleted or was never created. There are two ways to resolve the problem:

1. Either uncheck the object name from the replication object list.
2. Or create the object in the subscriber with similer schema in publisher.



Regards,
Online Powershell and SQL Classes @ http://tuitionaffordable.webstarts.com

Comments

Post a Comment

Popular posts from this blog

MSSQL Interview Question Clustering- Part2

Will Indian Rupee Cross 55?? Q: What will happen if you try to start the SQL service on the passive node? Ans: This will start because error log, mdf and ldf files are possessed by active node. Q: How exactly the SQL service starts on any node? Ans: Below is the list of all the steps in error log at the of SQL Service starting on one node, all the logs are self-explanatory- 1-SQLServerAgent service successfully stopped. 2-[sqsrvres] OnlineThread: asked to terminate while waiting for QP. 3-17148 :SQL Server is terminating due to 'stop' request from Service Control Manager. 4-17104 :Server Process ID is 9344. 5-This instance of SQL Server last reported using a process id of 6804 at 1/23/2011 10:39:34 AM (local) 1/23/2011 6:39:34 PM (UTC). 6-SQL Server is starting at priority class 'normal'(16 CPUs detected). 7-SQL Server configured for thread mode processing. 8-17125 :Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Block...
Read more

Handle Sexual Harassment

Image
Sexual harassment at work place is prevalent. It can be termed as bullying, unwelcome sexual advances and asking sexual favors at workplace. Harassment can happen to anyone and probability of recurrence increases if not tackled professionally. This is often observed that we don't talk enough on this topic. Some EEOC stats as per  link 79% of victims are women, 21% are men. 51% are harassed by a supervisor. Business, trade, banking, and finance are the biggest industries where sexual harassment occurs. 12% received threats of termination if they did not comply with their requests.  How to handle the sexual harassment- This needs to be documented. Victim should send out a mail to the offender informing that she/he is shocked with his/her actions on date at particular venue. I discussed this situaltion with my relatives and they asked me to inform you about my feelings. The victim has to be very professional. Victim needs to make sure that he seek for the read...
Read more

Error 1067: The cluster service is stopped on passive node of my two node sql cluster. It throws following error when I try to start this:

This is found that the cluster service in one of the passive stops. This throws following error when I try to start this. Error 1067: The process terminated unexpectedly I verified the password under which this cluster service is running. This account is perfect. So there should be some other problem. Let's go ahead and see the problem in the cluster.log file. Info from %WINDIR%\Cluster\cluster.log is as follows: WARN [EVT] EvtBroadcaster: EvPropEvents for node 2 failed. status 1727 WARN [NM] RpcExtErrorInfo: Error info not found. Error from clusterlog Error: Failed to read  (sector 12), error 170. and Failed to write  (sector 12), error 170. 1. started from cmd. net start clussvc 2. The Windows Firewall/Internet Connection Sharing service should neither be enabled nor set to start automatically. FmGetQuorumResource failed, error 170. Failed to read. Failed to form cluster, status 5086. Follwoing was the problem: The Admin NIC threw an error. This caused the neto...
Read more