Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Error Scripting DB Objects from My Computer

Author  Topic 

Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)

7020 Posts

Posted - 2005-03-14 : 16:45:54

When I attempt to script out a database object from any database server with Enterprise Manager, I get a message like this:
[SQL-DMO]CreateFile error on 'CORPSQL03.pubs.DP1'

If I change the scripting option from Unicode to ANSI, I get this:
[SQL-DMO]CreateFile error on 'CORPSQL03.pubs.DP2'

If I attempt to script the objects to a file, it creates the file, but it is empty.

I can script out these objects from any other computer, but it doesn't work on my computer. I am in the sysadmin role on all of these computers. The error happens whether I connect to the server with the SA password, or when I connect with my own account with integrated security.

I can script out jobs and operators from these servers, but I cannot script out stored procedures, tables, functions, or views.

I did a Google search and found a few postings about the same problem, but no one had a solution. Has anyone ever seem this problem, or know a solution?




CODO ERGO SUM

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2005-03-14 : 17:42:00
I would try reinstalling the SQL client tools as it sounds like something is messed up with tools. Then install sp3a on the client machine as the service packs aren't only for the database servers.

Tara
Go to Top of Page

Pskaarup
Starting Member

2 Posts

Posted - 2005-04-07 : 11:02:28
pskaarup
quote:
Originally posted by Michael Valentine Jones


When I attempt to script out a database object from any database server with Enterprise Manager, I get a message like this:
[SQL-DMO]CreateFile error on 'CORPSQL03.pubs.DP1'

If I change the scripting option from Unicode to ANSI, I get this:
[SQL-DMO]CreateFile error on 'CORPSQL03.pubs.DP2'

If I attempt to script the objects to a file, it creates the file, but it is empty.

I can script out these objects from any other computer, but it doesn't work on my computer. I am in the sysadmin role on all of these computers. The error happens whether I connect to the server with the SA password, or when I connect with my own account with integrated security.

I can script out jobs and operators from these servers, but I cannot script out stored procedures, tables, functions, or views.

I did a Google search and found a few postings about the same problem, but no one had a solution. Has anyone ever seem this problem, or know a solution?




CODO ERGO SUM

Go to Top of Page

Pskaarup
Starting Member

2 Posts

Posted - 2005-04-07 : 11:10:03
quote:
Originally posted by Pskaarup

I had the same problem. It went away when I rebooted.
quote:
Originally posted by Michael Valentine Jones


When I attempt to script out a database object from any database server with Enterprise Manager, I get a message like this:
[SQL-DMO]CreateFile error on 'CORPSQL03.pubs.DP1'

If I change the scripting option from Unicode to ANSI, I get this:
[SQL-DMO]CreateFile error on 'CORPSQL03.pubs.DP2'

If I attempt to script the objects to a file, it creates the file, but it is empty.

I can script out these objects from any other computer, but it doesn't work on my computer. I am in the sysadmin role on all of these computers. The error happens whether I connect to the server with the SA password, or when I connect with my own account with integrated security.

I can script out jobs and operators from these servers, but I cannot script out stored procedures, tables, functions, or views.

I did a Google search and found a few postings about the same problem, but no one had a solution. Has anyone ever seem this problem, or know a solution?




CODO ERGO SUM



Go to Top of Page

phpwiley
Starting Member

1 Post

Posted - 2005-12-05 : 22:27:16
We got a similar error - [SQL-DMO]CreateFile error on 'Genoa3.database_name.TAB'
We have NEVER seen this error before.
We tried rerunning the job again and it worked fine the second time. Truly bizarre. This job processed about 30,000 records (very few).
Go to Top of Page
   

- Advertisement -