August 13, 2008 at 3:00 pm
Hi
When I try to create a new Transactional Publication with Updatable Subscriptions I get this error message when it should create the Publication.
TITLE: New Publication Wizard
------------------------------
SQL Server could not create publication 'MyDatabaseName'.
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
The specified '@notify_level_email' is invalid (valid values are: 1, 2, 3).
Object 'MyDatabaseName' does not exist or is not a valid object for this operation.
Changed database context to 'MyDatabaseName'.
Job 'S175B014SQLPRD2-MyDatabaseName-14' started successfully.
Warning: The logreader agent job has been implicitly created and will run under the SQL Server Agent Service Account. (Microsoft SQL Server, Error: 14266)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3054&EvtSrc=MSSQLServer&EvtID=14266&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
August 19, 2008 at 11:02 am
And your question is? What does the error message mean? Where do you specify the setting in question? Is this a problem?
As a general rule, receiving any error messages are not good. It looks like you need to give us some more detail about your 'updatable' subscription - do you get this error message on creating the publication? Are you trying to use sql server's email utilities? Is there a radio button you selected as a 'default' but didn't understand? Help us out here.
I.W Coetzer (8/13/2008)
HiWhen I try to create a new Transactional Publication with Updatable Subscriptions I get this error message when it should create the Publication.
TITLE: New Publication Wizard
------------------------------
SQL Server could not create publication 'MyDatabaseName'.
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
The specified '@notify_level_email' is invalid (valid values are: 1, 2, 3).
Object 'MyDatabaseName' does not exist or is not a valid object for this operation.
Changed database context to 'MyDatabaseName'.
Job 'S175B014SQLPRD2-MyDatabaseName-14' started successfully.
Warning: The logreader agent job has been implicitly created and will run under the SQL Server Agent Service Account. (Microsoft SQL Server, Error: 14266)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3054&EvtSrc=MSSQLServer&EvtID=14266&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
August 19, 2008 at 11:43 am
😉
Hi, we have used (documented) the same steps for creating publications for 5 databases and it has always worked, but now i cannot even create a publication for a new dummy database which I created today so it seems that I cannot create a publication anymore on the sql 2005 server full stop.
And by not being able to create a publication (which results in the error message above) I cannot set up the subscription so it is something to do with the sql 2005 server instance.
I have tried it on our development sql 2005 server and it still works there.
funny thing though is that on the server with the problem there is two publications that were created a while ago and they are still working and talking to the remote sql server 2005 instances.
Bye
August 19, 2008 at 11:50 am
It's good to have different platforms to allow comparisons. Are both your production/QA and development machines on the same version of SQL Server? Were there any variations in what you entered as you created the replication? Do you have the appropriate email utilities on both environments (since the error message addressed email specifically, I ask this question). Unfortunately, I have no live experience with this variation on transactional replication, so I have no intuition to draw on.
August 19, 2008 at 12:28 pm
Hi
yes, same version, same steps (we have them documented).
I'm really lost with this problem.
I have managed to get microsoft to also look into this problem, they contacted me and I had to forward answers to a long list of questions from them, according to them it looks as though the old replication was not properly deleted, but why then does a new dummy database throw the same exception when one tries to create a publication therefore.
August 19, 2008 at 12:56 pm
IF you are not meticulous about changing the names each time, at every possible location where you can change database names, then you expose and 'dirty' maintenance that the SQL Server Wizards may provide. ANY residual content from removing a replication may cause problems for you, especially if you don't follow a specific order or skip a step. There are so many subtle pieces involved in replication that it's easy to miss something, that then hangs around and gets in your way. In a testing environment, I've had to wipe the slate completely clean, uninstall and reinstall SQL Server in order to get replication to operate as I want. In a non-test environment, you don't have that luxury. So debris will lie around, waiting to get in your way.
August 19, 2008 at 3:04 pm
But that is what I also basically tried on the production server.
I created a new database with a name that has never been used for a database on that server added a table gave it a primary key (otherwise one can't select it as an article for replication) and then tried to create the publication but alas it failed as well at the last step with that same error message ... :crying:
August 21, 2008 at 7:43 am
Sorted it out, we had to change the way our operator is set up - to which emails are sent when jobs fail. The email addresses that we specified where not in the something@something.com format.
August 21, 2008 at 1:28 pm
Congratulations! I'm about to embark on setting up email notifications / alerts when processes fail, for the first time. We'll see how it goes.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply