Wise Package studio 7.0 SP3 - import failure
Hi,
We are using 'Wise Package Studio 7.0 SP3' in our domain. While importing MSI packages to Software Manager, few of them failed to import with below error. Please suggest.
Error : The file to import ("\\Server\Wise Share Point\Scripts\test\123\test123.msi") doesn't exist.
Thanks
RK
What have you done so far to try and diagnose the problem?
Hi RK,
My first suggestion would be to recommend that you check whether the file(s) in question are actually present at the location(s) reported in the error message. Then check if the MSI files are open in any other program - as you cannot import a locked or in-use file.
Finally, try mapping a drive letter to the sharepoint, and attempt an import using a direct path, rather than a UNC path.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Thanks EDT for quick
Thanks EDT for quick response.
I am importing the packages using 'Import a single package from any network or local drive' import method with the below options.
- Import a single package from any network or local drive -> add the msi path in client PC
a. Distribute source files to the share point directory
b. Overwrite existing application and package
c. Perform the operation on the Wise Package Studio server.
d. Detect conflicts while importing
I guess in this import method, the MSI source will be distributed to sharepoint directory and then MSI is imported. In my case, the MSI failed to distribute to sharepoint directory and resulting in import failure.
Thanks
RK
Try running validation on the failing MSI files
There may be a fundamental issue preventing the MSIs from installing, so I would first of all check that the MSIs pass the F4 table check in setup editor, and you could also run a full validation on the MSI as well, in case there are any overt ICE errors.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
I am trying to import the
I am trying to import the vendor provided msi (which we generally don't add any changes, if required we add transform to it). When I check for errors in MSI, there are lot more. But the package installs without any issues.
Can I use any alternate import methods to import these kind of MSI's?
Thanks
RK
Try changing the import parameters
Try importing the MSI without asking for source files to be distirbuted to the share point.
Also, for cross checking, which vendor apps are you having problems with? If any of them are available as free downloads, it would be interesting to try an import into a different WPS7 SP3 environment to yours
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
I copied the MSI to project
I copied the MSI to project folder in sharepoint location (i.e. \\server\wpssharepoint\projects) and then imported it to software manager, it imported without any issues. Thanks for the help.
Most of the problematic packages are microsoft ones like office , visio 2003, etc.
Thanks
RK
Hmm, perhaps your original information was not complete
So what you are saying is that you were previously trying to import packages from a location that was not in your sharepoint.
I had assumed, based on the error message you provided, that the import WAS taking place from within the sharepoint project folders.
So it is worth noting for future reference that any imports should be present in the wise share point project folders prior to import.
Aside from that, Microsoft's MSIs do not always import nicely whatever the source location. If you find a problem when importing a Microsoft MSI with an MST, try importing the MSI first, then the MST later.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Thanks EDT. Having another issue while importing the packages
I tried to import the couple of packages today. They doesn't import and the status in wise task manager shows as "Waiting" for long time and no progress further. I cancelled the tasks manually and tried to import them again but no luck. Any idea on this?
Thanks
RK
Check the share point and WPS install point
The import process generates what I believe is a queue file of some sort, as it has a file extension of something like .que, but I cannot recall if it is generated in the share point or in the WPS install folders.
What I suggest is a search of these two locations for any file with an extension beginning with q - ie search on something like *.q*
If you find a couple of these files, associated with the apps you tried to import, you can delete (or rename) the queue files and then try again.
I'm going back a few years, but I seem to recall that the presence of these files could block any further import attempts.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Will try this and update
Thanks EDT. Will try the options you suggested and let you know how it goes.
Thansk
RK
Deleted the que files but no luck
I found the *.que files in \\server\wpssharepoint\scripts folder and deleted them. Then tried importing the packages, the status still shows as "waiting". Please let me know if I can try any other options?
Any limitations for maximum number of packages
FYI, I imported 308 packages to software manager repository so far. Sharepoint directory and SQL databases has enough free space. Does software manager database has any limitations for maximum number of packages?
Thanks
RK
I have no other options to suggest
I have seen WPS environments with thousands of applications, so if you have the spare resources in terms of space, your application count is not going to cause any issues.
If the apps don't want to import, it could be that they have some fundamental defect - have you tried running ICE validation on them? Maybe the schema is somehow different to the usual values and thus is causing some sort of issue with the import process.
How long have you "waited" ?
I've no more ideas to suggest other than:
1. Check the Altiris Knowledgebase in case this issue is mentioned in there
2. Call Wise support and ask them
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Problem isn't with packages.. something to be done at server end
I have tried to import many packages, it resulted in the same issue. So, the problem isn't with the packages. I also checked the packages for errors, they seems to be clean. Waited for almost 3-4 hours after initiating the import process, but the status still remains as "waiting".
There could be something wrong with WPS application server or SQL databases configured for WPS. Does restructuring the database index or reconfiguring the databases can help here?
Thanks
RK
Could it......
.....have something to do with the server itself? It's possible a SQL service reset or server reboot could help the issue.....but I know it's kind of a long shot. Have you tried anything like this yet?
May be I can try this option but not right away
Thanks tjwest.
Ya, I can try this option but not right away. Because the server has many other databases configured to it and requires time to schedule for SQL server reset or server reboot.
Thanks
RK
WPS application server reboot did the trick
Rebooting WPS application server helped to resolve this issue. I am able to import the packages now but it import seems to be very slow.
Can restructuring the database index by increasing "block size" and "hash table size" helps to resolve the slowness issue?
WFWI.exe faulting error on WPS application server
Hi EDT,
While I am importing the packages from client PC, wfwi.exe is crashing on WPS application server frequently. Below are the event details for reference. Can you please help me here?
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 6/16/2009
Time: 3:43:32 PM
User: N/A
Computer: Server
Description:
Faulting application WfWI.exe, version 7.3.0.385, faulting module WfWI.exe, version 7.3.0.385, fault address 0x0034aaea.
Thanks
RK
Sorry, I don't know where your problem lies
Have you tried importing the apps on the server? This problem can be caused by all sorts of issues - network errors, lack of memory, no doubt Wise have a long list of other things they can suggest - so I think it's time you gave Wise a call.
Alternatively, you could try rebuilding your WPS installation from scratch, and creating a clean SQL database for it to use, to ensure that you don't have any problems with corruption in your files or database. Also create a clean sharepoint, as you can always migrate project files from your current location.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Time for database maintenance?
Hey boppanav,
If imports continue to be slow, it may be because the database just needs some cleaning up. I don't think Wise has a utility to perform maintenance, but any DBA should be able to tell you if the database needs any work and run clean up scripts. Unfortunately, database maintenance isn't my bag ;-)
Would you like to reply?
Login or Register to post your comment.