IT and business subjects
17-Jan-1313 Leave a comment
An error occurred generating a bootstrapper: Unable to begin updating resource for bin\Debug\app.publish\setup.exe with error 80070002 TESTPUBLISH
Untick the Prerequisites button
See also:
17-Jan-1313 Leave a comment
At first thought it ran OK in Crystal not when called from program.
Then checked that it ran from the program on the Crystal developer machine OK.
So runs OK on developer’s machine not on particular user’s machines.
Hence error with ODBC. Changed developer machine ODBC to use from SQLNCLI to SQL Server Native Client 10.0 i.e. SQLNCLI10 and then went to report and “Set Location” for the newest table, the report then worked on all machines
15-Jan-1313 Leave a comment
Have an old Excel file that connects to a database list using Microsoft Query. An existing user was moved to a new Windows 7 machine and then got this error.
[Microsoft][ODBC Driver Manger] Data source name not found and no default driver specified
Tried various things. In the end.
In Administrative Tools > ODBC > Drivers on his machine SQLNCLI was missing.
I did not want to install this old version, so initially changed the connection string to “SQL Server Native Client 10.0” but “SQLNCLI10” may work
14-Dec-1212 Leave a comment
VB.Net dynamic SQL WHERE DateField = ‘2012-12-13’ converts to US date and possibly throws error if then invalid
Was only happening on Windows XP, possiby 32-bit computers.
Windows 7 64-bit were ok.
In this case it was against a view. Solved by changing view:
SELECT ts.JobSheetID
, CAST(js.DateMJSAASdatetime2(0)) AS DateMJSA
,js...
FROM
13-Dec-1212 Leave a comment
In SQL Server 2005 32-bit > Linked Servers > Providers > VFPOLEDB was present, (with in process ticked)
This provider was not available in SQL Server 2012 64-bit
Executed as user: NT SERVICE\SQLSERVERAGENT. Cannot initialize the data source object of OLE DB provider “VFPOLEDB” for linked server “”. [SQLSTATE 42000] (Error 7303) OLE DB provider “VFPOLEDB” for linked server “” returned message “Invalid path or file name.”. [SQLSTATE 01000] (Error 7412). The step failed.
10-Dec-1212 Leave a comment
With thanks to
http://aartemiou.blogspot.co.uk/2011/02/no-global-profile-is-configured-specify.html
”
Even though the first three tasks were executed successfully, when I checked the history of the job that undertakes the execution of the maintenance plan, there was an error message on the last task that is the “Notify Operator” Task.
A part of the error message is the following:
“No global profile is configured. Specify a profile name in the @profile_name parameter.”
So, what does the above error message tell us? It actually says that upon the task’s execution, it cannot find a Database Mail profile in order to use it for sending the email notification.
To overcome this problem, you can set one of the available Database Mail profiles as the default one.
In SQL Server 2005 or 2012 you can do this in the following way through SSMS:
“
16-Nov-1212 Leave a comment
Use a CTE. Problem could occur in
WITH myCTE AS
(
SELECT WO, QuoteNo, EntryNo = ROW_NUMBER() OVER (PARTITION BY QuoteNo ORDER BY WO)
FROM dbo.Orders2006
WHERE QuoteNo IS NOT NULL
)
UPDATE dbo.Orders2006
SET EntryNo = myCTE.EntryNo
FROM dbo.Orders2006
INNER JOIN myCTE ON myCTE.WO = dbo.Orders2006.WO
With thanks to:
http://stackoverflow.com/questions/1466963/sql-row-number-function-in-where-clause
19-Oct-1212 Leave a comment
On a x64 PC
‘ The type initializer for ‘CrystalDecisions.Shared.SharedUtils’ threw an exception’
Project properties > Compile > Advanced Compile Options > Target CPU change to X86
Or on install of SAP Crystal Reports Version for Visual Studio 2010 tick box for running x64
With thanks to
http://www.logicaltrinkets.com/wordpress/?p=213
and for runtime
http://www.businessobjects.com/jump/xi/crvs2010/us2_default.asp
15-Oct-1212 Leave a comment
The connection string is wrong
27-Sep-1212 Leave a comment
Solved with thanks to:
http://stackoverflow.com/questions/9284375/unable-to-apply-publish-properties-for-item-x
“It appears that the issue is related to ClickOnce. Navigate to the project, right click on it and click on properties. Go to the Publish tab and click on Application Files. Check the ‘Show all files’ checkbox and scroll through the list of files. Eventually, you will come across the file that has a yellow exclamation point on it. This file is orphaned and needs to be removed. Right click on the file and there should be a remove option.
Now build the solution and the warning should be gone.”
Stephen Shakespeare 