StrataFrame Forum » StrataFrame Database Deployment Toolkit » Issues » Error when deploy localization tables

Error when deploy localization tables

Chan — Wed, 05 Nov 2008 10:16:19 GMT

Hi,

I hit error as attached when I try to deploy localization tables and data to server.

Please advice Thank you

RE: Error when deploy localization tables

Dustin Taylor — Wed, 05 Nov 2008 10:16:19 GMT

This can happen when importing the security tables. I've never seen it happen with localization or messaging tables, but either way, it's a simple fix:

1) Edit each of your imported tables (I'd start with the security tables if you have them in your app as they are the most likely culprits)

2) Ensure that any automatically created Stored Procedures actually have Sproc Names for them (if not, uncheck and recheck the box to regenerate the name)

3) Save the table

Do that for each of the security tables and see if it resolves your problem. If not, try the same thing with the localization and messaging tables.

RE: Error when deploy localization tables

Keith Chisarik — Mon, 03 Nov 2008 22:34:04 GMT

I have this exact same error where blank auto-generated SP's are created. I ran across it last week and ran across this post while searching for a solution.

I have never seen this before, this is also the first project that I have used messaging/localization.

Screen shot attached.

RE: Error when deploy localization tables

Chan — Mon, 03 Nov 2008 19:34:03 GMT

Hi,
I tried to workaround to create localization table in local machine. However, I hit another error. It complaint stored procedure name is empty.

I checked DDT, it contains two SP which is auto-generated (by import localization tables). However, it shows [dbo].[].
When I tried to check it from Table Properties, the InsertProcedure column show some name.

Any ideas?
Thank you

RE: Error when deploy localization tables

Ivan George Borges — Mon, 03 Nov 2008 05:22:29 GMT

Hi Chan.

This is from MSDN forum:

[quote]

I should have followed this up ages ago but here is our experience. As per the knowledgebase article I linked to:

This problem occurs because the TCP Chimney Offload feature is enabled on the server. The TCP Chimney Offload feature is enabled by the Windows Server 2003 Scalable Networking Pack.

This article also mentions that the TCP Chimney Offload feature is also enabled by installing SP2 for Windows 2003. In our case these errors stoppped as soon as we disabled this feature on the client machines. I'm not sure if it is neccessary to also do this on the SQL server as it was already disabled for us.

Hope this helps.

[/quote]

http://forums.microsoft.com/msdn/showpost.aspx?postid=134053&siteid=1&sb=0&d=1&at=7&ft=11&tf=0&pageid=4