Not a one of us can sucessfully script an entire database from the
Enterprise manager, ie. by right clicking on the database and selecting
"script database". It appears that there is a problem with the creation
of scripts for the stored procedures. The scripting stops near the end
with the following message:
[SQL-DMO]CreateFile error on '{Machine Name}.{Database Name}.PRC'
The script file is created, however only the tables and drop statements
are in the file. Basically it looks like it's getting to the point
where it would write the stored proceures out and dying.
This happens when we create a script in a single file. If we select the
"file per object" option or don't select any stored procedures then the
scripting completes just fine.
I haven't tried to script anything in a while so I don't know when this
started happening. I attempted to generate a script on a server and it
seemed to work fine. The server had SP3 and reporting services
installed as well.
We can still use DTS and a "copy sql server objects" task to copy from
one machine to another. Only generation of complete scripts for a
database seems to be affected.
Searching Google, the Knowledgebase, etc. didn't seem to yield any help
on this error either.
Any help would be appreciated.
Thanks,
Bill
Thanks for your posting!
From your descriptions, I understood that you would like to Generate
Scripts from SQL Server Enterprise Manager and encounter the error message
[SQL-DMO]CreateFile error on '{Machine Name}.{Database Name}.PRC' in the
process of generating it. If you have any questions or concerns, don't
hesitate to let me know. We are always here to be of assistance!
Based on my konwledge, Anti Virus program, such as McAfee Services, may
sometimes lead to this error. Please ensure AntiVIrus program and its
services are disabled and then try to generate the scripts from SQL Server
Enterprise Manager again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Nope, I've already tried disabling McAffee and stopping every service
even remotely related to it. I still get the same error.
Any other ideas?
Bill
Thanks for your prompt updates!
If security permits, please *uninstall* McAfee and then try to script the
database objects. I surveied internal and found McAfee will set flags in
operating system and deny it access the file sometimes.
Also, please help me collect the information below
1. Send me your SQL Error Logs to v-mi...@online.microsoft.com (please
remove 'online' as it's only for SPAM)
2. Are you logon the Windows as administrative privilege?
Please understand to find out the root cause of this issue we may need to
analyze codes and this work has to be done by contacting Microsoft Customer
Service and Support. Therefore, we probably will not be able to resolve the
issue through the newsgroups. If the issue is urgent, I recommend that you
open a Support incident with Microsoft Customer Service and Support so that
a dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Customer Service and Support phone
numbers, please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
Completely removing McAffee fixed the problem, just disabling it didnt,
however as far as I'm concerned this doesn't resolve the issue. If the
Enterprise manager has a problem with a virus scanner it is because
Enterprise manager is doing something wierd in the way it is writing
files to the hard drive. In today's computing environment, running a
computer without a virus scanner is really not an option. If every
other program on my computer works fine with McAffee and ONLY this one
blows up I have a really hard time saying it is solely a problem in
McAfee and absolving Microsoft and the SQL server team from all
responsibility. I use a wide array of different software from Microsoft
and other vendors, and this is the first case I've run into where McAfee
can be legitimately blamed for causing a problem in a piece of software.
I'll go on and open a case for this issue with Microsoft and contact
McAfee as well.
Bill
We found that the error appears to be caused by a McAfee filter driver that
was interfering with the CreateFile api that specifically sets the flag
FILE_FLAG_DELETE_ON_CLOSE.
You might be working with McAfee to get a newer version of their driver
and/or working to determine why this driver is causing problems.
Hope the information above will also help for your opening the incident.
Thanks for your understanding. Your cooperation is appreciated, and will
result in a more efficient troubleshooting process.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.