I'm getting an "Invalid object name 'infocaster301'" server error
When I try to "Save & Publish" a page name change in the content tree, I get the following error after installing the package. It appears that it does save it but is just unable to publish the change.
Server Error in '/' Application. Invalid object name 'infocaster301'. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Invalid object name 'infocaster301'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Seems like the SQL Table for the 301 URL Tracker has not been created with the installation. Can you provide me with more information about your set-up? (like OS, SQL version, .NET version, Umbraco version, shared hosting?)
BTW, for now you can fix it yourself by running the following query:
CREATE TABLE infocaster301( NodeID int NOT NULL, OldUrl nvarchar(400) NOT NULL, IsCustom bit NOT NULL, Message nvarchar(400) NULL, Inserted datetime NOT NULL, CONSTRAINT PK_infocaster301 PRIMARY KEY CLUSTERED ( NodeID ASC, OldUrl ASC ) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY]
ALTER TABLE infocaster301 ADD CONSTRAINT DF_infocaster301_Custom DEFAULT ((0)) FOR IsCustom ALTER TABLE infocaster301 ADD CONSTRAINT DF_infocaster301_Inserted DEFAULT (getdate()) FOR Inserted
Thanks for the update. Just one question regarding the SQL Server 2000 installation, would there be any issues with the installed package if we upgrade the server to SQL 2008 at a later date?
I created the table and then created a script with Sql 2008 to generate the table. So to find out what was wrong with Sql 2000, I generated the script again but for Sql 2000 and there was one difference; on the primary key definition.
I just removed some Sql crap (maybe I could remove it from the main package, so there's one package for all Sql versions):
2008: ) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
2000: ) ON [PRIMARY]
If I'd use the 2000 syntax for all Sql versions, I don't think anything will break... But to be sure I made two versions. I will look into this tomorrow and decide if I'm going to supply only the 2000 version (compatible with 2005 and 2008) or still two different versions.
Btw, you didn't mention if it's working now... So, does it? :-D
I'm getting an "Invalid object name 'infocaster301'" server error
When I try to "Save & Publish" a page name change in the content tree, I get the following error after installing the package. It appears that it does save it but is just unable to publish the change.
Seems like the SQL Table for the 301 URL Tracker has not been created with the installation. Can you provide me with more information about your set-up? (like OS, SQL version, .NET version, Umbraco version, shared hosting?)
BTW, for now you can fix it yourself by running the following query:
Aight, that didn't go very well, next attempt:
We are using:
Tried implementing the table above but Sql 2000 reports a syntax error
So that's what went wrong, looks like Sql 2000 doesn't support something in the query.
Do you have any more detailed information about the syntax error?
I think I found what caused the SQL Server 2000 problems.
I added a new package, especially for SQL Server 2000: http://our.umbraco.org/FileDownload?id=835
Please mark this as answer if it solves your problems :-)
Thanks for the update. Just one question regarding the SQL Server 2000 installation, would there be any issues with the installed package if we upgrade the server to SQL 2008 at a later date?
Nope, there won't be any issues...
I created the table and then created a script with Sql 2008 to generate the table.
So to find out what was wrong with Sql 2000, I generated the script again but for Sql 2000 and there was one difference; on the primary key definition.
I just removed some Sql crap (maybe I could remove it from the main package, so there's one package for all Sql versions):
2008:
) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
2000:
) ON [PRIMARY]
If I'd use the 2000 syntax for all Sql versions, I don't think anything will break... But to be sure I made two versions. I will look into this tomorrow and decide if I'm going to supply only the 2000 version (compatible with 2005 and 2008) or still two different versions.
Btw, you didn't mention if it's working now... So, does it? :-D
Yeah - the update for SQL 2000 works perfectly. Awesome work - been wanting something like this for ages...
I had the same problem when installing on SQL Azure.
I used the statement above, but without the "ON [PRIMARY]" since that's not allowed on Azure.
My question is, (since this is a 2010 thread) did the data model change with the 1.5.2 version?
Hmm, apart from the IsRegex bit.
I found that out myself. ;)
Yep if you are trying to get 301 Url Tracker package running on SQL Azure then you will need to run this script:
To run a query you can use the in Browser manager which should be available in the Dashboard as a link, pretty clever.
Would be nice to add this to the package itself if it could sniff it out some how? ;)
Pete
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.